Firebase Authentication in Android Kotlin - Build, Publish & Deploy

Build & Publish - Firebase Authentication

Performance Impact of Firebase Authentication

Firebase Authentication adds network calls to your app for user sign-in and token refresh. These calls can cause slight delays but usually do not affect frame rate if handled asynchronously. Memory usage is minimal, mostly for storing user session data. Battery impact is low since authentication happens infrequently, typically at app start or user action.

💻

How to Optimize Firebase Authentication for 60fps Rendering

Use asynchronous calls with Kotlin coroutines or callbacks to avoid blocking the main thread. Cache user credentials securely to reduce repeated sign-ins. Avoid heavy UI updates during authentication. Show simple loading indicators to keep UI responsive. Use Firebase's built-in token refresh to maintain session without user interruption.

Impact on App Bundle Size and Startup Time

Adding Firebase Authentication increases your app size by about 2-5MB depending on dependencies. This is moderate and acceptable for most apps. Startup time impact is minimal if authentication is done after initial UI loads. Use ProGuard or R8 to shrink unused Firebase code and reduce size.

iOS vs Android Differences for Firebase Authentication

Both platforms use Firebase SDKs but with platform-specific APIs (Swift for iOS, Kotlin for Android). iOS requires configuring GoogleService-Info.plist, Android uses google-services.json. iOS apps must handle Sign in with Apple if used, Android handles Google Sign-In differently. Both require proper OAuth client setup in Firebase Console.

Relevant Store Review Guidelines and Requirements

• Ensure user privacy by following Apple App Store and Google Play policies on data collection and user consent.
• Implement secure authentication flows to prevent unauthorized access.
• Provide clear user-facing privacy policies explaining authentication data use.
• For Apple, support Sign in with Apple if your app offers third-party sign-in options.
• Comply with GDPR and other regional regulations if your app targets those users.

Self-Check: Your App Takes 5 Seconds to Load This Screen. What's Likely Wrong?

Likely your app is performing Firebase Authentication synchronously on the main thread, blocking UI rendering. Or you may be waiting for network calls without showing progress. To fix, move authentication calls off the main thread, use asynchronous patterns, and show a loading indicator to keep UI responsive.

Key Result

Firebase Authentication adds minimal memory and battery load but requires asynchronous handling to keep UI smooth. It moderately increases app size by a few MB. Platform setup differs between iOS and Android, especially for sign-in methods. Follow store privacy and security guidelines carefully.

Practice

1. What is the main purpose of Firebase Authentication in an Android app?

easy

A. To store user data in a database

B. To send push notifications to users

C. To design the app's user interface

D. To securely manage user sign-in and registration

Solution

1. Step 1: Understand Firebase Authentication role

   Firebase Authentication is designed to handle user sign-in and registration securely.

2. Step 2: Differentiate from other Firebase services

   It does not store user data (that's Firestore/Realtime Database), nor handle UI design or notifications.

3. Final Answer:

   To securely manage user sign-in and registration -> Option D

4. Quick Check:

   Firebase Authentication = Secure sign-in [OK]

Hint: Remember Firebase Auth is for user sign-in only [OK]

Common Mistakes:

• Confusing Authentication with database storage
• Thinking it handles UI design
• Assuming it manages notifications

2. Which Kotlin code snippet correctly registers a new user with email and password using Firebase Authentication?

easy

A. firebaseAuth.registerUser(email, password).addOnCompleteListener { ... }

B. firebaseAuth.signInWithEmailAndPassword(email, password).addOnCompleteListener { ... }

C. firebaseAuth.createUserWithEmailAndPassword(email, password).addOnCompleteListener { ... }

D. firebaseAuth.createUser(email, password).addOnCompleteListener { ... }

Solution

1. Step 1: Identify correct Firebase method for registration

   The method to register a new user is createUserWithEmailAndPassword(email, password).

2. Step 2: Check method names in options

   registerUser and createUser do not exist. signInWithEmailAndPassword is for signing in existing users, not registration.

3. Final Answer:

   firebaseAuth.createUserWithEmailAndPassword(email, password).addOnCompleteListener { ... } -> Option C

4. Quick Check:

   Register new user = createUserWithEmailAndPassword [OK]

Hint: Register uses createUserWithEmailAndPassword method [OK]

Common Mistakes:

• Using signInWithEmailAndPassword to register
• Using non-existent methods like createUser or registerUser
• Confusing method names

3. Given this Kotlin code snippet, what will be printed if the user is signed in?

val user = firebaseAuth.currentUser
if (user != null) {
    println("User is signed in")
} else {
    println("No user signed in")
}

medium

A. User is signed in

B. NullPointerException error

C. No user signed in

D. Compilation error

Solution

1. Step 1: Understand currentUser property

   firebaseAuth.currentUser returns the current signed-in user or null if none.

2. Step 2: Analyze the if condition

   If user is not null, it prints "User is signed in"; otherwise, "No user signed in".

3. Final Answer:

   User is signed in -> Option A

4. Quick Check:

   currentUser != null means user signed in [OK]

Hint: currentUser null means no user; else signed in [OK]

Common Mistakes:

• Assuming currentUser throws error if null
• Confusing sign-in check logic
• Expecting compilation errors incorrectly

4. Identify the error in this Kotlin code for signing out a user:

firebaseAuth.signOut
println("User signed out")

medium

A. signOut is not a FirebaseAuth method

B. Missing parentheses after signOut method

C. println should be inside a callback

D. No error, code is correct

Solution

1. Step 1: Check signOut method usage

   signOut is a method and requires parentheses: signOut()

2. Step 2: Verify other options

   signOut exists in FirebaseAuth; println can be outside callback; so only missing parentheses is error.

3. Final Answer:

   Missing parentheses after signOut method -> Option B

4. Quick Check:

   signOut() needs parentheses [OK]

Hint: Methods need () even if no parameters [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Thinking signOut is a property
• Assuming println must be in callback

5. You want to create a function in Kotlin that registers a user and then immediately signs them in using Firebase Authentication. Which code snippet correctly does this?

hard

A. firebaseAuth.createUserWithEmailAndPassword(email, password).addOnCompleteListener { task -> if (task.isSuccessful) { println("User registered and signed in") } }

B. firebaseAuth.signInWithEmailAndPassword(email, password).addOnCompleteListener { task -> if (task.isSuccessful) { println("User registered and signed in") } }

C. firebaseAuth.createUserWithEmailAndPassword(email, password).addOnCompleteListener { task -> if (task.isSuccessful) { firebaseAuth.signInWithEmailAndPassword(email, password) } }

D. firebaseAuth.createUserWithEmailAndPassword(email, password).addOnCompleteListener { task -> if (task.isSuccessful) { firebaseAuth.signOut() } }

Solution

1. Step 1: Understand createUserWithEmailAndPassword behavior

   This method registers and automatically signs in the user if successful.

2. Step 2: Analyze options for correct flow

   createUserWithEmailAndPassword(...).addOnCompleteListener { task -> if (task.isSuccessful) { println("User registered and signed in") } } registers and confirms success. signInWithEmailAndPassword only signs in existing users. Calling signIn after createUser is redundant. Calling signOut after is incorrect.

3. Final Answer:

   firebaseAuth.createUserWithEmailAndPassword(email, password).addOnCompleteListener { task -> if (task.isSuccessful) { println("User registered and signed in") } } -> Option A

4. Quick Check:

   Registration auto signs in [OK]

Hint: Register auto signs in; no need to call signIn after [OK]

Common Mistakes:

• Calling signIn after createUserWithEmailAndPassword unnecessarily
• Using signIn without registering first
• Signing out immediately after registration