Expo vs bare React Native - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Expo Managed Workflow

Which statement best describes the Expo managed workflow in React Native development?

A It allows you to write React Native apps without configuring native code, using Expo's tools and services.

B It requires manual setup of native iOS and Android projects before coding.

C It only supports Android development and excludes iOS.

D It forces you to eject your app to use any third-party native modules.

💡 Hint

Think about which workflow hides native code complexity.

Expo managed workflow provides a ready-to-use environment where you write JavaScript and use Expo's APIs without touching native code.

❓ ui_behavior

intermediate

Behavior Differences in Native Module Usage

You want to use a native module not supported by Expo. What happens if you try to use it in an Expo managed project without ejecting?

A The app will fail to build or run because Expo managed workflow does not support custom native modules.

B Expo automatically converts native modules to JavaScript equivalents.

C The app will build and run normally with the native module working.

D The native module will work only on Android but not on iOS.

💡 Hint

Consider Expo's limitations on native code.

Expo managed workflow does not allow adding custom native code, so unsupported native modules cause build failures.

❓ lifecycle

advanced

App Lifecycle Differences

How does the app lifecycle management differ between Expo managed and bare React Native projects?

A Both Expo managed and bare React Native apps require manual native lifecycle event handling.

B Expo managed apps handle lifecycle events internally, while bare React Native apps require manual native lifecycle handling.

C Bare React Native apps have no lifecycle events, unlike Expo managed apps.

D Expo managed apps do not support lifecycle events at all.

💡 Hint

Think about who manages native lifecycle in each workflow.

Expo managed workflow abstracts native lifecycle, while bare React Native requires developers to handle native lifecycle events if needed.

❓ navigation

advanced

Navigation Setup Differences

Which is true about navigation setup in Expo managed vs bare React Native projects?

A Expo managed projects require manual native linking for navigation libraries.

B Bare React Native projects cannot use React Navigation.

C Expo managed projects can use React Navigation without extra native linking, while bare React Native may require manual linking for some navigation dependencies.

D Navigation libraries are not supported in Expo managed projects.

💡 Hint

Consider how Expo handles native dependencies.

Expo managed workflow includes prebuilt native code for popular libraries like React Navigation, avoiding manual linking.

🔧 Debug

expert

Debugging Build Failures in Bare React Native

You ejected from Expo to bare React Native and now your iOS build fails with a native module error. What is the most likely cause?

A Expo managed workflow does not support native modules, so this error is unrelated.

B You must remove all native modules to build successfully.

C You need to reinstall Expo CLI globally to fix native module errors.

D You forgot to run 'pod install' in the ios directory after adding native modules.

💡 Hint

Think about native dependencies setup after ejecting.

After ejecting, native modules require proper linking and installation steps like 'pod install' for iOS to build correctly.