|< Answering the big question: should you learn SwiftUI, UIKit, or both?||Migrating from UIKit to SwiftUI >|
Fully updated for Xcode 11.2
This guide is called SwiftUI by Example, because it focuses particularly on providing as many examples as possible, with each one solving real problems you’ll face every day.
I have literally tried to structure this so that almost every entry starts with “How to…” because this is about giving you hands-on code you can use in your own projects immediately. That also means I’ve tried to get to the point as fast as possible and stay there, so if you’re looking for a longer, slower introduction to SwiftUI I’m afraid this isn’t it.
If you’ve already grabbed the basics of SwiftUI and just want code that solves your problems, by all means just jump in wherever interests you.
My code examples are specifically written for folks who are following along linearly, so if you’re want to make those changes you may need to do a little light editing to make it fit your code.
If you’re just starting out with SwiftUI you should read this guide in a linear order – just keep reading and clicking Next until you’re done. I’ve written the guide so that later chapters build on earlier ones, so a linear approach really is a good idea.
If this is you, you should start by creating a new iOS app using the Single View App template. It doesn’t matter what you call it, but I would like you to make sure and check the “Use SwiftUI” box otherwise the rest of this guide will be very confusing indeed.
SPONSORED Instabug helps you identify and resolve severe crashes quickly. You can retrace in-app events and know exactly which line of code caused the crash along with environment details, network logs, repro steps, and the session profiler. Ask more questions or keep users up-to-date with in-app replies straight from your dashboard. Instabug takes data privacy seriously, so no one sees your data but you! See more detailed features comparison and try Instabug's crash reporting SDK for free.