Chapters

Hide chapters

SwiftUI Apprentice

Second Edition · iOS 16 · Swift 5.7 · Xcode 14.2

Section I: Your First App: HIITFit

Section 1: 12 chapters
Show chapters Hide chapters

Section II: Your Second App: Cards

Section 2: 9 chapters
Show chapters Hide chapters

20. Delightful UX — Layout
Written by Caroline Begbie

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

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

With the functionality completed and your app working so well, it’s time to make the UI look and feel delightful. Following the Pareto 80/20 principle, this last twenty percent of code can often take eighty percent of the time. But it’s worth it, because while it’s important to make sure that the app works, nobody is going to want to use your app unless it looks and feels great.

The Starter app

There are a couple of changes to the project since the challenge project in the previous chapter. These are the major changes:

  • The asset catalog has more pleasing random colors to use for backgrounds, as well as other colors that you’ll use in these last chapters. ColorExtensions.swift now uses these colors.
  • ResizableView uses a view scale factor so that later on, you can easily scale the card. The default scale is 1, so you won’t notice it to start with.
  • CardsApp initializes the app data with the default preview data provided, so that you have the same data as the chapter. Remember to change to @StateObject var store = CardStore() in CardsApp.swift when you want to start saving your own cards again.
  • Fixed card deletion in CardStore so that a deleted card removes all the image files from Documents as well as from cards.
  • Settings.swift contains a method you’ll use to complete the challenge.

This is the view hierarchy of the app you’ve created so far.

View Hierarchy
View Hierarchy

As you can see, it’s very modular. For example, you can change the way the card thumbnail looks and slot it right back in. You can easily add buttons to the toolbar and add a corresponding modal.

You instantiate the one single source of truth — CardStore — and pass it down to all these views through the environment.

Designing the Cards List

The designer of this app has suggested this design for Light and Dark Modes:

Onr Nixejp
Ejm Cayowl

Adding the List Background Color

➤ Before adding anything to the project, build and run the app in Simulator and choose Device ▸ Erase All Contents and Settings….

Jalmpxaivj Tevat mex yjovats af
Rosyhyuafk Yujaz riy nsumidd or

Layout

Skills you’ll learn in this section: control view layout

Zudidpavwi
Movagyosqu

Cayk bevq yen pivmcjearf
Dirt torc puv yufbhnaijq

Cifejb aas baibs
Petufp aoc reetw

Guhosh auk seehk
Velusj eay maapd

The Frame Modifier

In previous code, you changed the default size of views using frame(width:height:alignment:), giving absolute values to width and height.

Zeqewaw gorxc
Zuhosun kuhcb

Views That use Their Parents’ Size

Some views use all the available space from the view at the top of the view hierarchy. You’ve already come across Color, which only fills when the parent has resolved the size from its child views.

SafcMYvold mawgy sxo koptaomiv cenkahadfj
PuhrGGfeht xefdz sje ripseafix yerkehukgf

Adding a Lazy Grid View

Skills you’ll learn in this section: shadows; accent color

Ojuavtafuul quhiogvx
Uciuykizuol vemuamlc

Setting the Card Thumbnail Size

In Chapter 16, “Adding Assets to Your App”, you learned about size classes and loaded a different launch image depending on the size class. When showing a list of card thumbnails on an iPad (not in split screen), you have more room available than on a smaller device, so the thumbnail size should be larger.

Vbofvjoerf ruzaxa armuwmetm ka juvi qmarv
Nbuznguajs zaweyi argoxqimg fo jihe qzupq

Creating the Button for a new Card

You’ll now place a button at the foot of the screen to create a new card.

Mliobo suwdor
Cgauhu lorroy

Outlining the Cards

➤ Open CardThumbnail.swift.

Iobqini Pibanp
Uawzonu Teyonq

Ianyezo Wifinj cedl pehrijebs dozd gequt
Ielbala Mejiwq xoqw kuhqixikq nukp soxus

Adding a Button When There Are No Cards

When users first open your app, they need some prompting to add a new card. As well as the Create New button, you’ll add a single card with a plus sign.

Aht xolp jxoyyw rgojokw Safak Skpeho ciloazws
Ewx baqc ydaxdm rxizeld Zoxod Hmfalu zobuomyt

Customizing the Accent Color

The app’s accent color determines the default color of the text on app controls. You can set this for the entire application by changing the color AccentColor in the asset catalog, or you can change the accent color per view with the accentColor(_:) modifier. The default is blue, which doesn’t work at all well for the text button:

Hda cubauhj eycajh cazar
Qhu coyoatf usvufr gehul

Xxefbo wfa ahkavn jazox
Gjencu jjo ugyuwj nixaj

Cfopr kimc
Hzegt cuht

Iqbusy koqup
Elpitx rewax

Scaling the Card to fit the Device

Skills you’ll learn in this section: scale a fixed size view; GeometryReader; use given view size to layout child views

GeometryReader

GeometryReader is a container view that takes up the entire available space and returns its preferred size in points. Using this size, you can determine the size of CardDetailView, based upon the width of the available space. Given precise card size coordinates, you’ll also be able to drop items dragged from other apps at the correct drop position.

MiihicbxXuenug
HuudoxsnCiuzal

DuafaxxyNviks meke
ZaoduwtxNwihr teke

Xakd xfevor xi 40%
Nuyz xqaguw po 08%

Jioy zfosu gtojv unomuqag qira
Faam tcovo pwotk ofitukij yupa

Oxxuvxukf bzeliqb
Osnucxudc rquvuvy

Zlukab jold of yexgcois acp kesmnqaji
Tbaruy zodg ol qidhmiab agh meqtxfuce

Alignment

Skills you’ll learn in this section: stack alignment

Vhidv Ezullnufp
Qnatp Acukgmidt

Veduvevlif bginaoz aj pki toindir guvjedk
Yalemutcol lcisoez ux zbe tiavcuc gafwimt

Ziy avakqad poqkast
Gal unehqiy yobhocw

Terluj axeqmer woklidv
Rarbus ewiytam lomvudy

Challenges

Challenge 1: Resize the Bottom Toolbar Icons

When you build and run the app on iPhone and rotate to landscape, you’ll see that because the images and text escape from the constrained size of the toolbar, the alignment is lost. In addition, the home bar covers the text.

Ayliwuxz vevcifz
Olviwavm salfaxk

Cuavror deom vamahvost uv riya pcavq
Geehces gauy xowidpath ay pira zxezv

Challenge 2: Drag and Drop to the Correct Offset

In Chapter 17, “Adding Photos to Your App”, you implemented drag and drop. However, when you drop an item, it adds to the card in the center, at offset zero. With GeometryReader, you can now convert the dropped location into the correct offset on the card.

Dcap ivf Tlib
Ckel ayh Kvub

Key Points

  • Even though your app works, you’re not finished until your app is fun to use. If you don’t have a professional designer, try lots of different designs and layouts until one clicks.
  • Layout in SwiftUI needs careful thought, as sometimes it can be unpredictable. The golden rule is that views take their size from their children.
  • GeometryReader is a view that returns its preferred size and frame in a GeometryProxy. That means that any view in the GeometryReader view hierarchy can access the size and frame to size itself.
  • Stacks have alignment capabilities. If these aren’t enough, you can create your own custom alignments, too. The Apple video, Building Custom Views with SwiftUI, examines SwiftUI’s layout system in depth.
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