Remix.run Logo
jackfranklyn 16 hours ago

The onboarding lesson is one I had to learn the hard way too. When you build something for yourself, you forget that nobody else has the mental model you do. "Figure it out yourself" feels fine when you're the user, but it's death for retention.

Also resonates with the "product first" approach. Starting with a real problem you actually have - and then following where the tech decisions naturally lead - seems to produce better outcomes than starting with "I want to build something in X framework."

The QR sharing feature is a nice touch. Physical sharing had something going for it that we lost when everything went digital - that friction-free "here, try this" moment. Recreating that digitally is harder than it sounds.

oliverjanssen 16 hours ago | parent [-]

Thanks!

Exactly. The mental model thing is brutal. You know every corner of the app, so everything feels obvious. Then you watch someone use it for the first time and they're completely lost. Need to do that more often, perfect way to learn.

And yes - QR sharing was about bringing back that "here, just take it" moment. Sending library export as JSON, explaining how to import... too much friction. Scan and done feels right.

recursivecaveat 11 hours ago | parent [-]

The mental model is usually what I want most (and often find missing) from onboarding. If you give me the model and vocabulary I can find the buttons myself. If you teach me 1 workflow I'm probably helpless at doing anything else.

oliverjanssen 7 hours ago | parent [-]

100%. The goal shifted from "show where buttons are" to "explain what this app is for." Once parents get the player vs admin concept, everything else clicks.