2021-07-30 - Wallet Update

[MaximusHaximus]

Welcome to the team, @esaminu ! (Osman) :).
@esaminu is going to be working on end-to-end testing critical flows on the wallet in the short term, and we're really excited to have him on board!

Done

Production releases

• See descriptions for specifics:
• Release 2021-07-21 near-wallet#1942
• Release 2021-07-23 near-wallet#1953

Noteable changes:

1. Fungible Tokens Transferrability

• Users can now send (NEP-141) fungible tokens to other NEAR wallets directly from the wallet 'Send' UI flow! (Transfer Fungible Tokens - Version 0 near-wallet#1714)
• Users no longer see fungible tokens on their account dashboard unless they own some quantity of the token (Hide 0 balances for tokens near-wallet#1900)
• Added send/receive buttons to the navigation bar when using the wallet from a desktop so you can get to the send flow from anywhere else in the wallet UI!

2. Disabled 2FA SMS support for Vietnam

• Due to an excessive amount of failed deliveries via SMS to Vietnam, we have temporarily disabled 2FA using SMS to Vietnam. We are investigating a workaround/fix to this problem and intend to re-enable this functionality when we have the issue addressed.

This release also marks some important milestones in the project!

1. This contains our first implementation of a service in the codebase with no coupling to redux, mixpanel, etc.,
2. This contains the first components in the codebase that strictly follow the wrapper / presentational component pattern!
   These improvements to how we build will allow us to separate async concerns with side-effects from the pure presentational layer of our UI, which will let us start building good tests around our components. Coming soon: Storybooks for new display components!
3. We are adjusting our official sprint start/end dates to match up with reality a bit better.

• Previously, our sprints were 2 weeks long -- they ended on Wednesdays, and started the next day. We are trialing 8-day sprints, which start on Monday and run until the following Wednesday.
• After each sprint, we are allocating the last 2 days of that week to post-launch support for the code we just shipped, codebase maintenance (removing dead code/feature flagged code from the prior sprint) and to give the team a bit of a chance to participate in hack-it Fridays and do some learning about the new best practices we are implementing in the project.

In Progress

1. FIat currency value of NEAR tokens - Shipping this sprint! (Fiat currency value of the wallet near-wallet-roadmap#28) (NEAR <> Fiat Conversion near-wallet#1854)

• We will start displaying fiat values of fungible tokens in the wallet!
• Initial release will show NEAR token fiat values in USD
• Future releases may display fiat equivalents for other fungible tokens that are listed on Coingecko
• Future releases may display fiat equivalents in multiple fiat currencies (e.g. EUR, CNY, etc.)

2. Feature flags in the Wallet codebase! - Shipping this sprint!

• We want to facilitate a more regular shipping schedule where small bugfixes can be shipped directly to mainnet without needing to wait for the next major release cycle/merge to stable, and without needing to cherry-pick commits and deal with hotfixes and bi-directional merges between master and stable.
• We also want eliminate 'doom PRs' with large/huge diffs being merged to production when we are cutting a release; large releases are not feasibly reviewable and we want diffs to be small so we can be explicit about what we're shipping/changing.
• We're going to accomplish this by using feature flags! By wrapping new behavioural changes in feature flag checks, we will be able to merge new code to our trunk branch and ship it to our mainnet instances even though the code is disabled in some environments.
• This will let us merge partial implementations early on, so that multiple team members can iterate on in-progress code without creating an ever-increasing-in-size changeset in a feature branch

3. Redux state structured by account id - Working on the selectors layer!
   See details @ Refactor Redux state to be keyed by accountId and new folder/file structure near-wallet#1239

• Currently we only store any Redux state for the currently active account, and clear all redux state and re-load when switching accounts.
• By keeping our state organized by Account, we can improve loading time account switching time drastically.
• Adding redux-persist combined with this change should allow almost instantaneously UI load times for the wallet when a user has visited in the past.
• Our first stage of this process is to ensure that all Redux state accessing is done via a selector. This will provide a consistent and stable API for our components to use to fetch data while we change the underlying state shape.