Why Firebase provides mobile backend services in iOS Swift - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Firebase module in Swift.

iOS Swift

import [1]

Drag options to blanks, or click blank then click option'

AFirebase

BUIKit

CFoundation

DSwiftUI

Attempts:

3 left

💡 Hint

Common Mistakes

Importing UIKit instead of Firebase

Forgetting to import Firebase

Firebase is imported using import Firebase to access its backend services.

2fill in blank

medium

Complete the code to initialize Firebase in the AppDelegate's didFinishLaunchingWithOptions method.

iOS Swift

FirebaseApp.[1]()

Drag options to blanks, or click blank then click option'

Aconfigure

Bstart

Cinitialize

Dlaunch

Attempts:

3 left

💡 Hint

Common Mistakes

Using start() or initialize() instead of configure()

Not calling FirebaseApp.configure() at all

Firebase is initialized by calling FirebaseApp.configure() in the app launch method.

3fill in blank

hard

Fix the error in the code to save data to Firestore database.

iOS Swift

let db = Firestore.firestore()
db.collection("users").document("user1").setData([1])

Drag options to blanks, or click blank then click option'

A("name": "Alice", "age": 25)

B["name": "Alice", "age": 25]

C["name" => "Alice", "age" => 25]

D[name: "Alice", age: 25]

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses instead of square brackets

Omitting quotes around keys

Using => instead of : for key-value pairs

Firestore expects a dictionary with keys as strings and values, so use ["name": "Alice", "age": 25].

4fill in blank

hard

Fill both blanks to read data from Firestore and print the user's name.

iOS Swift

let db = Firestore.firestore()
db.collection("users").document("user1").getDocument { (document, error) in
  if let document = document, document.exists {
    let data = document.[1]()
    print(data[[2]] as? String ?? "No name")
  }
}

Drag options to blanks, or click blank then click option'

Adata

BgetData

C"name"

DdocumentData

Attempts:

3 left

💡 Hint

Common Mistakes

Using getData() instead of data()

Not quoting the dictionary key

Use data() to get the document data dictionary, then access the "name" key.

5fill in blank

hard

Fill all three blanks to authenticate a user with email and password using Firebase Auth.

iOS Swift

Auth.auth().[1](withEmail: [2], password: [3]) { authResult, error in
  if let error = error {
    print("Error: \(error.localizedDescription)")
  } else {
    print("User signed in")
  }
}

Drag options to blanks, or click blank then click option'

AsignIn

B"[e-mail]"

C"password123"

DcreateUser

Attempts:

3 left

💡 Hint

Common Mistakes

Using createUser instead of signIn

Not passing email and password as strings

Use signIn method with email and password strings to sign in a user.

Practice

1. Why do mobile developers use Firebase as a backend service?

easy

A. Because it requires building all backend code from scratch

B. Because it only works with web apps, not mobile apps

C. Because it provides ready-to-use backend features like data storage and user authentication

D. Because it is only for storing images, not data

Solution

1. Step 1: Understand Firebase's purpose

   Firebase offers backend services like data storage, authentication, and real-time updates to simplify app development.

2. Step 2: Compare options with Firebase features

   Because it provides ready-to-use backend features like data storage and user authentication correctly states Firebase provides ready backend features, unlike options B, C, and D which are incorrect.

3. Final Answer:

   Because it provides ready-to-use backend features like data storage and user authentication -> Option C

4. Quick Check:

   Firebase backend features = Ready-to-use services [OK]

Hint: Firebase saves time by offering ready backend tools [OK]

Common Mistakes:

• Thinking Firebase only works for web apps
• Believing you must write all backend code yourself
• Confusing Firebase as only an image storage service

2. Which Swift code snippet correctly initializes Firebase in an iOS app?

easy

A. FirebaseApp.configure()

B. Firebase.initialize()

C. Firebase.start()

D. Firebase.setup()

Solution

1. Step 1: Recall Firebase initialization method in Swift

   The official method to initialize Firebase in Swift is FirebaseApp.configure().

2. Step 2: Check other options for correctness

   Options A, B, and D are not valid Firebase initialization methods in Swift.

3. Final Answer:

   FirebaseApp.configure() -> Option A

4. Quick Check:

   Firebase initialization = FirebaseApp.configure() [OK]

Hint: Use FirebaseApp.configure() to start Firebase in Swift [OK]

Common Mistakes:

• Using incorrect method names like initialize or start
• Forgetting to call configure before using Firebase features
• Confusing Firebase initialization with other libraries

3. Given this Swift code using Firebase Realtime Database:

let ref = Database.database().reference()
ref.child("messages").setValue(["Hello", "World"])
ref.child("messages").observe(.value) { snapshot in
  if let messages = snapshot.value as? [String] {
    print(messages.joined(separator: ", "))
  }
}

What will be printed in the console?

medium

A. Hello, World

B. ["Hello", "World"]

C. messages

D. Error: Cannot cast snapshot value

Solution

1. Step 1: Understand the data set and observe method

   The code sets the "messages" child to an array ["Hello", "World"] and observes changes to print them.

2. Step 2: Analyze the print statement inside the observer

   The snapshot value is cast to [String], then joined with ", ", resulting in "Hello, World" printed.

3. Final Answer:

   Hello, World -> Option A

4. Quick Check:

   Firebase data read = "Hello, World" [OK]

Hint: Observe returns data; joined array prints as comma-separated string [OK]

Common Mistakes:

• Expecting raw array print instead of joined string
• Confusing snapshot key with value
• Assuming a type cast error without checking data type

4. You wrote this Swift code to authenticate a user with Firebase:

Auth.auth().signIn(withEmail: email, password: password) { authResult, error in
  if error != nil {
    print("Login failed")
  } else {
    print("Login successful")
  }
}

But the app always prints "Login failed" even with correct credentials. What is the likely issue?

medium

A. Firebase does not support email/password login

B. The email and password variables are not declared

C. The print statements are reversed

D. FirebaseApp.configure() was not called before authentication

Solution

1. Step 1: Check Firebase initialization requirement

   Firebase must be initialized with FirebaseApp.configure() before using authentication features.

2. Step 2: Understand effect of missing initialization

   If not initialized, authentication calls fail silently, causing error to be non-nil and printing "Login failed".

3. Final Answer:

   FirebaseApp.configure() was not called before authentication -> Option D

4. Quick Check:

   Firebase initialization missing = Login fails [OK]

Hint: Always call FirebaseApp.configure() before auth calls [OK]

Common Mistakes:

• Assuming variable declaration causes login failure
• Thinking print statements are swapped
• Believing Firebase lacks email/password support

5. You want to build a chat app using Firebase that updates messages in real-time. Which combination of Firebase features should you use to achieve this?

hard

A. Cloud Storage for storing messages and Analytics for tracking users

B. Realtime Database for live data updates and Authentication for user sign-in

C. Firestore for storing images and Remote Config for UI changes

D. Crashlytics for error reporting and Performance Monitoring for speed

Solution

1. Step 1: Identify Firebase features for real-time data and user management

   Realtime Database provides live data syncing; Authentication manages user sign-in.

2. Step 2: Evaluate other options for relevance

   Options B, C, and D mention features unrelated to real-time chat and user authentication.

3. Final Answer:

   Realtime Database for live data updates and Authentication for user sign-in -> Option B

4. Quick Check:

   Realtime chat needs Realtime Database + Authentication [OK]

Hint: Use Realtime Database plus Authentication for live chat apps [OK]

Common Mistakes:

• Choosing Cloud Storage instead of Realtime Database for messages
• Confusing Analytics or Crashlytics as backend services
• Ignoring user authentication needs