Date/Time: 2018-04-26 @ 12:45 UTC / 08:45 EDT / 20:45 HKT
Click here to convert to your time zone
Length: 45 minutes
Meeting link: https://zoom.us/j/351130688
This meeting is for issues around our consumer facing products such as the Blockstack Browser and future mobile apps.
Please reply to this forum post with items you would like included on the agenda.
Each item should include:
Background information: Links to github issues, forum posts, etc with background information on the item
Desired outcome: what decision or deliverable would you like from the discussion of this topic at the meeting?
We’ll save ~10 minutes or so for community questions or comments at the end of the meeting.
2018-04-26 Consumer Product Engineering Meeting
We’re creating a list of what we view as consumer products so that we’re all on the same page as to what things should be discussed in this meeting.
Oh ok, thank you.
- React web app
- macOS app
- Windows app
- Linux app
Thomas: re: each team has its own website, but they should really only be responsible for the content of the project, whereas a small team is responsible for the larger design language/system for every product at blockstack. eg each team can enter content via .md/cms that uses a template/website
Notes on browser:
- We’re taking out the app directory
- Form factor is web deployment, desktop apps are just wrappers and less relevant, discuss native mobile apps and extensions
- The “browser” will only be for onboarding, authentication, profile management, data management
- Can we make this one category that includes subcategories for Web, Linux, MAC, windows, iOS and Android? Easier to reason about?
- Web version should be disabled once you deposit any money at all unless you’ve hooked up a hardware wallet. Look at the myetherwallet fiasco. We could even disable deposits for this version unless a hardware wallet has been connected. Subdomains are fine. Domains are more valuable.
- We should also have a conversation about the possibility of an extension form factor. We need to ship one for Mozilla although this is likely not going to be possible in Q2.
- Splitting our the app directory
- The keychain will always have to be in the core app, but could split out wallet functionality into an app that gets included in an iframe
- We need to simplify the interface. After onboarding, the only features should be profile management, settings, wallet, and data/app management.
- For work on the social graph support, we should consider having that be a separate “contacts” app.
Notes on investor wallet:
- Should it be separate?
- security reviews
- integration with Trezor
- hire a security professional, maybe Dominik
Notes on App Store:
- Will be on app.co
- Will be very important for us to automate app submisions - this will lower the friction for developers and also help us better track app growth - it will also make it more inviting for developers to build apps
- Should be extremely simple at first
Notes on explorer:
- We should talk about the best way to maintain this and continue to make improvements
- Probably want to give this its own domain instead of a subdomain - think etherscan
Notes on websites that aren’t apps:
Blockstack.org is one and corresponds primarily to devtools, Gaia will have its own website. The blockchain might have its own.
- In the future we want to move towards a world where each team can maintain its own website without having to involve the rest of the team or get permission. Think how uport has its own site and Mitchell and Clint and JB have their own community site.
A possible short list (for the near term):
- Blockstack web (w/ wrappers for iOS, Android, Mac, Linux and windows)
- is a “browser” and wallet - investor wallet just uses hardware wallet integrations for higher security
- App Store
Future products (won’t be worked on until 2019 or later)
- Actual browser on desktop and mobile w/ BNS support