Turbo Modules overview in React Native - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import a Turbo Module in React Native.

React Native

import { [1] } from 'react-native';

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

AuseState

BView

CTurboModuleRegistry

DNativeModules

Attempts:

3 left

💡 Hint

Common Mistakes

Using NativeModules instead of TurboModuleRegistry

Importing unrelated hooks like useState

Turbo Modules are accessed via TurboModuleRegistry in React Native.

2fill in blank

medium

Complete the code to get a Turbo Module named 'MyModule'.

React Native

const myModule = [1].get('MyModule');

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

ANativeModules

BReact

CModuleRegistry

DTurboModuleRegistry

Attempts:

3 left

💡 Hint

Common Mistakes

Using NativeModules.get instead of TurboModuleRegistry.get

Trying to call get on React or ModuleRegistry which don't exist

TurboModuleRegistry.get('MyModule') returns the Turbo Module instance.

3fill in blank

hard

Fix the error in the Turbo Module method call to get a string result.

React Native

const result = await myModule.[1]();

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

AfetchData

Bfetch_data

CFetchData

Dfetchdata

Attempts:

3 left

💡 Hint

Common Mistakes

Using snake_case or incorrect capitalization

Calling a method name that does not exist

Method names in Turbo Modules use camelCase like 'fetchData'.

4fill in blank

hard

Fill both blanks to define a Turbo Module interface with a method returning a Promise.

React Native

export interface [1] {
  [2](): Promise<string>;
}

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

AMyTurboModule

BfetchData

CgetData

DMyModule

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect interface or method names

Not returning a Promise in the method signature

The interface name is 'MyTurboModule' and method 'fetchData' returns a Promise.

5fill in blank

hard

Fill all three blanks to register a Turbo Module in native code (TypeScript style).

React Native

import { TurboModuleRegistry } from 'react-native';

const [1] = TurboModuleRegistry.get<[2]>('[3]');

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

AmyModule

BMyTurboModule

CMyModule

DTurboModule

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up interface and variable names

Using wrong string name for the module

We assign the module to 'myModule', use interface 'MyTurboModule', and get 'MyModule' by name.

Practice

1. What is the main purpose of Turbo Modules in React Native?

easy

A. To speed up communication between JavaScript and native code

B. To create UI components faster

C. To manage app navigation

D. To handle network requests

Solution

1. Step 1: Understand Turbo Modules role

   Turbo Modules are designed to improve the speed of interaction between JavaScript and native code in React Native apps.

2. Step 2: Compare with other options

   Creating UI components, managing navigation, and handling network requests are not the primary goals of Turbo Modules.

3. Final Answer:

   To speed up communication between JavaScript and native code -> Option A

4. Quick Check:

   Turbo Modules = Faster JS-native communication [OK]

Hint: Turbo Modules speed up JS and native code talking [OK]

Common Mistakes:

• Confusing Turbo Modules with UI components
• Thinking Turbo Modules handle navigation
• Assuming Turbo Modules manage network

2. Which of the following is the correct way to access a Turbo Module named MyModule in React Native?

easy

A. const myModule = ModulesRegistry.get('MyModule');

B. const myModule = NativeModules.get('MyModule');

C. const myModule = TurboModule.get('MyModule');

D. const myModule = TurboModuleRegistry.get('MyModule');

Solution

1. Step 1: Recall correct API usage

   The official way to access Turbo Modules is using TurboModuleRegistry.get('ModuleName').

2. Step 2: Eliminate incorrect options

   NativeModules.get and TurboModule.get are not valid methods. ModulesRegistry does not exist.

3. Final Answer:

   const myModule = TurboModuleRegistry.get('MyModule'); -> Option D

4. Quick Check:

   Use TurboModuleRegistry.get() to access Turbo Modules [OK]

Hint: Use TurboModuleRegistry.get('Name') to access modules [OK]

Common Mistakes:

• Using NativeModules instead of TurboModuleRegistry
• Calling non-existent get methods
• Mixing up module registry names

3. What will happen if you try to access a Turbo Module that does not exist using TurboModuleRegistry.get('UnknownModule')?

medium

A. It returns null or undefined

B. It throws a syntax error

C. It crashes the app immediately

D. It returns an empty object

Solution

1. Step 1: Understand TurboModuleRegistry behavior

   If the requested module does not exist, TurboModuleRegistry.get() returns null or undefined instead of throwing errors.

2. Step 2: Check other options

   No syntax error or immediate crash occurs. It does not return an empty object either.

3. Final Answer:

   It returns null or undefined -> Option A

4. Quick Check:

   Missing Turbo Module returns null/undefined [OK]

Hint: Missing Turbo Modules return null or undefined [OK]

Common Mistakes:

• Expecting a syntax error
• Assuming app crashes immediately
• Thinking it returns empty object

4. You wrote const myModule = TurboModuleRegistry.get('MyModule') but get an error saying TurboModuleRegistry is not defined. What is the likely cause?

medium

A. Turbo Modules are not supported on your device

B. You misspelled the module name in get()

C. You forgot to import TurboModuleRegistry from 'react-native'

D. You need to call TurboModuleRegistry as a function

Solution

1. Step 1: Analyze the error message

   The error TurboModuleRegistry is not defined means the variable or object is not available in the current scope.

2. Step 2: Identify common cause

   This usually happens if you forget to import TurboModuleRegistry from the React Native package.

3. Final Answer:

   You forgot to import TurboModuleRegistry from 'react-native' -> Option C

4. Quick Check:

   Missing import causes 'not defined' error [OK]

Hint: Always import TurboModuleRegistry before use [OK]

Common Mistakes:

• Assuming misspelled module name causes 'not defined'
• Thinking device support causes 'not defined'
• Trying to call TurboModuleRegistry as a function

5. You want to improve your React Native app's performance by using Turbo Modules. Which of the following steps should you take to correctly implement and access a Turbo Module named FastLogger?

hard

A. Use NativeModules.FastLogger without any native Turbo Module implementation

B. Implement native code for FastLogger, export it as a Turbo Module, then access it via TurboModuleRegistry.get('FastLogger')

C. Write FastLogger only in JavaScript and import it normally

D. Create FastLogger as a React component and use it in JSX

Solution

1. Step 1: Understand Turbo Module implementation

   Turbo Modules require native code implementation and exporting as a Turbo Module to gain performance benefits.

2. Step 2: Access Turbo Module correctly

   After native implementation, access the module in JavaScript using TurboModuleRegistry.get('FastLogger').

3. Step 3: Eliminate incorrect options

   Writing only JavaScript or using NativeModules without Turbo Module native code won't improve performance. Creating a React component is unrelated.

4. Final Answer:

   Implement native code for FastLogger, export it as a Turbo Module, then access it via TurboModuleRegistry.get('FastLogger') -> Option B

5. Quick Check:

   Native Turbo Module + TurboModuleRegistry.get() = Performance boost [OK]

Hint: Native code + TurboModuleRegistry.get() = Turbo Module use [OK]

Common Mistakes:

• Skipping native implementation
• Using NativeModules instead of TurboModuleRegistry
• Confusing Turbo Modules with React components