Custom ViewModifiers in iOS Swift - UI Render Trace

Component - Custom ViewModifiers

This UI component demonstrates how to create and use a custom ViewModifier in SwiftUI. A ViewModifier lets you package styling or behavior changes to reuse on multiple views easily.

Widget Tree

ContentView
└── VStack
    ├── Text
    └── Button

The root ContentView contains a vertical stack (VStack) with two children: a Text view and a Button. Both use the custom ViewModifier to style their appearance.

Render Trace - 4 Steps

Step 1: ContentView

Step 2: VStack

Step 3: Text

Step 4: Button

State Change - Re-render

Trigger:User taps the Button

Before

Button is styled with RoundedBlueBackground, no action triggered

→

After

Button tap triggers action (e.g., print message), UI appearance unchanged

Re-renders:Only the Button's internal state updates if any, but no visual change so no re-render visible

UI Quiz - 3 Questions

What does the custom ViewModifier do to the Text and Button?

A Changes the font size to very large

B Adds a blue rounded rectangle background and white text color

C Adds a shadow and rotates the views

D Removes padding around the views

Key Insight

Creating custom ViewModifiers in SwiftUI helps keep your code clean and consistent by reusing styling or behavior across multiple views. This approach is like making a reusable style recipe you can apply anywhere.

Practice

1. What is the main purpose of creating a custom ViewModifier in SwiftUI?

easy

A. To reuse a set of view styles and behaviors easily

B. To create a new type of view from scratch

C. To handle user input events directly

D. To manage app navigation between screens

Solution

1. Step 1: Understand what a ViewModifier does

   A ViewModifier bundles styling and behavior changes for views.

2. Step 2: Identify the main use

   It helps reuse these styles easily across many views.

3. Final Answer:

   To reuse a set of view styles and behaviors easily -> Option A

4. Quick Check:

   Custom ViewModifiers = reuse styles [OK]

Hint: Think: reuse styles and behaviors with one modifier [OK]

Common Mistakes:

• Confusing ViewModifier with creating new views
• Thinking it handles navigation or input directly
• Assuming it manages app state

2. Which of the following is the correct way to apply a custom ViewModifier named Highlight to a Text view?

easy

A. Text("Hello").modifier(Highlight())

B. Text("Hello").applyModifier(Highlight)

C. Text("Hello").useModifier(Highlight())

D. Text("Hello").addModifier(Highlight)

Solution

1. Step 1: Recall the correct method name

   The method to apply a ViewModifier is .modifier().

2. Step 2: Check syntax for applying Highlight

   It should be .modifier(Highlight()) with parentheses to create the modifier instance.

3. Final Answer:

   Text("Hello").modifier(Highlight()) -> Option A

4. Quick Check:

   Use .modifier() with instance [OK]

Hint: Remember: .modifier() takes an instance with () [OK]

Common Mistakes:

• Using wrong method names like applyModifier or addModifier
• Forgetting parentheses after modifier name
• Passing type instead of instance

3. Given this custom ViewModifier:

struct RedTitle: ViewModifier {
  func body(content: Content) -> some View {
    content
      .font(.title)
      .foregroundColor(.red)
  }
}

What will this code display?

Text("Welcome").modifier(RedTitle())

medium

A. Text "Welcome" with no changes

B. Text "Welcome" in default color with title font

C. Text "Welcome" in red color with default font

D. Text "Welcome" in red color with title font

Solution

1. Step 1: Analyze the RedTitle modifier

   It sets the font to title and text color to red.

2. Step 2: Apply modifier to Text("Welcome")

   The text will appear with title font size and red color.

3. Final Answer:

   Text "Welcome" in red color with title font -> Option D

4. Quick Check:

   RedTitle = red + title font [OK]

Hint: Look at modifier body: font and color changes [OK]

Common Mistakes:

• Ignoring the font change
• Assuming default color remains
• Confusing modifier effects

4. What is wrong with this custom ViewModifier code?

struct BlueBackground: ViewModifier {
  func body(content: Content) -> some View {
    content.background(Color.blue)
  }

  func body(content: Content) -> some View {
    content.padding()
  }
}

medium

A. Background modifier is not allowed inside ViewModifier

B. Two body functions cause a duplicate method error

C. Missing return keyword in body functions

D. Padding modifier must be applied before background

Solution

1. Step 1: Check method definitions in struct

   There are two body(content:) methods defined, which is not allowed.

2. Step 2: Understand Swift rules for method overloading

   Swift does not allow two methods with the same signature in one struct.

3. Final Answer:

   Two body functions cause a duplicate method error -> Option B

4. Quick Check:

   Duplicate body() methods = error [OK]

Hint: Only one body(content:) allowed per ViewModifier [OK]

Common Mistakes:

• Trying to overload body method
• Forgetting return keyword (not needed here)
• Misunderstanding modifier order rules

5. You want to create a custom ViewModifier that adds a rounded border only if a Boolean highlight is true. Which of these implementations correctly applies the border conditionally?

hard

A. struct ConditionalBorder: ViewModifier {
var highlight: Bool
func body(content: Content) -> some View {
if highlight {
content.border(Color.green, width: 2)
} else {
content
}
}
}

B. struct ConditionalBorder: ViewModifier {
var highlight: Bool
func body(content: Content) -> some View {
content.border(highlight ? Color.green : Color.clear, width: 2)
}
}

C. struct ConditionalBorder: ViewModifier {
var highlight: Bool
func body(content: Content) -> some View {
content
.border(Color.green, width: highlight ? 2 : 0)
}
}

D. struct ConditionalBorder: ViewModifier {
var highlight: Bool
func body(content: Content) -> some View {
content
.border(Color.green, width: highlight)
}
}

Solution

1. Step 1: Eliminate compile errors

   struct ConditionalBorder: ViewModifier { var highlight: Bool func body(content: Content) -> some View { if highlight { content.border(Color.green, width: 2) } else { content } } } returns different view types in if-else (compiler error). struct ConditionalBorder: ViewModifier { var highlight: Bool func body(content: Content) -> some View { content .border(Color.green, width: highlight) } } passes Bool to width (CGFloat expected, type error).

2. Step 2: Compare remaining options

   struct ConditionalBorder: ViewModifier { var highlight: Bool func body(content: Content) -> some View { content.border(highlight ? Color.green : Color.clear, width: 2) } } uses Color.clear with fixed width 2: invisible but expands frame (layout shift). struct ConditionalBorder: ViewModifier { var highlight: Bool func body(content: Content) -> some View { content .border(Color.green, width: highlight ? 2 : 0) } } uses conditional width 2/0: border only when true, no layout shift.

3. Final Answer:

   content.border(Color.green, width: highlight ? 2 : 0) -> Option C

4. Quick Check:

   Conditional width = correct conditional border [OK]

Hint: Ternary on width for conditional border without layout shift [OK]

Common Mistakes:

• Returning different view types in if-else inside body
• Passing Bool where CGFloat is expected
• Using Color.clear with fixed width (layout shift)