React Native Reanimated - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is React Native Reanimated used for?

React Native Reanimated is a library that helps create smooth and powerful animations in React Native apps by running animation code on the native thread, making animations faster and more fluid.

beginner

What is a shared value in React Native Reanimated?

A shared value is a special kind of variable that holds animation state and can be safely updated on the native side. It allows animations to run smoothly without blocking the JavaScript thread.

intermediate

Explain the purpose of the useAnimatedStyle hook.

The useAnimatedStyle hook lets you create styles that automatically update when shared values change. It connects animation values to the style properties of components.

intermediate

Why does React Native Reanimated run animations on the native thread?

Running animations on the native thread avoids delays caused by JavaScript processing. This means animations stay smooth even if the JavaScript thread is busy doing other work.

beginner

What is the role of the withTiming function?

withTiming is used to create a timing animation that changes a shared value smoothly over a set duration, like moving a box from left to right in a given time.

Which hook is used to create animated styles in React Native Reanimated?

A useState

B useAnimatedStyle

C useEffect

D useRef

useAnimatedStyle creates styles that update automatically when shared values change.

What does a shared value in Reanimated represent?

A A variable that holds animation state on the native thread

B A React component

C A CSS style

D A JavaScript event handler

Shared values hold animation data and run on the native thread for smooth animations.

Why is running animations on the native thread beneficial?

A It disables animations

B It makes the app use more memory

C It makes animations smoother by avoiding JavaScript delays

D It slows down animations

Native thread animations avoid JS thread delays, keeping animations smooth.

Which function would you use to animate a value over time in Reanimated?

A useState

B setTimeout

C withSpring

D withTiming

withTiming animates values smoothly over a specified duration.

What is the main difference between React Native Reanimated and Animated API?

A Reanimated runs animations on the native thread, Animated runs mostly on JS thread

B Animated is faster than Reanimated

C Reanimated does not support gestures

D Animated is only for web apps

Reanimated improves performance by running animations on the native thread.

Describe how React Native Reanimated improves animation performance compared to standard React Native animations.

Think about where the animation code runs and how that affects smoothness.

Explain the role of shared values and how they interact with animated styles in React Native Reanimated.

Consider how animation data flows from variables to UI styles.

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