Accounts and sign-in
How people sign in to your app, what is supported, and how to check that data is separated properly.
Most apps need accounts. If yours does, say so when asked during Make it real, and it is built in.
What is supported
| Method | Notes |
|---|---|
| Email and password | The default |
| One-time code by email | A code instead of a password |
| Google sign-in | Works on both platforms |
| Apple sign-in | Available; Apple requires it on iPhone apps that offer other social sign-ins |
Sign-in works identically in a phone preview and an installed build, so you can test the whole flow before shipping anything.
Where sign-in screens come from
The sign-in and sign-up screens, and the splash screen, are built by Mistflow directly rather than generated fresh per app. They are also protected from later edits.
That is deliberate. Sign-in is the one screen where a small mistake locks every user out of the app, and it is the screen with the least design upside. You can restyle it; the mechanics stay intact.
Who can see what
When your app has accounts, it also has an owner: someone who can see across users. What each role can see is one of the questions asked at build time, and it is worth answering carefully.
Test it directly: sign in as a second person and confirm you cannot see the first one's records. Do not assume separation because the screens look right.
Managing the people using your app
Every project gets user administration in the dashboard, independent of what your app offers. You can:
- See everyone who has signed up
- Ban and unban someone
- Revoke a session, signing that device out
Alongside it are analytics and a read-only data browser for the app's own data. These are Mistflow's operator tools over any project, not something your app has to build.
If the people running your app need their own screens, that is the owner console, a separate web surface over the same data.
First-run experience
You are always signed in, which makes it easy to ship an app whose sign-up flow is broken. Before showing anyone the app, sign out and walk the full path: sign-up, first screen, first useful action. Every build is run through that path automatically on an emulator, but your own pass catches things a script cannot judge.