Your app gets real users — and you get the tools to run it
Your Bool can now have its own visitors, not just yours. Turn on accounts and every app gets sign up, sign in, and password reset — fully wired, with email/password and Google sign-in built in from the start. Ask for it by name and it just works: no auth code to write, no screen to design from scratch. Once your app has real users, you need to run it like one: today's release also gives you the dashboard to watch them arrive and the API to reach their data.
First, a sign-in screen that's yours to restyle
Every app comes with a ready-made sign-in screen — restyle its layout, colors, and copy to match your app while the sign-in logic underneath keeps working untouched.
Then decide how much of your app it guards
Wrap a page, a feature, or the whole app behind sign-in — just ask, and Bool decides where accounts make sense so you don't get a login wall you didn't need.
And every visitor's data stays their own
Each signed-in visitor only ever sees their own rows — notes, orders, saved items, whatever your app stores — automatically kept separate from everyone else's. Sign-ups in one Bool never show up in another, so each app has its own visitor list.
Watch them arrive in Analytics and Logs
Two new tabs in your project dashboard show you what those users are doing. Analytics gives you visits, unique and live visitors, and a chart of traffic over time you can zoom to 24h, 7d, 30d, or 90d, plus breakdowns by top pages, country, referrer, OS, device, and browser. Logs gives you a request-by-request trail you can filter by date range, event kind, or success/error status — and now that your visitors have accounts, you can click any one of them to see just their activity.
Reach their data from anywhere with the API
A third new tab lists every one of your data models with ready-to-paste code snippets and a REST endpoint, so you can call your app's data from outside your app. Accounts carry through here too: each person who signs in can grab a personal API key that acts as them, so external calls only ever see what that user is allowed to see.
