Location services in React Native - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of location services in a mobile app?

Location services allow an app to get the device's current position, like latitude and longitude, to provide location-based features such as maps, navigation, or nearby places.

beginner

Which React Native API is commonly used to access the device's location?

The Geolocation API or the @react-native-community/geolocation package is used to get the device's current position in React Native.

beginner

Why do you need to ask for permission before accessing location in a mobile app?

Because location data is private and sensitive, apps must ask the user for permission to access it. This protects user privacy and follows platform rules.

intermediate

What is the difference between 'getCurrentPosition' and 'watchPosition' in location services?

getCurrentPosition gets the device's location once. watchPosition keeps tracking location changes over time and updates continuously.

intermediate

How can you improve battery life when using location services in a React Native app?

Use location updates only when needed, prefer less frequent updates, choose lower accuracy if possible, and stop watching location when not required.

Which permission is typically required to access location on Android devices?

A INTERNET

B READ_CONTACTS

C ACCESS_FINE_LOCATION

D WRITE_EXTERNAL_STORAGE

ACCESS_FINE_LOCATION permission allows apps to access precise location on Android.

In React Native, which method gets the device's current location only once?

A getCurrentPosition

B watchPosition

C startLocationUpdates

D subscribeLocation

getCurrentPosition fetches the location once, while watchPosition listens continuously.

What should you do if the user denies location permission in your app?

A Keep requesting permission repeatedly

B Show a message explaining why location is needed and disable location features

C Ignore and continue accessing location

D Force close the app

Respect user choice, explain why location is needed, and disable related features gracefully.

Which of these is a good practice to save battery when using location services?

A Stop location updates when not needed

B Use high accuracy location always

C Keep location tracking running in background indefinitely

D Request location every second

Stopping location updates when not needed helps save battery.

What does the 'watchPosition' method do in location services?

A Gets location once

B Requests permission

C Stops location tracking

D Tracks location changes continuously

watchPosition listens for location changes and updates continuously.

Explain how to request and use location permissions in a React Native app.

Think about asking the user first, then getting location if allowed.

Describe the difference between getting location once and tracking location continuously. When would you use each?

Consider a map app showing current location vs a running app tracking movement.

Practice

1. What is the main purpose of using Geolocation.getCurrentPosition in a React Native app?

easy

A. To display a map on the screen

B. To continuously track the user's location

C. To request permission for location access

D. To get the user's current location once

Solution

1. Step 1: Understand the function purpose

   Geolocation.getCurrentPosition is designed to get the user's location only once when called.

2. Step 2: Differentiate from continuous tracking

   Continuous tracking uses watchPosition, not getCurrentPosition.

3. Final Answer:

   To get the user's current location once -> Option D

4. Quick Check:

   Single location fetch = getCurrentPosition [OK]

Hint: Get current location once with getCurrentPosition [OK]

Common Mistakes:

• Confusing getCurrentPosition with watchPosition
• Thinking it requests permissions automatically
• Assuming it tracks location continuously

2. Which of the following is the correct syntax to request the user's current location in React Native?

easy

A. navigator.location.getCurrentPosition(successCallback);

B. Geolocation.watchPosition(successCallback, errorCallback);

C. Geolocation.getCurrentPosition(successCallback, errorCallback);

D. Location.getPosition(successCallback, errorCallback);

Solution

1. Step 1: Identify correct API usage

   The correct React Native API call for one-time location is Geolocation.getCurrentPosition with success and error callbacks.

2. Step 2: Eliminate incorrect options

   watchPosition is for continuous tracking, navigator.location and Location.getPosition are not valid React Native APIs.

3. Final Answer:

   Geolocation.getCurrentPosition(successCallback, errorCallback); -> Option C

4. Quick Check:

   Correct method and parameters = Geolocation.getCurrentPosition(successCallback, errorCallback); [OK]

Hint: Use getCurrentPosition with success and error callbacks [OK]

Common Mistakes:

• Using watchPosition for one-time location
• Using browser navigator API in React Native
• Incorrect method names or missing callbacks

3. What will be the output of the following code snippet in a React Native app if location permission is granted and location is successfully fetched?

Geolocation.getCurrentPosition(
  position => console.log(position.coords.latitude),
  error => console.log(error.message)
);

medium

A. Logs the user's latitude coordinate as a number

B. Logs the error message string

C. Throws a syntax error

D. Logs the entire position object

Solution

1. Step 1: Analyze success callback

   The success callback logs position.coords.latitude, which is a number representing latitude.

2. Step 2: Understand error callback usage

   The error callback logs error messages only if permission is denied or fetching fails, which is not the case here.

3. Final Answer:

   Logs the user's latitude coordinate as a number -> Option A

4. Quick Check:

   Success callback logs latitude number [OK]

Hint: Success callback logs latitude, error callback logs error [OK]

Common Mistakes:

• Expecting entire position object logged
• Confusing error callback with success callback
• Assuming syntax error due to arrow functions

4. Identify the error in this React Native code snippet for tracking location changes:

const watchId = Geolocation.watchPosition(
  position => console.log(position.coords.longitude),
  error => console.log(error.message)
);
Geolocation.clearWatch(watchId);

medium

A. Error callback should be first argument

B. clearWatch is called immediately, stopping tracking instantly

C. watchPosition requires a third parameter for options

D. watchPosition does not return a watchId

Solution

1. Step 1: Understand watchPosition behavior

   watchPosition starts tracking and returns a watchId to stop it later.

2. Step 2: Analyze clearWatch usage

   Calling clearWatch(watchId) immediately after starting tracking stops it right away, so no updates will be received.

3. Final Answer:

   clearWatch is called immediately, stopping tracking instantly -> Option B

4. Quick Check:

   Immediate clearWatch stops tracking [OK]

Hint: Don't clearWatch immediately after watchPosition [OK]

Common Mistakes:

• Calling clearWatch too soon
• Mixing argument order in watchPosition
• Assuming watchPosition returns nothing

5. You want to build a React Native app that tracks the user's location continuously but only updates the UI when the user moves more than 50 meters. Which approach is best to implement this efficiently?

hard

A. Use watchPosition with distanceFilter: 50 option to limit updates

B. Use getCurrentPosition repeatedly every second with a timer

C. Use watchPosition without options and filter distance manually in callback

D. Request location once and update UI only if user moves manually

Solution

1. Step 1: Understand continuous tracking with filtering

   watchPosition supports options like distanceFilter to update only when user moves a set distance, saving resources.

2. Step 2: Compare other options

   Using getCurrentPosition repeatedly wastes battery and CPU. Filtering manually after every update is less efficient. Requesting location once won't track movement.

3. Final Answer:

   Use watchPosition with distanceFilter: 50 option to limit updates -> Option A

4. Quick Check:

   distanceFilter option limits updates efficiently [OK]

Hint: Use distanceFilter option with watchPosition for efficient updates [OK]

Common Mistakes:

• Polling location repeatedly with getCurrentPosition
• Ignoring distanceFilter and filtering manually
• Requesting location only once for continuous tracking