React Native Reanimated - UI Render Trace

Component - React Native Reanimated

This UI component uses React Native Reanimated to create smooth, native-driven animations. It animates a box that moves horizontally when you press a button, showing how animations can improve app interactivity and feel.

Widget Tree

View
├── Animated.View
└── Button

The root View contains two children: an Animated.View which is the animated box, and a Button that triggers the animation. The Animated.View visually moves horizontally on the screen when the button is pressed.

Render Trace - 4 Steps

Step 1: View

Step 2: Animated.View

Step 3: Button

Step 4: Animated.SharedValue and withTiming

State Change - Re-render

Trigger:User presses the 'Move Box' button

Before

animatedValue is 0, box is centered

→

After

animatedValue is 150, box shifted right by 150 units

Re-renders:Animated.View re-renders with updated transform; Button and parent View remain unchanged

UI Quiz - 3 Questions

What happens when the 'Move Box' button is pressed?

A The red box slides smoothly to the right.

B The button disappears.

C The screen background color changes.

D Nothing happens.

Key Insight

React Native Reanimated lets you create smooth, performant animations by running them on the native side, avoiding slow JavaScript timers. This improves user experience by making UI interactions feel natural and responsive.

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