When Your Android App Doesn't Need a Login Screen

Firebase Authentication gets reached for by default on most new Android projects, but it's worth asking first whether the app actually needs identity — not just whether it's easy to add. For a learning app aimed at students who want to start practicing immediately, an account wall in front of the first quiz is friction with no clear payoff.

Our approach: keep Firebase in the stack for what it's genuinely good at in this context — Crashlytics for crash visibility and FCM for push notifications — without introducing Auth until there's a real feature that needs it, like cross-device progress sync. Bolting on authentication later is a smaller job than most teams expect if the app's data layer is already structured around a stable local identifier rather than assuming a server-issued user ID from day one.

When Auth does become necessary, the pattern we'd reach for is anonymous authentication first — giving every install a Firebase UID immediately, invisibly — with an optional upgrade path to email or phone sign-in later. It preserves progress across the upgrade without ever forcing a decision before the user has seen any value.