React Native Reanimated - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What is the output of this Reanimated shared value update?

Consider this React Native Reanimated code snippet that updates a shared value on button press. What will be the value of progress.value after pressing the button twice?

React Native

import {useSharedValue} from 'react-native-reanimated';

const progress = useSharedValue(0);

function onPress() {
  progress.value = progress.value + 0.5;
}

A 1.0

B 0.5

C 2.0

D 0

💡 Hint

Each press adds 0.5 to the current value.

The shared value starts at 0. Each press adds 0.5, so after two presses, progress.value is 1.0.

❓ lifecycle

intermediate

When does a worklet run in React Native Reanimated?

In React Native Reanimated, when is a worklet function executed?

A On the UI thread, immediately when called from JS thread

B On the UI thread, scheduled by Reanimated runtime

C Only on the JS thread asynchronously

D On the native thread after a delay

💡 Hint

Worklets run on the UI thread for smooth animations.

Worklets are special functions that run on the UI thread, scheduled by Reanimated to avoid blocking the JS thread.

📝 Syntax

advanced

What error does this Reanimated code produce?

What error will this code snippet cause when run in a React Native app using Reanimated?

React Native

import {useSharedValue} from 'react-native-reanimated';

const progress = useSharedValue(0);

function update() {
  'worklet';
  progress.value += 1;
}

update();

A No error, runs correctly

B SyntaxError: Missing semicolon

C TypeError: progress.value is not a number

D ReferenceError: progress is not defined inside worklet

💡 Hint

Worklets have isolated scope and cannot access variables outside unless passed or declared.

Inside a worklet, variables from outside scope are not accessible unless passed explicitly. Here, progress is undefined inside the worklet.

❓ navigation

advanced

How to trigger a navigation action after animation ends?

You want to navigate to another screen after a Reanimated animation finishes. Which approach correctly triggers navigation after the animation?

A Use <code>withTiming</code> callback to call navigation inside the worklet

B Call navigation immediately after starting animation without callback

C Use <code>runOnJS</code> inside animation callback to call navigation function

D Use <code>setTimeout</code> with animation duration to call navigation

💡 Hint

Navigation functions run on JS thread, so use runOnJS to call them from worklet.

Animation callbacks run on UI thread worklets. To call JS thread functions like navigation, use runOnJS inside the animation callback.

🧠 Conceptual

expert

What is the main benefit of using React Native Reanimated worklets?

Why do React Native developers use worklets in Reanimated for animations instead of running animation logic on the JS thread?

A Worklets allow animations to run on the UI thread, making them smoother and avoiding JS thread delays

B Worklets simplify writing animations by using plain JavaScript without any restrictions

C Worklets automatically optimize battery usage by reducing CPU frequency

D Worklets enable animations to run on the native thread with direct hardware access

💡 Hint

Think about what causes janky animations in React Native.

Worklets run animation code on the UI thread, avoiding delays caused by JS thread blocking, resulting in smooth animations.

Practice

1.

What is the main purpose of useSharedValue in React Native Reanimated?

easy

A. To hold and update animation values that can change over time

B. To create static styles for components

C. To handle user input events

D. To navigate between screens

Solution

1. Step 1: Understand useSharedValue role

   useSharedValue is designed to store values that can change and animate smoothly.

2. Step 2: Compare with other options

   Static styles, user inputs, and navigation are unrelated to useSharedValue.

3. Final Answer:

   To hold and update animation values that can change over time -> Option A

4. Quick Check:

   useSharedValue = hold animation values [OK]

Hint: Remember: useSharedValue stores changing animation data [OK]

Common Mistakes:

• Confusing useSharedValue with static styling
• Thinking it handles user input or navigation
• Assuming it triggers animations directly

2.

Which of the following is the correct syntax to create an animated style using useAnimatedStyle?

const animatedStyle = useAnimatedStyle(() => {
  return {
    opacity: sharedValue.value
  };
});

easy

A. const animatedStyle = useAnimatedStyle(() => { opacity: sharedValue.value });

B. const animatedStyle = useAnimatedStyle(() => ({ opacity: sharedValue.value }));

C. const animatedStyle = useAnimatedStyle(() => return { opacity: sharedValue.value });

D. const animatedStyle = useAnimatedStyle(() => [ opacity: sharedValue.value ]);

Solution

1. Step 1: Check arrow function syntax

   Returning an object directly requires parentheses around the object: () => ({ ... }).

2. Step 2: Validate each option

   const animatedStyle = useAnimatedStyle(() => ({ opacity: sharedValue.value })); uses correct syntax with parentheses. Options A, C, and D have syntax errors.

3. Final Answer:

   const animatedStyle = useAnimatedStyle(() => ({ opacity: sharedValue.value })); -> Option B

4. Quick Check:

   Arrow function returning object needs parentheses [OK]

Hint: Use parentheses to return object in arrow functions [OK]

Common Mistakes:

• Missing parentheses around returned object
• Using return without braces properly
• Using array brackets instead of object braces

3.

Given the code below, what will be the opacity of the Animated.View after the shared value updates to 0.5?

const opacity = useSharedValue(1);

const animatedStyle = useAnimatedStyle(() => ({
  opacity: opacity.value
}));

// Later in code
opacity.value = 0.5;

medium

A. The opacity will remain 1

B. The opacity will become undefined

C. The opacity will update to 0.5 smoothly

D. The opacity will instantly jump to 0.5 without animation

Solution

1. Step 1: Understand shared value update

   Updating opacity.value directly sets the value immediately without animation.

2. Step 2: Direct assignment causes instant jump

   Reanimated updates the style instantly to 0.5 when using direct assignment, without smooth interpolation.

3. Final Answer:

   The opacity will instantly jump to 0.5 without animation -> Option D

4. Quick Check:

   Direct sharedValue.value = instant update [OK]

Hint: Direct shared value changes update instantly; use withTiming for smooth animation [OK]

Common Mistakes:

• Thinking the value stays the same after update
• Assuming it animates smoothly without withTiming
• Confusing with non-animated style updates

4.

Identify the error in the following code snippet using React Native Reanimated:

const progress = useSharedValue(0);

const animatedStyle = useAnimatedStyle(() => {
  transform: [{ translateX: progress }]
});

medium

A. transform property should be a string, not an array

B. useSharedValue should be called inside useEffect

C. Missing .value when accessing shared value inside useAnimatedStyle

D. useAnimatedStyle cannot return an object

Solution

1. Step 1: Check how shared values are accessed

   Inside useAnimatedStyle, shared values must be accessed with .value.

2. Step 2: Identify the error in transform

   The code uses progress instead of progress.value, causing a runtime error.

3. Final Answer:

   Missing .value when accessing shared value inside useAnimatedStyle -> Option C

4. Quick Check:

   Access sharedValue.value inside animated styles [OK]

Hint: Always use .value to read shared values inside animated styles [OK]

Common Mistakes:

• Forgetting .value on shared values
• Calling useSharedValue inside effects incorrectly
• Misunderstanding transform property format

5.

You want to create a button that scales up smoothly when pressed and returns to normal size when released. Which approach correctly uses React Native Reanimated to achieve this?

const scale = useSharedValue(1);

const animatedStyle = useAnimatedStyle(() => ({
  transform: [{ scale: scale.value }]
}));

// On press in
scale.value = withTiming(1.2, { duration: 200 });

// On press out
scale.value = withTiming(1, { duration: 200 });

hard

A. This approach correctly animates scale on press in and out using withTiming

B. You must use useState instead of useSharedValue for animation

C. withTiming cannot be used inside event handlers

D. Animated styles cannot animate transform properties

Solution

1. Step 1: Check useSharedValue and useAnimatedStyle usage

   Using useSharedValue to hold scale and useAnimatedStyle to apply transform is correct.

2. Step 2: Verify animation with withTiming

   withTiming smoothly animates the scale value on press in and out events.

3. Step 3: Confirm event handler usage

   Assigning scale.value = withTiming(...) inside press handlers is valid and triggers animation.

4. Final Answer:

   This approach correctly animates scale on press in and out using withTiming -> Option A

5. Quick Check:

   UseSharedValue + withTiming = smooth press scale animation [OK]

Hint: Use withTiming on shared values for smooth press animations [OK]

Common Mistakes:

• Using useState instead of useSharedValue for animation
• Thinking withTiming can't be used in event handlers
• Believing transform can't animate