matchedGeometryEffect in iOS Swift

Introduction

The matchedGeometryEffect helps you smoothly move or transform a view from one place to another in your app. It makes animations look natural and connected.

When you want to animate a button moving to a new position on the screen.

When you want to smoothly change a small image into a larger one on tap.

When you want to animate a card expanding from a list to a detail view.

When you want to connect two views visually during a transition.

Syntax

iOS Swift

view.matchedGeometryEffect(id: "uniqueID", in: namespace)

The id is a unique string or value that links two views together.

The namespace is a special container that groups matched views for animation.

Examples

This links a Text view with the id "text" inside the given namespace.

iOS Swift

Text("Hello")
  .matchedGeometryEffect(id: "text", in: namespace)

This links a Circle shape with the id "circle" for animation.

iOS Swift

Circle()
  .frame(width: 50, height: 50)
  .matchedGeometryEffect(id: "circle", in: namespace)

Sample App

This example shows a blue rounded rectangle that grows from a small square to a large square when tapped. The matchedGeometryEffect links the two shapes so the animation is smooth and connected.

iOS Swift

import SwiftUI

struct ContentView: View {
  @Namespace private var namespace
  @State private var isExpanded = false

  var body: some View {
    VStack {
      if !isExpanded {
        RoundedRectangle(cornerRadius: 25)
          .fill(Color.blue)
          .frame(width: 100, height: 100)
          .matchedGeometryEffect(id: "shape", in: namespace)
          .onTapGesture {
            withAnimation(.spring()) {
              isExpanded = true
            }
          }
      } else {
        RoundedRectangle(cornerRadius: 25)
          .fill(Color.blue)
          .frame(width: 300, height: 300)
          .matchedGeometryEffect(id: "shape", in: namespace)
          .onTapGesture {
            withAnimation(.spring()) {
              isExpanded = false
            }
          }
      }
    }
  }
}

Important Notes

Always use the same id and namespace for views you want to animate between.

The views must be in the same view hierarchy or visible at the same time for the effect to work.

You can animate many properties like size, position, and shape with this effect.

Summary

matchedGeometryEffect links two views for smooth animations.

Use a unique id and a shared namespace to connect views.

Great for animating changes in size, position, or shape between views.

Practice

1. What is the main purpose of matchedGeometryEffect in SwiftUI?

easy

A. To manage data persistence

B. To create a new view from scratch

C. To handle user input events

D. To link two views for smooth animations between them

Solution

1. Step 1: Understand matchedGeometryEffect usage

   This modifier connects two views by their id and namespace to animate changes smoothly.

2. Step 2: Identify the purpose

   It is used specifically for animating transitions in position, size, or shape between views.

3. Final Answer:

   To link two views for smooth animations between them -> Option D

4. Quick Check:

   matchedGeometryEffect = link views for animation [OK]

Hint: matchedGeometryEffect connects views for smooth animations [OK]

Common Mistakes:

• Thinking it creates new views
• Confusing it with event handling
• Assuming it manages data

2. Which of the following is the correct way to apply matchedGeometryEffect to a view in SwiftUI?

easy

A. view.matchedGeometryEffect("uniqueID", ns)

B. view.matchedGeometryEffect(id: "uniqueID", namespace: ns)

C. view.matchedGeometryEffect(id: ns, namespace: "uniqueID")

D. view.matchedGeometryEffect(namespace: "uniqueID", id: ns)

Solution

1. Step 1: Recall matchedGeometryEffect syntax

   The correct syntax requires named parameters: id as a unique identifier and namespace as the shared namespace.

2. Step 2: Match parameters correctly

   view.matchedGeometryEffect(id: "uniqueID", namespace: ns) uses id: "uniqueID" and namespace: ns, which is correct.

3. Final Answer:

   view.matchedGeometryEffect(id: "uniqueID", namespace: ns) -> Option B

4. Quick Check:

   Correct syntax uses named parameters id and namespace [OK]

Hint: Use named parameters id and namespace in matchedGeometryEffect [OK]

Common Mistakes:

• Swapping id and namespace parameters
• Omitting parameter names
• Passing parameters in wrong order

3. Consider this SwiftUI code snippet:

struct ContentView: View {
  @Namespace var ns
  @State var isExpanded = false
  var body: some View {
    VStack {
      if isExpanded {
        RoundedRectangle(cornerRadius: 25)
          .matchedGeometryEffect(id: "shape", namespace: ns)
          .frame(width: 300, height: 200)
      } else {
        RoundedRectangle(cornerRadius: 25)
          .matchedGeometryEffect(id: "shape", namespace: ns)
          .frame(width: 100, height: 100)
      }
      Button("Toggle") { isExpanded.toggle() }
    }
  }
}

What happens when the button is tapped?

medium

A. The rectangle smoothly animates between small and large sizes

B. The rectangle instantly changes size without animation

C. The app crashes due to namespace error

D. The button does not toggle the rectangle size

Solution

1. Step 1: Understand matchedGeometryEffect behavior

   Using the same id and namespace links the two rectangles for animation.

2. Step 2: Analyze the toggle effect

   Toggling isExpanded switches between two frames, triggering a smooth size animation.

3. Final Answer:

   The rectangle smoothly animates between small and large sizes -> Option A

4. Quick Check:

   matchedGeometryEffect animates size changes smoothly [OK]

Hint: Same id and namespace animate size changes smoothly [OK]

Common Mistakes:

• Expecting instant size change without animation
• Confusing namespace usage
• Thinking toggle won't affect view

4. Given this code snippet, what is the error that prevents the matchedGeometryEffect animation from working?

@Namespace var ns

var body: some View {
  VStack {
    Circle()
      .matchedGeometryEffect(id: "circle", namespace: ns)
      .frame(width: 50, height: 50)
    if showSquare {
      Rectangle()
        .matchedGeometryEffect(id: "square", namespace: ns)
        .frame(width: 100, height: 100)
    }
  }
}

medium

A. Namespace is not declared properly

B. Frames are missing for the views

C. The ids for matchedGeometryEffect are different, so no animation occurs

D. showSquare is not toggled anywhere

Solution

1. Step 1: Check matchedGeometryEffect ids

   The Circle uses id "circle" and the Rectangle uses id "square"; they must share the same id to animate.

2. Step 2: Understand animation linking

   Different ids mean views are not linked, so no smooth animation happens.

3. Final Answer:

   The ids for matchedGeometryEffect are different, so no animation occurs -> Option C

4. Quick Check:

   Same id needed for matchedGeometryEffect animation [OK]

Hint: Use same id for views to animate with matchedGeometryEffect [OK]

Common Mistakes:

• Assuming different ids animate
• Ignoring namespace importance
• Missing frame sizes

5. You want to animate a card flipping effect between a front and back view using matchedGeometryEffect. Which approach correctly achieves this?

hard

A. Use the same id and namespace on front and back views, toggle visibility, and animate rotation

B. Use different id values for front and back views with the same namespace

C. Apply matchedGeometryEffect only to the front view and toggle the back view without it

D. Use matchedGeometryEffect with no namespace to link the views

Solution

1. Step 1: Understand matchedGeometryEffect for flipping

   To animate a flip, both front and back views must share the same id and namespace to link their geometry.

2. Step 2: Combine with rotation animation

   Toggling visibility and animating rotation creates the flip effect smoothly.

3. Final Answer:

   Use the same id and namespace on front and back views, toggle visibility, and animate rotation -> Option A

4. Quick Check:

   Same id + namespace + rotation = flip animation [OK]

Hint: Flip needs same id, namespace, and rotation animation [OK]

Common Mistakes:

• Using different ids breaks animation
• Forgetting to animate rotation
• Omitting namespace causes errors