Animated API basics in React Native - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new animated value starting at 0.

React Native

const opacity = new Animated.Value([1]);

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

A0

B1

Cnull

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 1 instead of 0 starts fully visible, not invisible.

Passing null or true causes errors.

The Animated.Value constructor needs a starting numeric value. Here, 0 means fully transparent.

2fill in blank

medium

Complete the code to start a timing animation that changes opacity to 1 over 500ms.

React Native

Animated.timing(opacity, { toValue: [1], duration: 500, useNativeDriver: true }).start();

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

Afalse

Bnull

C0

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0 means no change in opacity.

Passing false to toValue causes errors.

toValue should be 1 to animate opacity from 0 to fully visible.

3fill in blank

hard

Fix the error in the code to animate the scale of a view from 1 to 2.

React Native

const scale = new Animated.Value(1);
Animated.timing(scale, { toValue: [1], duration: 300, useNativeDriver: true }).start();

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

A1

B2

C'2'

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using '2' as a string causes runtime errors.

Using 1 means no scale change.

toValue must be a number 2 to scale up the view. A string '2' is invalid.

4fill in blank

hard

Fill in the blank to create an animated style that changes opacity and scale.

React Native

const animatedStyle = {
  opacity: opacity,
  transform: [{ scale: [1] }]
};

return <Animated.View style={animatedStyle} />;

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

Ascale

Bopacity

CscaleValue

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using opacity instead of scale in transform.

Using undefined variable names.

The transform property expects an object with the scale key set to the animated value.

5fill in blank

hard

Fill all three blanks to create a fade-in and scale-up animation using Animated.parallel.

React Native

Animated.parallel([
  Animated.timing(opacity, { toValue: [1], duration: 400, useNativeDriver: true }),
  Animated.timing(scale, { toValue: [2], duration: 400, useNativeDriver: true })
]).start([3]);

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

A1

B2

C() => console.log('Animation done')

D() => alert('Done')

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong toValue numbers.

Passing alert instead of console.log.

Missing the callback function.

Opacity animates to 1 (visible), scale animates to 2 (double size), and the callback logs when done.

Practice

1. What is the primary purpose of Animated.Value in React Native's Animated API?

easy

A. To define the duration of an animation

B. To create a new component for animation

C. To store and track the current value of an animation

D. To handle user gestures during animation

Solution

1. Step 1: Understand the role of Animated.Value

   Animated.Value is used to hold a numeric value that changes over time during an animation.

2. Step 2: Differentiate from other Animated API parts

   It does not create components or handle gestures; it only stores the animation's current value.

3. Final Answer:

   To store and track the current value of an animation -> Option C

4. Quick Check:

   Animated.Value = animation value holder [OK]

Hint: Animated.Value holds the changing number in animation [OK]

Common Mistakes:

• Confusing Animated.Value with animation duration
• Thinking Animated.Value creates UI components
• Assuming it handles user input gestures

2. Which of the following is the correct syntax to create an Animated.Value starting at 0?

easy

A. const anim = new Animated.Value(0);

B. const anim = Animated.value(0);

C. const anim = Animated.Value(0);

D. const anim = Animated.createValue(0);

Solution

1. Step 1: Recall correct Animated.Value instantiation

   Animated.Value is a class and must be instantiated with new.

2. Step 2: Check each option's syntax

   Only new Animated.Value(0) is correct; others miss new or use wrong method names.

3. Final Answer:

   const anim = new Animated.Value(0); -> Option A

4. Quick Check:

   Use new keyword to create Animated.Value [OK]

Hint: Always use 'new' when creating Animated.Value [OK]

Common Mistakes:

• Omitting the 'new' keyword
• Using lowercase 'value' instead of 'Value'
• Using non-existent methods like createValue

3. What will be the final value of anim after this code runs?

const anim = new Animated.Value(0);
Animated.timing(anim, {toValue: 100, duration: 500, useNativeDriver: false}).start();
// Assume animation completes instantly for this question

medium

A. 100

B. 0

C. 50

D. undefined

Solution

1. Step 1: Understand Animated.timing behavior

   Animated.timing animates the value from its current state to toValue over the given duration.

2. Step 2: Since animation completes instantly here, anim reaches toValue

   Because we assume instant completion, anim will be 100 after animation.

3. Final Answer:

   100 -> Option A

4. Quick Check:

   Animated.timing sets value to toValue after animation [OK]

Hint: Animated.timing moves value to toValue after animation [OK]

Common Mistakes:

• Thinking value stays at 0
• Assuming value is halfway (50) instantly
• Confusing useNativeDriver effect on value

4. Identify the error in this animation code snippet:

const anim = new Animated.Value(0);
Animated.timing(anim, {toValue: 1, duration: 300}).start();

medium

A. toValue must be 0 or less

B. Missing useNativeDriver property in timing config

C. start() method is missing a callback

D. Animated.Value should be initialized with 1

Solution

1. Step 1: Check Animated.timing config requirements

   Since React Native 0.62+, useNativeDriver is required to specify if native driver is used.

2. Step 2: Identify missing property

   The code lacks useNativeDriver, causing a warning or error.

3. Final Answer:

   Missing useNativeDriver property in timing config -> Option B

4. Quick Check:

   Always include useNativeDriver in Animated.timing [OK]

Hint: Always add useNativeDriver in timing config [OK]

Common Mistakes:

• Ignoring useNativeDriver requirement
• Thinking start() needs a callback
• Initializing Animated.Value incorrectly

5. You want to animate a view's opacity from 0 to 1 and then back to 0 repeatedly. Which approach correctly uses the Animated API to achieve this?

hard

A. Use setTimeout to manually update opacity value every second

B. Use a single Animated.timing with toValue 1 and duration doubled

C. Use Animated.spring with toValue 1 and then call Animated.timing to 0

D. Use Animated.loop with Animated.sequence of two Animated.timing calls changing opacity 0->1 and 1->0

Solution

1. Step 1: Understand repeating animations

   To repeat animations, Animated.loop is used to repeat a sequence or animation indefinitely.

2. Step 2: Use Animated.sequence to chain opacity changes

   Animating opacity from 0 to 1 then back to 0 requires sequencing two Animated.timing calls inside a loop.

3. Step 3: Evaluate options

   Use Animated.loop with Animated.sequence of two Animated.timing calls changing opacity 0->1 and 1->0 correctly uses Animated.loop with Animated.sequence of two timings. Others either don't loop or use incorrect methods.

4. Final Answer:

   Use Animated.loop with Animated.sequence of two Animated.timing calls changing opacity 0->1 and 1->0 -> Option D

5. Quick Check:

   Loop + sequence = repeated animation [OK]

Hint: Use Animated.loop with sequence for repeated animations [OK]

Common Mistakes:

• Trying to do repeat with single timing
• Mixing spring and timing incorrectly
• Using manual timers instead of Animated API