Native APIs for React Natives
Native APIs are the device capabilities a React Native app can reach, such as camera, location, notifications, sensors and file storage, plus the animation and gesture systems used for smooth interfaces. They are exposed through Expo modules or community libraries, and most need runtime permission from the user before they work.
Stage: Device Features · Part of the React Native roadmap · Last reviewed 19 November 2026
What to learn in Native APIs
- Request and handle runtime permissions for camera and location
- Read the device position with expo-location and handle denial
- Schedule and receive local and push notifications
- Animate values with Reanimated using shared values on the UI thread
- Attach pan and swipe gestures with react-native-gesture-handler
Native APIs interview questions
Why is Reanimated preferred over the core Animated API for complex gestures?
Reanimated runs animation logic as worklets on the UI thread, so animations keep running even when the JavaScript thread is busy. That avoids dropped frames during gestures. The core Animated API can use the native driver for some properties but is more limited.
How should an app behave when the user denies a permission?
It should keep working where possible and explain what is lost. Check the permission status before use, show a clear message, and offer a button that opens system settings. On many platforms a second system prompt may not appear after a denial, so do not rely on re-asking.
Where Native APIs fits in the React Native roadmap
Native APIs belongs to the Device Features stage (intermediate level), which takes about 19 hours. Native power.
Other units in this stage
Back to the full React Native roadmap