Chapters
Chapters

Chapters

Hide chapters

SwiftUI by Tutorials

Fifth Edition · iOS 16, macOS 13 · Swift 5.8 · Xcode 14.2

Before You Begin

Section 0: 4 chapters
Show chapters Hide chapters

Section I: Diving Into SwiftUI

Section 1: 4 chapters
Show chapters Hide chapters

Section II: Building Blocks of SwiftUI

Section 2: 3 chapters
Show chapters Hide chapters

Section III: State & Data Flow

Section 3: 5 chapters
Show chapters Hide chapters

Section IV: Navigation & Data Display

Section 4: 5 chapters
Show chapters Hide chapters

Section V: UI Extensions

Section 5: 4 chapters
Show chapters Hide chapters

Section VI: SwiftUI for macOS

Section 6: 3 chapters
Show chapters Hide chapters

7. Introducing Stacks & Containers
Written by Antonio Bello

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

In the previous chapter, you learned about common SwiftUI controls, including TextField, Button, Slider and Toggle. In this chapter, you’ll be introduced to container views, which are used to group related views together, as well as to lay them out in respect to each other.

Before starting, though, it’s essential to learn and understand how views are sized.

Preparing the Project

Before jumping into views and their sizes, be aware that the starter project for this chapter has some additions compared to the final project of the previous chapter.

If you want to keep working on your own copy, worry not! Just copy these files and add to your project, or drag and drop then directly into Xcode.

  • Practice/ChallengeView.swift
  • Practice/ChallengesViewModel.swift
  • Practice/ChoicesRow.swift
  • Practice/ChoicesView.swift
  • Practice/CongratulationsView.swift
  • Practice/PracticeView.swift
  • Practice/QuestionView.swift
  • StarterView.swift
  • HistoryView.swift

Layout and Priorities

In UIKit and AppKit, you were used to using Auto Layout to constrain views. The general rule was to let a parent decide the size of its children, usually obtained by adding constraints, unless their size was statically set using, for example, width and height constraints.

Puwo oxbujzixaoy
Vufa ongatyipood

Layout for Views With a Single Child

Open the starter project and go to Practice/ChallengeView.swift, which is a new view created out of the SwiftUI View template. You can see that it contains a single Text:

Vwaxv Kesqa Muffw
Wrucp Dixnu Dolwj

Cehqi Geplq 9
Finho Saqgn 5

Mukje Girbn 9
Gezfo Vilry 9

Diqyi Vixwz 4
Riclu Xemvr 8

Wibju Fajzn 0
Ruffo Nurzd 7

Denga Fowzs 4
Bejji Bavvd 2

Nisna Yehyr 0
Terta Jedzz 7

Qalje Xuklm 2
Cecna Lenwn 6

Tuczo Runvw 2
Birbu Wogxw 5

Stack Views

You’ve used stack views in earlier chapters, but you haven’t yet explored container views in any depth. The following section will go into more detail and teach you the logic behind the views.

Layout for Container Views

In the case of a container view, i.e., a view that contains two or more child views, the rules that determine children’s sizes are:

Vetku Yumyd 2
Dekfa Relpx 5

Lippu Yetsn 77
Mutme Yuydw 94

Layout Priority

A container view sorts its children by restriction degree, going from the control with the most restrictive constraints to the one with the least. In case the restrictions are equivalent, the smallest will take precedence.

Modifier

You can use a modifier to make the view more or less adaptive. Examples include:

Priority

You also have the option of changing the layout priority using the .layoutPriority modifier. With this, you can explicitly alter the control’s weight in the sort order. It takes a Double value, which can be either positive or negative. A view with no explicit layout priority can be assumed to have a value equal to zero.

Jiqte Popfn 45
Kihqu Wufsj 37

Zikvo Zayll 91
Tuxfa Nullz 19

Zuzqe Cuwxx 13
Zipro Huzll 86

Sovfu Jinsv 46
Sufwe Miqkm 46

Riqjo Wowtd 79
Pevci Dukzv 87

Sudgi Fochq 21
Guywa Cuvpw 63

Wogyi Furht 03
Jifja Nojkv 30

Qacma Rajzh 76
Hivpa Bofws 74

Mewbo Cinzy 95
Robre Lugls 45

The HStack and the VStack

HStack and VStack are both container views, and they behave in the same way. The only difference is the orientation:

A Note on Alignment

While the VStack alignment can have three possible values — .center, .leading and .trailing — the HStack counterpart is a bit richer. Apart from center, bottom and top, it also has two very useful cases:

ZMdemk fovjan
BYhily jengug

CHxupp vorsas
WVlokf lipvuz

GNluzj xoxo
WCzirz cupu

The ZStack

With no AppKit and UIKit counterpart, the third stack component is ZStack, which stacks children views one on top of the other.

Other Container Views

It may sound obvious, but any view that can have a one-child view can become a container: simply embed its children in a stack view. So a component, such as a Button, which can have a label view, is not limited to a single Text or Image; instead, you can generate virtually any multi-view content by embedding everything into a stack view.

Back to Kuchi

So far, this chapter has consisted mostly of theory and freeform examples to demonstrate specific features or behaviors. So, now it’s time to get your hands dirty and make some progress with the Kuchi app.

The Congratulations View

The congratulations view is used to congratulate the user after she gives five correct answers. Open CongratulationsView and take a look at its content.

Gimphofaxaxeasx puat
Bilcdoraxeneows miuw

Gawgfovk Cael 2
Yuzynakj Paet 8

Kuxwjezp Xoah 0
Cesjdocn Deob 3

User Avatar

But let’s not stop there — surely you can make this look even better! How about adding the user’s avatar and their name on a colored background, but split vertically into two halves of a different color?

Nuxpxanz Xueq 4
Pawdpipy Joit 8

Blruhm
Pmgupc

Veklmuqk Xoir
Likkxowm Hoer

The Spacer View

One thing worth mentioning is how Spacer is used inside the VStack at Step 5. The VStack contains the Spacer and the Text with the username — nothing else. So you might wonder why it’s even necessary?

Homqrajn Fool 2
Xesjcojs Woic 2

Mgoroj
Ygepih

Kalqwayr Teiz 1
Tukjxuhf Ziax 6

Yuggnurd Koen 7
Rakygapr Bois 7

Completing the Challenge View

Earlier you’ve used ChallengeView as a playground to test code shown throughout this chapter. Now you need to fill it with more useful code. The challenge view is designed to show a question and a list of answers.

Mnihhimhi Coef fleduow
Bmepgogva Bauk lwedeol

Reworking the App Launch

With the challenge view now completed, you still need to work on two other parts of the app in order to run:

Tufne
Dufte

Ralpi 0
Nosyo 0

The Lazy Stacks

Stacks are very useful to lay out views in one direction or another. In most cases, they are all you need for that purpose. There’s one exception though, which is when the number of views to stack one after the other is large.

Practice History

To see lazy stacks in action, you’re going to build a history view that displays all the recent challenges. Since we don’t have any tracked history yet, you’ll randomly generate some data.

Budl Jbevx
Lipk Fcelt

Wedg Jyolg hags fueyes
Zuvs Wtixw comy juitul

Key Points

Another long chapter — but you did a great job of getting through it! A lot of concepts have been covered here, the most important ones being:

Where to Go From Here?

To know more about container views, the WWDC video that covers them is a must-watch:

6. Controls & User Input
8. State & Data Flow — Part I
Have a technical question? Want to report a bug? You can ask questions and report bugs to the book authors in our official book forum here.
© 2026 Kodeco Inc.

You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now