You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In preparation for Mainnet which is announced to be right after Carthage release and scheduled for production on or before August 15th, I am making an attempt to collect a number of features supporting new users onboarding, key features discoverability and overall usability.
This means that Ephesus features (channel payouts), whilst present to the newest runtime, will be delivered on Pioneer and Atlas after mainnet.
Adam in effect will remain the only designer to support Atlas, Pioneer and Marketing Website (joystream.org) adaptation for MainNet launch. Hence I am listing non-atlas features here as well, with a view to balance this work out and ensure that critical features in non-Atlas apps are designed on time and make it to Mainnet.
Objective
All front end user touch points across joystream platform are ready for new users, potentially drawn with mainNet launch, to start onboarding and ready to perform all necessary actions with minimal friction.
For Joystream.org - create appropriate treatment for Mainnet launch page, that can be used as a landing page for all external campaigns, target Content Providers/ Channel Owners Segment and feature links to the platform FE apps.
For Pioneer.org - ensure to accommodate agreed additional main-net features while make progress with overall app usability.
For Atlas - focus on overall usability for new users, and bring the hero launch features (NFTs marketplace) to a more usable state.
Scope
Two 🆕 features are earmarked for both Atlas and Pioneer wrt above:
Talisman [Universal] Wallet/ Signer
Fiat Exchange
⚠️ NB: the prioritisation is being worked on, so features listed below may be delivered in a different order from what is presented below.
Context
In preparation for Mainnet which is announced to be right after Carthage release and scheduled for production on or before August 15th, I am making an attempt to collect a number of features supporting new users onboarding, key features discoverability and overall usability.
This means that Ephesus features (channel payouts), whilst present to the newest runtime, will be delivered on Pioneer and Atlas after mainnet.
Adam in effect will remain the only designer to support Atlas, Pioneer and Marketing Website (joystream.org) adaptation for MainNet launch. Hence I am listing non-atlas features here as well, with a view to balance this work out and ensure that critical features in non-Atlas apps are designed on time and make it to Mainnet.
Objective
All front end user touch points across joystream platform are ready for new users, potentially drawn with mainNet launch, to start onboarding and ready to perform all necessary actions with minimal friction.
For Joystream.org - create appropriate treatment for Mainnet launch page, that can be used as a landing page for all external campaigns, target Content Providers/ Channel Owners Segment and feature links to the platform FE apps.
For Pioneer.org - ensure to accommodate agreed additional main-net features while make progress with overall app usability.
For Atlas - focus on overall usability for new users, and bring the hero launch features (NFTs marketplace) to a more usable state.
Scope
Two 🆕 features are earmarked for both Atlas and Pioneer wrt above:
Atlas
search
query usage #2882Out of scope: ⛔
Pioneer
JSG
Pioneer Builders WG - 👥 - community dev
Joystreaml.org
Out of scope:
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: