If the fediverse is to be adopted by the masses, the onboarding experience needs to change. A new user can’t be presented with a choice of instances as part of signing up or at least the process of making the choice needs to dumbed down a lot. I don’t know how or if this can be solved, I just know as someone involved in app development and UX that the current experience won’t work.
My mother would not know how to handle this paragraph: “Lemmy.world is one node in a network of hundreds of Lemmy instances. Before you sign up here, take a moment to explore all the instances at https://lemmyverse.net/. You may find an instance with a regional or topical emphasis that speaks to you! Don’t worry about being left out; Lemmy instances are interconnected so users from each instance can participate with communities on other instances.”
For mass adoption it needs to be so simple that even non-techie older people can get through it without feeling like they might be doing something wrong.
I think they should stick to the “email provider” analogy. Whole paragraph should be something like:
The only thing you need to start interacting with the Fediverse is an account with one of the many providers, just like with email! Providers are freely available across the globe: pick one that suits your location or interests best! You can start browsing the content of nearly the entire Fediverse from whatever provider you choose. Don’t worry, you can always create an account with a different provider later.
You could add a sentence or two about where to find sensible defaults or link an article that explains the more subtle things.
I think the emphasis on instances (and not naming them the more familiar providers) hinders adoption.
Never considered it like that, good analogy
That’s a great analogy, but it’s too big a barrier for many, most give up before picking a instance, we should set good defaults and then the users can figure it out once they are used to the platform.
Yes, very much in favor of sensible defaults for first timers. Most frontends/apps support multiple accounts anyway so changing/adding more later on really shouldn’t be a problem