BCF Feedback on LODEPay Redesign Specs

Owned by Dan Wasyluk (Unlicensed)
Last updated: Oct 23, 2020

related doc: https://lodeone.atlassian.net/wiki/spaces/AA4T/pages/309788687/LODEPay+Wallet

General

Across the board we need a swagger doc that outlines the available APIs for retrieving data represented in the new designs that is housed within Lode’s cloud environment. In some cases the members portal API will need to perform additional actions behind the scenes in order to build the dataset that is needed to populate some of these new screens.

  • Example: Recent Activity

    • Need members portal to be adding ‘activity entries’ as user’s perform actions. In some cases the wallet (or related microservices) may need to call a specific endpoint on the members portal to register an activity; we need these APIs defined and documented

    • Activity types- we need to agree on a standard set of activity types and what the display entry for that activity type looks like. Currently we have a number of sample rows that relate to things like ‘direct payment’, ‘payment sent’ and some other un-titled activities. We need to finalize the list of these activities and what their display looks like.

  • Example: Buy > Purchase History

    • The VDC microservice has some ability to provide a purchase history relative to certain assets but would need to be enhanced to provide a ‘proper’ purchase history for those assets.

    • For other assets we would need new API’s for purchase history specifically things such as purchases of LODE tokens.

  • Example: Buy > Lode > Bank Wire

    • We don’t support this payment method at all in the wallet today so we will need documented APIs around the bank-wire purchase process.

  1. Desktop designs have a navbar at the top with a ‘search’ field, what does this search across?

  2. Designs for both desktop and mobile show users having an avatar but there is no way to set/upload an avatar, what should the expectation for avatars be?

  3. There is also a notifications icon on the top bar but we have no designs of it ‘expanded'. What are the notifications expected in this area? Are they expected to persist in some way?

  4. There is a ‘gift icon’ in the navbar, we aren’t sure what functionality is expected of this control.

  5. Support - there is a nav item for support but no designs for a support page. What is the expectation when the user clicks this button?

Components

  1. Need ‘loading component’ for

    1. Full page loading (currently large circle loader in AGXPayMobile, visible on VDC screen and Gas Station screen)

    2. Process pending (currently bottom-blue indeterminate loading bar presented when user is setting up a new wallet or restoring a backed-up wallet)

  2. Dropdown design will require significant additional dev work to accommodate the custom ‘dropdown style’ shown in the mockup. Additionally this type of modification of the dropdown is non-standard for many modern applications.

  3. Row component- we can use rows within lists as components (swipe left or right on the row to perform an action). We use this in the transaction-history view and need a design spec for it there (and can use it in other views JFYI for design team).

  4. Feedback: Warning messages look very similar to buttons

Login

  1. Design is not standard responsive

  2. Where does the ‘Let’s get started' view show? The wallet setup step occurs before it making it unreachable

  3. Desktop: Swipe picture to navigate slide set

    1. Text overlaid on slide (and animated?)

    2. Wallet-init controls displayed using button-panels to the right of the slides

  4. Mobile: Swipe picture to navigate slide set

    1. Text displayed as header/subheader at bottom of screen

    2. Wallet-init controls displayed using standard buttons below the slides

Terms of Service

  1. Desktop: Terms displayed to the right of the login-slides in self-contained scrolling panel. Should scroll independently of page. Agree/Disagree buttons should be visible at all times.

  2. Agree button should be disabled until user scrolls to the bottom of the TOS

  3. TOS should be fetched dynamically

  4. Currently there are no requirements around logging the user’s agreement to the TOS (its simply flagged in local storage)

New Wallet - Display Recovery Phrase

  1. Different component displays the phrase on desktop v. mobile

New Wallet - Reenter Recovery Phrase

  1. Different component displays the phrase on desktop v. mobile

  2. Progress bar?

Existing Wallet - Enter Recovery Phrase

  1. Should we center align form on desktop to match all other center-aligned desktop forms?

  2. Progress bar?

Create Wallet - Link Lode Account on Setup

  1. Why use option buttons on desktop rather than making it match mobile?

Create Wallet - Link- New account

  1. Not standard responsive design

  2. Desktop: “skip this step” button- artifact that should be removed?

  3. What happens after you create a new account?

    1. You get an email with a confirmation code?

      1. The email has a link to automatically confirm?

    2. The app takes u to a page to enter the confirmation code?

  4. What features should be disabled if the user signs up for a new account but hasn’t agreed to any of the investment contracts/TOS/etc outside of the initial TOS required in order to use the app to begin with.

Create Wallet - Link- New account enter confirmation code

  1. details TBD

Create Wallet - Link - Existing Account

  1. 2FA code input needs to be its own screen/experience based on if that user has 2fa enabled.

Dashboard

  1. different designs for mobile and desktop, not simple responsive

  2. in desktop mode, a QR code ‘address’ is shown, address will be different based on coin, which address are we showing here?

  3. Dashboard shows a total sum of all assets. What do we do for assets that do not have a fiatValue datasource?

  4. On desktop for >5 assets will the list just scroll horizontally or can it only be navigated using the arrows in the top right?

  5. Why show masked VDC in assets list view when nothing can be done with it? Also we are no longer showing the VDC balance in assets view?

Buy

  1. Why show token info modal prior to purchase? This will become redundant very fast and annoy users.

  2. Different designs for mobile v desktop, not standard responsive

  3. Will purchase methods be hardcoded per-asset or will it be dynamic in some way?

  4. Designs show purchase flow for ‘buy LODE tokens with Silvercard’ - how do the flows for buying LODE with Silver Bullion or with Bank Wire look?

  5. When purchasing tokens with a silvercard there aren’t designs to for choosing whether you are buying a new card or whether you are redeeming an existing epin.

  6. There is a design for 'Add an item to deliver in exchange for Lode Tokens) but it seems to be the start of some kind of shopping cart experience? Ne`ed more info on the rest of the flow here / what happens if the user leaves mid-flow, etc.

    1. In mobile mode are the screens intended to be presented 1, 2, 3 sequentially or as-shown-in-design 1,2,3 one giant scrolling list that is dynamically updated as you perform actions in other areas of the screen?

  7. What does the info icon in the top right of buy screens show?

  8. Need an API for historical token price, in the case of LODE/AGX/AUX we would need the members portal to provide a special API for that data.

Assets

  1. Nonstandard design for responsive layout

  2. How is tx history display on desktop and mobile? Its unclear how a user chooses the asset they want to interact with on desktop.

    1. Will need members portal APIs to support ‘merged’ transaction history as represented in the design which supports pagination/loading more.

  3. On mobile what happens when you press the action buttons from the main list view (ie: send, receive, buy)

  4. Need an API for historical token price, in the case of LODE/AGX/AUX we would need the members portal to provide a special API for that data.

Assets - Coin Page

  1. Where is history price history drawn from (what API source?)

  2. What should we do for assets that have no fiat value data source

  3. Assuming that tx history should remain as-is today aka ‘load more’ etc.

Gas Station

  1. Not standard responsive design

  2. same components can be reused on desktop/mobile but layout and routes will be different (routes… maybe)

  3. Should consider GAS station for ETH?

Settings - Unlinked - FOR ALL SETTINGS SCREENS WE NEED API DOCS

  1. Unlinked view not standard responsive design (although simple)

  2. Showing 2FA alongside U/P is nonstandard, it needs to be a secondary step after U/P has been authenticated

Settings - Signup

  1. Signup form is same component but shown in modal on desktop (why?)

  2. confirmation code sent via email- same component but modal on desktop (why?)

Settings - Linked - This view is strange in the mobile v. desktop sense very different control paradigms at play

  1. Profile

    1. Standard responsive form - special validators we need to know about?

  2. Preferences

    1. Why is this view so dramatically different on mobile? are elements missing from desktop?

  3. Account Info - these views are very different between desktop and mobile, its very jarring.

    1. Where is this on mobile?

    2. Change password screen

      1. Enhance rules UI

    3. Things like recovery phrase, wallet pin are not related to your account they can exist without a lode account at all, these should likely be in a different tab altogether.

      1. Pin change- modal on desktop, standard screen on mobile

      2. Recovery phrase - modal on desktop, standard screen on mobile

  4. Investment Contracts

    1. different views for desktop v mobile (again, modal v standalone screen)

    2. What are the expectations for the various investment contracts and storing the user accepted info?

    3. What does ‘more information’ do in these views (desktop)?