Device info and haptics in React Native - Build, Publish & Deploy

Build & Publish - Device info and haptics

Performance Impact

Accessing device info and triggering haptics usually has minimal impact on frame rate and memory. Device info calls are lightweight and often cached. Haptic feedback uses native hardware, so it does not affect app CPU or memory significantly. However, excessive or continuous haptic triggers can drain battery faster and may cause slight UI jank if called on the main thread too often.

Optimization Tips

Cache device info results to avoid repeated native calls. Trigger haptics sparingly and only on meaningful user actions to preserve battery and maintain smooth UI. Use asynchronous calls for device info to prevent blocking the UI thread. Avoid triggering haptics in rapid succession to keep 60fps smoothness.

App Size and Startup Time

Including device info and haptics libraries adds a small increase to app bundle size, typically under 1MB. This is minor compared to overall app size. Startup time impact is negligible since these features initialize on demand, not at app launch.

iOS vs Android Differences

On iOS, haptics use the Taptic Engine with predefined feedback types. On Android, haptics use the Vibrator API with more variability across devices. Device info APIs differ: iOS restricts access to some identifiers for privacy, while Android provides more hardware details but requires permissions. React Native libraries abstract these differences but testing on both platforms is essential.

Store Review Guidelines

• Ensure you request only necessary permissions for device info (e.g., no unnecessary location or phone state access).
• Respect user privacy: do not collect or transmit device identifiers without consent.
• Follow Apple's Human Interface Guidelines for haptic feedback usage to avoid misuse or annoyance.
• On Google Play, declare vibration permission in the manifest and explain its use if requested.

Self-Check Scenario

Your app takes 5 seconds to load this screen that shows device info and triggers haptics. What's likely wrong?

• Device info is fetched synchronously on the main thread, blocking UI rendering.
• Haptics are triggered repeatedly during loading, causing performance drops.
• Unnecessary permissions or heavy native modules increase startup time.

Fix by caching device info, using async calls, and limiting haptic triggers.

Key Result

Device info and haptics have minimal performance and size impact when used properly. Optimize by caching info and limiting haptic triggers. Follow platform privacy and permission rules for smooth app store approval.

Practice

1. Which React Native module provides information about the device's operating system?

easy

A. Platform

B. Dimensions

C. Vibration

D. StatusBar

Solution

1. Step 1: Identify the module for OS info

   The Platform module in React Native gives details about the device OS like 'ios' or 'android'.

2. Step 2: Compare with other modules

   Dimensions gives screen size, Vibration controls haptic feedback, and StatusBar manages the status bar UI, not OS info.

3. Final Answer:

   Platform -> Option A

4. Quick Check:

   OS info = Platform [OK]

Hint: Platform module always gives OS info in React Native [OK]

Common Mistakes:

• Confusing Dimensions with OS info
• Thinking Vibration provides device info
• Assuming StatusBar relates to OS details

2. Which of the following is the correct syntax to get the screen width using React Native's Dimensions module?

easy

A. Dimensions.screen.width()

B. Dimensions.width()

C. Dimensions.get('screen').width

D. Dimensions.getWidth('screen')

Solution

1. Step 1: Recall Dimensions API usage

   The correct method to get screen size is Dimensions.get('screen'), which returns an object with width and height.

2. Step 2: Access width property correctly

   Access the width by .width property, so Dimensions.get('screen').width is correct syntax.

3. Final Answer:

   Dimensions.get('screen').width -> Option C

4. Quick Check:

   Screen width = Dimensions.get('screen').width [OK]

Hint: Use Dimensions.get('screen').width to get screen width [OK]

Common Mistakes:

• Calling width as a function instead of property
• Using wrong method names like getWidth
• Accessing screen as a property instead of argument

3. What will be the result of this React Native code snippet?

import { Vibration } from 'react-native';

Vibration.vibrate(1000);

Choose the correct behavior.

medium

A. The device vibrates for 1 second

B. The device vibrates indefinitely until stopped

C. The device vibrates for 100 milliseconds

D. No vibration occurs because vibrate needs a pattern array

Solution

1. Step 1: Understand Vibration.vibrate parameter

   Passing a number like 1000 to Vibration.vibrate() makes the device vibrate for that many milliseconds (1000 ms = 1 second).

2. Step 2: Check other options

   Indefinite vibration requires a pattern with repeat, 100 ms is too short, and vibrate accepts a number directly, so no pattern array is needed.

3. Final Answer:

   The device vibrates for 1 second -> Option A

4. Quick Check:

   Vibration.vibrate(1000) = 1 second vibration [OK]

Hint: Number argument in vibrate() is vibration duration in ms [OK]

Common Mistakes:

• Thinking vibrate needs a pattern array always
• Confusing milliseconds with seconds
• Assuming vibrate runs indefinitely by default

4. Identify the error in this React Native code snippet that tries to vibrate the device:

import { Vibration } from 'react-native';

Vibration.vibrate([500, 1000]);

medium

A. The vibrate method requires a second argument for repeat

B. The array pattern is correct but missing a repeat flag

C. The array should be passed as a second argument, not the first

D. The vibrate method does not accept an array as argument

Solution

1. Step 1: Check Vibration.vibrate pattern usage

   Vibration.vibrate accepts an array pattern as first argument to define vibration and pause durations.

2. Step 2: Understand repeat flag necessity

   To repeat the pattern, a second boolean argument true is needed. Without it, the pattern runs once, so no error but possibly unintended behavior.

3. Final Answer:

   The array pattern is correct but missing a repeat flag -> Option B

4. Quick Check:

   Pattern array needs repeat flag to loop [OK]

Hint: Add second argument true to repeat vibration pattern [OK]

Common Mistakes:

• Thinking array is invalid argument
• Forgetting second argument for repeat
• Passing array as second argument instead of first

5. You want to create a React Native function that vibrates the device for 500ms, then pauses for 300ms, and repeats this pattern twice. Which code snippet correctly implements this behavior?

hard

A. Vibration.vibrate(500); Vibration.vibrate(300); Vibration.vibrate(500);

B. Vibration.vibrate([500, 300, 500, 300], true); setTimeout(() => Vibration.cancel(), 2600);

C. Vibration.vibrate([500, 300], true); setTimeout(() => Vibration.cancel(), 2600);

D. Vibration.vibrate([500, 300, 500, 300], false);

Solution

1. Step 1: Understand the required pattern

   The pattern is vibrate 500ms, pause 300ms, repeated twice: [500, 300, 500, 300].

2. Step 2: Use repeat false to play exactly twice

   Vibration.vibrate([500, 300, 500, 300], false) executes the sequence once without looping further.

3. Step 3: Eliminate other options

   Using true causes indefinite looping (cancel timing imprecise); shorter pattern loops incorrectly; separate calls lack pauses.

4. Final Answer:

   Vibration.vibrate([500, 300, 500, 300], false); -> Option D

5. Quick Check:

   Two pattern repeats = [500, 300, 500, 300], false [OK]

Hint: Unroll pattern twice with repeat false for exact repeats [OK]

Common Mistakes:

• Using repeat true without precise cancel
• Using false for repeat flag
• Calling vibrate multiple times instead of pattern