14
11 Comments

Feedback on my new shiny onboarding 💅

Over my last iterations on Frenl, I mostly focused on the landing pages and on raising the conversion rate. It is now around 20% and I am happy with it.

So far the only input I was asking from the users were two free texts "I can help with" and "I need help with". These were displayed in introduction emails.

I realized that it wasn't enough to spark interest and start conversations so I decided to add social/community links (Twitter, Medium, Indie Hackers...) to the Frenl user profiles.

Since it was a significant raise in the effort asked to the user, I wrapped it inside of a new multi steps gamified onboarding instead of asking for everything at once.

I am now in the situation where I have no clue if it was helpful and I would love to get feedback on the onboarding experience :)

In particular, do you feel like the requested amount of input is overwhelming?
Are there some field that you would only consider filling after testing the app more thoroughly?
Anything that felt odd?

Thank you so much in advance 🙏

https://www.frenl.com/indie-hackers

  1. 1

    The signup process was pretty smooth, although I did feel a little overwhelmed when I needed to fill out the two-sided part at the beginning, though it wasn't that bad since I could mostly click things instead of typing :)

    One thing that wasn't clear to me was if all the fields are required, but I ended up skipping them because I was lazy, not because I don't have them. It would be really nice if there was some autocomplete.

    Other than that, well done and congrats on your new flow :)

    1. 1

      Haha that's exactly what I thought too: "It's a lot of buttons but since it's only clicking it should be fine".

      Everything is optional in fact. I used to display "(optional)" in gray next to the fields but since it was everywhere it looked a bit weird.

      For the autocomplete, I think that in the future I would allow to link LinkedIn/Twitter accounts at the beginning. It would populate automatically half of the fields. It is definitely annoying.

      Thank you! And a quick question: if I had added a "Skip" button in the onboarding, do you think that you would have ignored more input?

      1. 1

        I'm not sure! I mean, since I started the signup without the "intention" to use the application, I think I might've been more impatient with the inputs than people who find you organically?

        One helpful point might be that i don't remember my medium username or my linkedin url off-the-cuff so i didn't want to open a new tab to fill those in.

        1. 1

          If there's one thing that I learned so far, is that whatever happens, users are always impatient :D

          Yep not sure what would be the best solution to tackle this...

  2. 1

    The only suggestion I have is to keep you call to action (signup button) visible without scrolling. It’s probably fine on desktop but on mobile it was offscreen. It’s also good to remember that no matter how amazing your onboarding is, there will always be drop off for every step. So keep it short 😬

    1. 1

      Thanks for the feedback, I'll try to improve my mobile flow!

      Yes definitely, I'm still trying to figure out what data is important. Not easy to choose :)

  3. 1

    I like your use of magic links. Are you using a library or service for that? or is it a custom implementation

    1. 1

      I really like magic links too. It's nice to not have passwords to manage.

      I did it custom. I pretty much over engineered everything so far :)

      1. 1

        I pretty much over engineered everything so far :)

        I'm working on a magic link service, that also includes crypto based device auth to speed up subsequent authentication flow. Would you be interested in talking further about how magic links is working for you?

        By the way if you want to see an example of our flow you can try out forgetpasswords.com

        1. 1

          Nice!

          crypto based device auth to speed up subsequent authentication flow

          What do you mean by that? You would somehow do device fingerprinting? Interesting concept.

          1. 1

            Not fingerprinting, we use the webcrypto api supported by most browsers now. so we use a public/private keypair that the device keeps hold of

  4. 1

    This comment was deleted 4 years ago.

Trending on Indie Hackers
After 10M+ Views, 13k+ Upvotes: The Reddit Strategy That Worked for Me! 42 comments Getting first 908 Paid Signups by Spending $353 ONLY. 24 comments 🔥Roast my one-man design agency website 21 comments I talked to 8 SaaS founders, these are the most common SaaS tools they use 19 comments What are your cold outreach conversion rates? Top 3 Metrics And Benchmarks To Track 19 comments Hero Section Copywriting Framework that Converts 3x 12 comments