The FIO dApp product has been renamed Dashboard. This page has not been updated.

Agenda

Re-align on high-level strategy

Register only and push to wallets VS. full functionality?

Current plan

Register only and push to wallets

David Gold proposed that the dApp be limited in functionality and more aggressively push to wallets which have integrated FIO.

In the meeting I will ask David Gold to explain to the dApp Committee:

DECISION: Proceeding as planned.

Closed Beta/Exclusivity

Current plan

MVP is made available to all users at launch, as the more users can benefit from the ease of onboarding, the better.

Closed Beta/Exclusivity

Kaitie Zhee proposed that at launch the dApp will only be available to restricted number of users.

In the meeting I will ask Kaitie Zhee to explain to the dApp Committee:

DECISION: Proceeding as planned. A new initiative was created: https://fioprotocol.atlassian.net/browse/WP-345

EDGE wallet framework

During recent discussions with EDGE, it was discovered that EDGE offers an SDK to dApp developers to allow users to generate and store private/public keys using the EDGE wallet framework. If adopted by the FIO dApp, it will likely make the development process faster, as it will eliminate the need to custom-code wallet logic and storage.

If implemented:

Further customization options:

In the meeting, we will discuss cons and pros of using that approach.

DECISION: consider using non-EDGE-branded version for FIO keys only in MVP.

Review UX (time permitting)

Review the latest UX and gather feedback.