There’s a couple of issues we want to think about and try to tackle when thinking about how to develop a mobile story for Blockstack
- Sign in with blockstack from mobile
- A Blockstack mobile app
- Name registration on mobile
- Possibly subdomain creation for large open source teams that don’t want their users to pay for a name
I’m starting with some notes around my thinking on these issues.
Sign in with blockstack from mobile requires, as a first step, redirecting a user to browser.blockstack.org on mobile sign-in attempts. This is easy enough to do, but we may want to figure out a more complex mobile sign-in story first. If we are okay with using browser.blockstack.org on mobile devices for a while, this could be done pretty quickly.
One potential snag – if we want people to sign in from mobile native apps, then we’d need a mobile auth API that would require more planning before I’d be comfortable estimating the effort.
Implementing a Blockstack mobile app is varying degrees of difficult, depending on what we call a mobile app. If browser.blockstack.org is the app, then that’s done. If it’s a native wrapper around that, it’s eminently achievable, but would still require some engineering effort (for iOS, for android, we haven’t started, but it doesn’t require that much) – realistic timeline is mid-January if we focused on that over other things
Paying for a name in mobile – that will be supported as soon as pure-JS operations are merged into the browser. I have some code that does the transaction generation, UTXO funding, etc, but it isn’t integrated into the browser, and doing so is not totally trivial. This is roughly a month of effort, but the question is when we’ll be able to prioritize this.
Subdomain creation – we are pretty close to something like this. Basically, if we wanted to roll out such a service ourselves, we’d need to build some additional tooling, and in doing so, would be able to provide other teams with documentation and code to get started with it themselves. There’s interest from a bunch of teams for us to build this. This is probably one sprint’s worth of effort if that’s the focus. The point here is that this is mostly about building infrastructure, rather than making any deep software changes