Why Custom animation timing in iOS Swift? - Purpose & Use Cases

The Big Idea

What if your app's animations could feel as smooth and natural as real life?

The Scenario

Imagine you want a button to move smoothly across the screen, but at different speeds during the journey, like speeding up then slowing down, just like a car on a road trip.

The Problem

Using only basic animation tools, you get a boring, constant speed that feels unnatural and robotic. It's hard to make animations feel alive or match the mood you want.

The Solution

Custom animation timing lets you control exactly how fast or slow parts of your animation run. You can create smooth, natural movements that feel real and engaging.

Before vs After

✗ Before

UIView.animate(withDuration: 2.0, delay: 0, options: [.curveLinear], animations: {
  button.frame.origin.x += 200
}, completion: nil)

✓ After

let timing = CAMediaTimingFunction(name: .easeInEaseOut)
let animation = CABasicAnimation(keyPath: "position.x")
animation.timingFunction = timing
animation.duration = 2.0
animation.byValue = 200.0
animation.fillMode = .forwards
animation.isRemovedOnCompletion = false
button.layer.add(animation, forKey: nil)

What It Enables

It enables animations that tell a story with motion, making apps feel polished and delightful.

Real Life Example

Think of a weather app where the sun rises slowly, speeds up, then gently sets, creating a calming effect that matches the time of day.

Key Takeaways

Basic animations move at a constant speed, which can feel dull.

Custom timing lets you shape the speed curve for natural motion.

This makes your app's animations more engaging and professional.

Practice

1. What does the .curveEaseIn animation option do in UIView animations?

easy

A. Starts the animation quickly and then slows down.

B. Starts the animation slowly and then speeds up.

C. Keeps the animation speed constant throughout.

D. Reverses the animation direction automatically.

Solution

1. Step 1: Understand UIView animation curves

   UIView animation curves control how the animation speed changes over time.

2. Step 2: Identify the effect of .curveEaseIn

   .curveEaseIn means the animation starts slowly and accelerates towards the end.

3. Final Answer:

   Starts the animation slowly and then speeds up. -> Option B

4. Quick Check:

   .curveEaseIn = slow start, speed up [OK]

Hint: EaseIn means slow start, speed up later [OK]

Common Mistakes:

• Confusing .curveEaseIn with .curveEaseOut
• Thinking it keeps constant speed
• Assuming it reverses animation

2. Which of the following is the correct syntax to animate a view's alpha to 0.5 over 0.3 seconds with ease-out timing?

easy

A. UIView.animate(duration: 0.3, options: .easeOut) { view.alpha = 0.5 }

B. UIView.animate(withDuration: 0.3, options: .curveEaseIn) { view.alpha = 0.5 }

C. UIView.animate(withDuration: 0.3, delay: 0, options: .curveEaseOut) { view.alpha = 0.5 }

D. UIView.animate(withDuration: 0.3) { view.alpha = 0.5, options: .curveEaseOut }

Solution

1. Step 1: Recall UIView.animate syntax

   The correct method signature is UIView.animate(withDuration:delay:options:animations:completion:). Options must be passed as a parameter.

2. Step 2: Check each option for syntax correctness

   UIView.animate(withDuration: 0.3, delay: 0, options: .curveEaseOut) { view.alpha = 0.5 } uses correct method name, parameters, and .curveEaseOut option. Others have wrong method names or misplaced options.

3. Final Answer:

   UIView.animate(withDuration: 0.3, delay: 0, options: .curveEaseOut) { view.alpha = 0.5 } -> Option C

4. Quick Check:

   Correct UIView.animate syntax = UIView.animate(withDuration: 0.3, delay: 0, options: .curveEaseOut) { view.alpha = 0.5 } [OK]

Hint: Use withDuration and options parameters correctly [OK]

Common Mistakes:

• Using wrong method name like animate(duration:)
• Placing options inside animation block
• Forgetting delay parameter

3. What will be the visible effect of this code snippet?

UIView.animate(withDuration: 1.0, delay: 0, options: [.curveEaseInOut]) {
  view.frame.origin.x += 100
}

medium

A. The view moves 100 points to the right, starting fast and slowing down.

B. The view moves 100 points to the right at a constant speed.

C. The view jumps instantly 100 points to the right without animation.

D. The view moves 100 points to the right, starting slow, speeding up, then slowing down.

Solution

1. Step 1: Understand .curveEaseInOut timing

   .curveEaseInOut means the animation starts slowly, speeds up in the middle, then slows down at the end.

2. Step 2: Analyze the animation effect

   The view's x position increases by 100 points over 1 second with ease-in-out timing, so it moves smoothly with acceleration and deceleration.

3. Final Answer:

   The view moves 100 points to the right, starting slow, speeding up, then slowing down. -> Option D

4. Quick Check:

   .curveEaseInOut = slow start & end, fast middle [OK]

Hint: EaseInOut means slow start and end, fast middle [OK]

Common Mistakes:

• Thinking it moves at constant speed
• Confusing easeInOut with easeIn or easeOut
• Expecting instant jump without animation

4. Identify the error in this Core Animation timing code:

let animation = CABasicAnimation(keyPath: "opacity")
animation.duration = 1.0
animation.timingFunction = CAMediaTimingFunction(name: .easeIn)
animation.fromValue = 1.0
animation.toValue = 0.0
view.layer.add(animation, forKey: "fade")

medium

A. The animation is missing a fillMode to keep final state.

B. The timingFunction property expects a string, not CAMediaTimingFunction.

C. The keyPath "opacity" is invalid for CABasicAnimation.

D. The timing function name should be .easeInEaseOut, not .easeIn.

Solution

1. Step 1: Check timingFunction usage

   Using CAMediaTimingFunction(name: .easeIn) is correct and supported.

2. Step 2: Identify missing fillMode

   Without setting fillMode and isRemovedOnCompletion, the animation resets after finishing, so the view returns to original opacity.

3. Final Answer:

   The animation is missing a fillMode to keep final state. -> Option A

4. Quick Check:

   Missing fillMode causes animation to revert [OK]

Hint: Add fillMode and isRemovedOnCompletion to keep final state [OK]

Common Mistakes:

• Assuming .easeIn is invalid timing function name
• Thinking timingFunction needs a string
• Ignoring fillMode and completion behavior

5. You want to create a custom animation that moves a view along a path with a non-linear speed, speeding up then slowing down repeatedly. Which approach best achieves this?

hard

A. Use CAKeyframeAnimation with a custom timing function and path to control speed and position.

B. Use CABasicAnimation with a custom CAMediaTimingFunction using control points for the speed curve.

C. Use UIView.animate with linear curve and manually update position in a timer.

D. Use UIView.animate with .curveEaseInOut option repeatedly in a loop.

Solution

1. Step 1: Understand animation requirements

   The animation needs to follow a path and have complex speed changes (speeding up and slowing down repeatedly).

2. Step 2: Evaluate animation options

   CAKeyframeAnimation allows animating along a path and supports custom timing functions for complex speed control, making it ideal here.

3. Final Answer:

   Use CAKeyframeAnimation with a custom timing function and path to control speed and position. -> Option A

4. Quick Check:

   CAKeyframeAnimation + custom timing = best for complex path and speed [OK]

Hint: Use CAKeyframeAnimation for path + custom speed control [OK]

Common Mistakes:

• Using UIView.animate for complex path animations
• Assuming CABasicAnimation can follow a path
• Trying to manually update position with timers