This is a roadmap for how we can strategically get the Blockstack app onto blockstack.org.
The motivation is that rather than explaining Blockstack with our website, we believe it’s a more effective strategy to let people see for themselves by getting them into the app explorer as soon as possible. In the future, blockstack.org will simply be the Blockstack app.
Initial Mockups of a new Landing page:
- We should take opportunities to resolve technical debt while we’re modifying code. That means making React components more modular, moving CSS to Sass, writing unit tests, etc.
- Being that we’re planning to redesign the website and messaging, our gameplan should allot appropriate time for the entire design and discovery process.
- At large scales, the app explorer will be a complex app, but we’re not there yet. It’s best to leave it as simple as possible for now so we don’t waste time building features we don’t end up needing.
Move the app explorer to blockstack.org
- The app explorer should be isolated so it’s portable for Phase 2.
- We will want a well executed design here with weigh-in from team and potentially investors.
- This is also a good opportunity to build the hyper-simple foundation of an Apps API. At first, we can just store a list of apps accessible via an endpoint, but in the future we can add a CRUD management layer.
- Build a simple admin dashboard for our team to easily add applications to the app explorer (If we used something like Django for now we get an admin dashboard for free) (in the future this will be a decentralized directory)
- 2 Weeks: Design mockups completed for the homepage
- 2 Weeks : Dev completed on the App Explorer app
Migrate blockstack.org content to Browser app
blockstack-browser is a very feature rich app, so it makes more sense to move the fairly simple
blockstack.org repo contents into the
- We should do this on a fork off the
developbranch so development can continue while the large changes are being developed.
- Here’s one spot we can take opportunities to resolve technical debt while we’re moving code. That means making React components more modular, moving CSS to Sass, writing unit tests, etc.
- We should make sure vital non-UI code is moved over the new codebase, like any scripts we need, etc.
- 2 Weeks: Code transfer and cleanup complete
We really want to redesign the app experience. I think it makes the most sense to do this before a big unveil, for a few reasons.
First, this is a dramatically new vision for our user experience and we should turn heads when it’s launched. We don’t want to roll out a new vision and have it feel half baked.
- We could launch once Phase 2 is complete and then make the design refresh a separate launch. I think we should do a redesign though.
- We could also break the redesign in two — 1) app pages and 2) info pages
- 9 weeks: We need to give this step some room, and clarify what we hope to accomplish. Conservatively, if we’re scrappy, I’d say 6 weeks. Liberally, 10-12 weeks. Let’s meet in the middle for these purposes.
With work complete, we can point blockstack.org to the Blockstack application site.
- We’ll want to make sure if we’re moving URLs around that we implement redirects so we don’t take a hit on SEO.
- 1 Week