Essentially it took me around 1.5 minutes to figure out how to login on the app. You tap buttons and it says login required. Why not just open up the login interface? Or provide an easy link or ask immediately after first run.

Or on the sidebar, have an obvious banner that says “Login”.

Just too many taps to get logged in to add your first account, and too difficult to figure out where to do so. And no help when the app prompts you to login. Make it super easy to do that!

Edit: I have developed modern UX/UI, so if even I found it confusing, I know non-expert or unfamiliar users are going to fail to ever use this app, which would be a shame. It’s really great!

  • JamesMowery@lemmy.mlOP
    11·
    1 year ago

    I don’t mean to be dismissive, there are some good ideas in this post… but if spending 1.5 minutes looking for the login button is a major issue for you, you’re about to have a bad time.

    If I, of all people, am spending 1.5 minutes… then A LOT of people are going to be having a bad time. I have previously developed UIs. Onboarding is one of the most critical stages of engagement and adoption of applications.

    The rest of your comments, to be frank, don’t make sense. Might even be dangerous, which really makes me question what you’re advocating for. Are you genuinely arguing for a poor onboarding experience just because people need to put in more work to understand something? Genuinely STOP, haha. It’s terrible to suggest such a thing.

    Put yourself in the shoes of a non-expert user. You are definitely NOT representing the 90% average users, and that type of attitude will hurt the fediverse and open communication tools.

    We want more people to join this community. We don’t want to guardrail it or make it difficult, which is the type of thing you are advocating for… for reasons that don’t make sense. Let’s get away from elitism and invite more people into this wonderful community, not whatever you just suggested!

    • PriorProject@lemmy.world
      1·
      1 year ago

      Are you genuinely arguing for a poor onboarding experience just because people need to put in more work to understand something?

      No? I’m not sure how you got that idea from my comment. Recapping:

      1. People are signing up very fast in spite of the poor onboarding. Maybe so fast that they’ll break servers. In these conditions it’s rational to focus on performance and capacity. It’s even rational to throttle onboarding, through disabling signups or deprioritizing onboarding polish.
      2. The rough onboarding experience is a true reflection the rough experience post-onboarding. In these conditions, its rational to optimize the post-onboarding experience FIRST to increase post-signup retention. A slick onboarding followed by a rough ride is a good way to maximize the number of people who write off your app/ecosystem and then provide poor word of mouth about it. Again, leading to potentially rational decisions to prioritize other work above onboarding polish.

      That said, you seem passionate about onboarding and have the background to do something about it. I’m sure you could help a lot getting involved in the github project. No one (including me) WANTS a poor onboarding experience. The question is who is going to prioritize it now over the other serious issues that are currently being caused by the rapid influx of successful signups in spite of the onboarding jank.