Although the app we were building wasn’t itself difficult, getting there took quite a bit of learning – we had to cover
@ObservedObject, and more. Some of those things – particularly
Codable – have only been introduced at a high level in this project, which is intentional; we’ll be getting into them more later on.
Now that your SwiftUI skills are coming along, I hope you noticed we were able to skip past some parts with very little explanation. For example, you know very well how to create forms with text fields and pickers because we’ve already covered that extensively, which means we can spend our time focusing on new stuff.
Anyone can sit through a tutorial, but it takes actual work to remember what was taught. It’s my job to make sure you take as much from these tutorials as possible, so I’ve prepared a short review to help you check your learning.
One of the best ways to learn is to write your own code as often as possible, so here are three ways you should try extending this app to make sure you fully understand what’s going on.
ContentViewso users can delete rows more easily.
ContentViewto contain some styling depending on their value – expenses under $10 should have one style, expenses under $100 another, and expenses over $100 a third style. What those styles are depend on you.
AddView. If you enter “fish” or another thing that can’t be converted to an integer, show an alert telling users what the problem is.
SPONSORED Building in-app subscriptions are hard – especially cross-platform. RevenueCat makes it simple. With their native SDKs, you can implement a custom subscription model for your app in hours, not months.
Link copied to your pasteboard.