Question
The Flutter check-in/check-out app is a new standalone client, but the backend today only exposes SvelteKit remote functions authenticated via Better-Auth's cookie session — not usable directly from a native mobile client. How does the Flutter app authenticate (token/API-key issued via Better-Auth, a dedicated mobile login flow, something else), and where does its API surface live — new +server.ts JSON endpoints alongside the existing remote functions, or a separate API layer? Should cover multi-org scoping (a user can belong to several orgs) since the existing web app already handles that via session + membership lookups.
Question
The Flutter check-in/check-out app is a new standalone client, but the backend today only exposes SvelteKit remote functions authenticated via Better-Auth's cookie session — not usable directly from a native mobile client. How does the Flutter app authenticate (token/API-key issued via Better-Auth, a dedicated mobile login flow, something else), and where does its API surface live — new
+server.tsJSON endpoints alongside the existing remote functions, or a separate API layer? Should cover multi-org scoping (a user can belong to several orgs) since the existing web app already handles that via session + membership lookups.