Why API integration connects to backends in React Native - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do mobile apps use API integration to connect to backends?

Choose the best reason why mobile apps connect to backend servers using APIs.

A To fetch and send data securely between the app and server

B To make the app run faster without internet

C To store all app data only on the device

D To avoid using any server resources

💡 Hint

Think about how apps get updated information or save user data.

APIs allow apps to communicate with backend servers to get or send data securely. This is essential for dynamic content and user data management.

❓ ui_behavior

intermediate

What happens in the app UI when API data is loading?

When a React Native app calls an API to get data, what should the UI show while waiting for the response?

A Show blank screen with no feedback

B Crash the app to restart

C Show a loading spinner or message

D Immediately show old data without update

💡 Hint

Think about how apps keep users informed during slow network calls.

Showing a loading spinner or message informs users that data is being fetched, improving user experience.

❓ lifecycle

advanced

When should a React Native app call backend APIs?

Which lifecycle event is best to trigger an API call to fetch data when a screen appears?

A Inside the component constructor

B Inside useEffect hook with empty dependency array

C Inside a button click handler only

D Inside the render method directly

💡 Hint

Think about when the component is ready and mounted.

Using useEffect with an empty dependency array runs the API call once after the component mounts, ideal for initial data fetch.

❓ navigation

advanced

How to pass API data between screens in React Native?

You fetched user info from backend on Screen A. How do you pass this data to Screen B when navigating?

A Use console.log to share data

B Store data only in Screen A state without passing

C Reload Screen B without any data

D Pass data as parameters in navigation.navigate call

💡 Hint

Think about how navigation libraries pass info between screens.

Passing data as parameters in navigation.navigate allows Screen B to receive and use the API data.

🔧 Debug

expert

Why does this React Native API call fail with 'Network request failed'?

Given this code snippet, why does the fetch fail?

fetch('http://localhost:3000/data')
  .then(response => response.json())
  .then(data => console.log(data))
  .catch(error => console.error(error))

A Mobile device cannot access localhost of development machine

B response.json() is not a function

C fetch requires POST method by default

D The URL is missing https:// prefix

💡 Hint

Think about what 'localhost' means on a mobile device.

On a mobile device, 'localhost' points to the device itself, not the development machine. The app cannot reach the backend server this way.

Practice

1. Why does a React Native app use API integration to connect to a backend server?

easy

A. To get or send data between the app and the server

B. To change the app's color scheme automatically

C. To increase the app's font size on the screen

D. To store data only on the user's device

Solution

1. Step 1: Understand the role of backend servers

   Backend servers store and manage data that apps need to access or update.

2. Step 2: Recognize API integration purpose

   API integration allows the app to communicate with the backend to get or send this data.

3. Final Answer:

   To get or send data between the app and the server -> Option A

4. Quick Check:

   API integration connects app and backend data [OK]

Hint: API integration moves data between app and server [OK]

Common Mistakes:

• Thinking API changes app design automatically
• Confusing local storage with backend data
• Believing API only changes UI elements

2. Which of the following is the correct way to fetch data from an API in React Native using async/await?

easy

A. const data = fetch('https://api.example.com/data').json();

B. const response = await fetch('https://api.example.com/data'); const data = await response.json();

C. fetch('https://api.example.com/data').then(response => response.text());

D. await fetch('https://api.example.com/data').json();

Solution

1. Step 1: Use fetch with await to get response

   fetch returns a promise; await waits for it to resolve to a response object.

2. Step 2: Use await on response.json() to parse JSON data

   response.json() returns a promise that resolves to the parsed data.

3. Final Answer:

   const response = await fetch('https://api.example.com/data'); const data = await response.json(); -> Option B

4. Quick Check:

   Use await twice: fetch and json() [OK]

Hint: Await fetch, then await response.json() [OK]

Common Mistakes:

• Calling json() directly on fetch without await
• Using response.text() instead of response.json()
• Missing await keyword causing unresolved promises

3. What will be logged to the console after this React Native code runs?

async function getData() {
  const response = await fetch('https://api.example.com/user');
  const user = await response.json();
  console.log(user.name);
}
getData();

medium

A. The entire user object printed as a string

B. undefined

C. An error because fetch is not awaited

D. The user's name from the API response

Solution

1. Step 1: Await fetch and parse JSON

   The code waits for the fetch call and parses the JSON response into the user object.

2. Step 2: Log the user's name property

   console.log prints the value of user.name from the parsed object.

3. Final Answer:

   The user's name from the API response -> Option D

4. Quick Check:

   Await fetch and json() gives user.name [OK]

Hint: Await fetch and json() before accessing data [OK]

Common Mistakes:

• Forgetting await causing unresolved promises
• Logging user instead of user.name
• Assuming fetch returns data directly without parsing

4. Identify the error in this React Native API call code:

async function fetchData() {
  const response = fetch('https://api.example.com/data');
  const data = await response.json();
  console.log(data);
}

medium

A. Using await on response.json() is incorrect

B. fetch URL is invalid syntax

C. Missing await before fetch causing response to be a promise

D. console.log should be inside a .then() block

Solution

1. Step 1: Check fetch call usage

   fetch returns a promise, so it must be awaited to get the response object.

2. Step 2: Identify consequence of missing await

   Without await, response is a promise, so calling response.json() causes an error.

3. Final Answer:

   Missing await before fetch causing response to be a promise -> Option C

4. Quick Check:

   Always await fetch before response.json() [OK]

Hint: Await fetch before calling response.json() [OK]

Common Mistakes:

• Assuming fetch returns data immediately
• Calling json() on a promise instead of response
• Misunderstanding async/await order

5. You want your React Native app to show updated weather data every time the user opens the app. Which approach best uses API integration to achieve this?

hard

A. Call the weather API inside a useEffect hook that runs on component mount

B. Store weather data once in a variable and never update it

C. Fetch weather data only when the user presses a button

D. Hardcode weather data in the app code

Solution

1. Step 1: Understand when to fetch updated data

   To get fresh data each time the app opens, fetch on component mount is ideal.

2. Step 2: Use React Native lifecycle with useEffect

   useEffect with empty dependency array runs once on mount, perfect for initial API call.

3. Final Answer:

   Call the weather API inside a useEffect hook that runs on component mount -> Option A

4. Quick Check:

   useEffect on mount fetches fresh data [OK]

Hint: Fetch data on mount with useEffect [OK]

Common Mistakes:

• Not updating data after first load
• Fetching only on user action missing auto updates
• Hardcoding data prevents real-time updates