Dashboard Roadmap
Current
Link to currenty dashboard roadmap:
Legacy (For Reference Only)
In process
Item | Description | Notes and Status | Order of Priority |
---|---|---|---|
Stake within the dashboard | UX and Spec Complete, UAT Tested Update: Staking will need to address voting/proxy with a drop-down menu to show a list of BPs | 1 - COMPLETE | |
Dashboard Integration - Register crypto handle and domain | This includes the following:
| This is at the initial scoping with business and the dashboard team Priority and order of deliverables to be determined during scoping Next steps:
| 2 |
Dashboard Integration - Buy FIO using Indacoin | Buy FIO using the Indacoin UX. | The Indacoin landing page has been completed: https://buy.fio.indacoin.io Next steps:
| 2 |
Dashboard Integration - Pay with crypto or exchange crypto into FIO tokens |
| This has been removed from scope of MVP, but needs to be enabled soon after launch. Registration site piece of this tracked in: DASH-4: [dashboard] Modify Registration Site to enable dashboard payment in cryptoClosed Next steps:
| 2 |
Dashboard Integration - User Flow |
| Next steps:
| 2 |
Dashboard Integration - Deeper Branding |
|
| 2 |
Dashboard Integration - Limit # of free crypto handles |
|
| 2 |
Porting of Registration Site functionality |
|
| 2 |
Token/Domain Wrapping | This includes wrapping for:
| UX In Process UX flows & specifications have been completed for: | 3 - COMPLETE |
Token/Domain Unwrapping | This includes unwrapping for:
| UX In Process Next steps:
| 3 - STARTING |
Notifications - Dashboard Global | This includes notifying in app and via email about
| UX Complete, Spec in process, Development in progress Next steps:
| 4 - IN PROGRESS |
Governance |
| Preliminary UX Done, Needs Review Next steps:
| 5 - IN PROGRESS |
Allow mapping of passed in public addresses - Opportunity | A wallet may add a link to pass public address(es) to the Dashboard to be mapped to the FIO Address, instead of copy/pasting | Not Started | ? |
Allow users to “import (or monitor)” FIO crypto handle so they can see transactions for it without having to import the owner private key. - Opportunity |
| Not Started |
|
In parking lot
Item | Description | Notes | Order of Priority |
---|---|---|---|
Get mappings from exchanges/wallets which use oauth and allow key retrieval. - Opportunity | Login with exchange credentialing, bypass login potential, automatic mapping | Not Started | TBD |
Register domain/address for someone else |
|
| TBD |
Lock tokens |
|
| TBD |
Degraded mode | Enable the Dashboard to function without the need to connect to FIO BE and EDGE servers once local wallet is established. |
| TBD |
Information/Promotions |
|
| TBD |
3rd party wallet integration |
|
| TBD |
Promote/recommend domains. |
|
| TBD |
Up-sell domains to address buyers and vv. |
|
| TBD |
“Watch domain” to see when it becomes available or is on sale. |
|
| TBD |
Pay with fiat |
|
| TBD |
Other blockchain tokens |
|
| TBD |
Mapped token balances |
|
| TBD |
Referral Program |
|
| TBD |
Pay for multiple years of domain |
|
| TBD |
Address/domain suggestions |
|
| TBD |
API Node Server |
|
| TBD |
Analytics |
|
| TBD |
Testing |
|
| TBD |
Super Bot | A telegram and Twitter bot that seamlessly enables users to register their own FIO address |
| TBD |
One-sided FIO Transactions | A FIO transaction where only one party has a FIO Address |
| TBD |
Ledger Staking | The ability to stake within the dashboard from a ledger device |
| TBD |
Add paging to Validate NFT Signature | Paging of data retrieval may be required when a lot of NFTs are returned (similar to how a wallet might page FIO Request data). | TBD |
Metrics
Item | Description | Notes | Order of Priority |
---|---|---|---|
Google Analytics | This includes … |
| TBD |
User Testing | This includes installing tracking functions such as:
|
| TBD |
KPIs | TBD |
| TBD |