...
...
...
...
...
...
Current
Product Path to Support KPIs
Usability Testing (The How)
Create plan to track metrics in order to better understand use patterns of the current production site
Create plan to conduct user testing sessions for current dashboard onboarding and use
Create plan to conduct user testing sessions for new features prior to roll-out
Reporting for users
Proper KPI Measurement
Analytics
Metrics / Measurement
Increase Use
Identify and create first time end-to-end user experience path (i.e. going passed simple registration)
Identify and create specific follow-on experiences for returning users (better educate and surface features)
Guides and prompts
Dashboard Main View 2.0 Experience
Identify and create new feature sets to drive use
Pay with crypto
Purchase FIO in dashboard
FIO Crypto Handle Monitoring (non-imported)
Locked Token Approach (example: lock and release token schedule)
Wallet Connection Expansion
Adoption centered notifications
Growth
End User - This relies on KPIs from other areas
Increase awareness of FIO protocol, the number of FIO Crypto handles and the number of and value of domain sales
Identify and implement cross-pollination of marketing and dashboard sites/channels to better integrate the two
Information/Promotion Highlighting within Dashboard
Information/Promotion Support in Marketing Channels
Create Referral Program Dashboard Experience
Create FIO Crypto Handle/Domain Promotion/Recommendation Engine
Third-Party Registration
Integration - This relies on KPIs from other areas
Increase Domain & Crypto Handle Registrations and Utilization with Partners
Create white-label model for partners
First Time User Experience
Landing Page
Identify and develop streamlined end-to-end partner experience
Return User Experience
Partner goal-oriented views (staking focused for example)
Opportunity - This relies on KPIs from other areas
Identify new creative ways FIO Protocol can increase usability across the dashboard and new segments
FIO Chat/Conversation Oriented Approach (humanized experience)
Token Management System (TMS)
Portable Dashboard Components
Community Support - This relies on KPIs from other areas
Create Governance UX
Operational (Ongoing)
Maintenance and Updating - Identify Bugs
Continue to identify areas of improvement within current deployment
Perform UAT and Production UX Testing
Triage/Fix Product Experiences when identified
...
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:
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 |
...
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 |
...