We see it differently perhaps because we’re looking at users differently.
To help explain my reasoning, let’s segment users into different groups such as early adopters / tech savvy versus majority who need stuff that just works. Obvs a vast simplification, so not accurate or definitive, but useful for illustration.
First group, no problem.
Second group will have certain characteristics that change the balance. For them (the large majority I suggest), having a separate launcher and learning how it works together with SAFE Apps (browser and other stuff) is I think what we need to consider: versus having one app which is called “SAFE Network”, and operates as both browser and SAFE App Launcher (in the way we originally envisaged SAFE Launcher - hence the name).
For most people (ie the ones who need something that is very simple and just works) the adoption process reduces to:
- download / install and run SAFE Network
Using SAFE Network becomes
- start SAFE Network
- browse SAFE Websites instantly (no account needed)
Storing data requires a one-off account creation process, which once done can offer login whenever the user starts SAFE Network, while saying it is not needed just to browse.
This is a very slick and easy process for both getting on SAFE Network the first time, and each time the user wants to use it. They only have to know about one thing, and it does what it is called, until the point at which they are ready to learn how to do the next thing.
This is one of the least well understood but most crucial things about building a user base. It is also very hard to engineer, but for mass adoption software (or almost anything) needs to be trivially easy for most people to begin using, and only gradually ask more of the user as they become familiar with it and want to move onto doing more. In this context trivially easy for most people means sufficiently within their competence to be trivially easy to understand, and minimal time and effort to achieve.
So for example: getting on to browse SAFE website content should be install and run one thing, storing data is an optional action the user can discover or seek out through the user interface, and when they do, they are prompted to create an account. Once they have done this, and are logged in, further command options become available (such as for messaging, sharing data, creating a web service etc.). Prior to that point those options are also offered, but when activated prompt the user to login or create an account.
Step by step we can lead almost every user to the maximum of their competence at the time, and if we get it right, the software will take them beyond this by teaching them (or rather helping them discover and learn) how to increase their competence and do something they never realised the wanted to do or could achieve.
Creating software that does this takes careful thought, and is hard for various reasons. One is that we naturally assume knowledge and skills of users that they won’t have. Once I know something without thinking about it, it becomes very hard for me to place myself in the shoes of the majority of users, but is readily apparent when I try to show the average person something that to me is trivially easy.
If we want SAFE Network to be adopted by the masses, I think this is what we will have to achieve. Not necessarily on day one, but the sooner the better, so let’s give it a go! 