I've done some #SwiftUI lately for @pushheroapp@PastePalApp , and amazed by how easy and fun it is to make apps. If you want to get into SwiftUI but don't know where to start, here are my recommended resources #iosdev
Thread 👇
1) First thing first is @Apple official guides. Apple has done a stunning job to make SwiftUI tutorials fun and interactive
7) Taking about video series, I also want to highlight @objcio excellent SwiftUI Layout Explained.
I used to use @LinkedIn LayoutKit framework so I thought I understand SwiftUI enough. But after the series by @chriseidhof@floriankugler I understand more how SwiftUI is built
Every time I google something about SwiftUI, @twostraws has already an answer ready for me ❤️
9) 🥁 to the hardcore part SwiftUI Lab swiftui-lab.com by Javier
This blew my mind on how he managed to deep dive into SwiftUI with lots of cool insights given the lack of SwiftUI documentation at time
10) Talking about @SwiftUILab without mentioning this app A Companion for SwiftUI swiftui-lab.com/companion/ is a no no. This app worths every penny to play and understand SwiftUI
11) Next is Netsplit netsplit.com/swiftui which I learned a lot about SwiftUI layout system, flexible frames, and how Stack works. Unfortunately, the site is down and I can only read from archive now
13) What SwiftUI blogs should I read? There are plenty, but here come first in my mind
- @swiftbysundell by @johnsundell if you want to learn how to write better Swift and SwiftUI code, this site is a must-visit
14) Swift with Majid by @mecid I was lucky enough to meet @mecid at WWDC2019. Since then he has amazed us by weekly articles about new SwiftUI APIs and how to use them
15) Another interesting blog is Five Stars by @zntfdr talking about practical tips for building SwiftUI applications. He is also the author of WWDC Notes, which provides quality notes during WWDC
16) Learning from open source. Nothing is better than get a hand-on on existing open-source projects and learn best practices from it
1) Core Data is more than just SQLite wrapper, it manages objects, relationships, fetching, faulting, ...
2) Having 2 context: 1 main and 1 background that are both backed by the persistent coordinator. In modern Core Data stack, NSPersistentContainer has default viewContext already, we just need another newBackgroundContext
1) Scratch your own itch. If you don't have any itch to scratch, stop here. This is awkward. Go travelling. Go exploring the world. The world always has problems and needs solution.
2) Build any service, app or website. Along the way you'll find tons of things you need that and unsolved by existing solutions, and tons of things you can improve upon.
3) Sign up for some paid newsletters to find ideas. This is the worst. This is like someone browsing through a tatoo catalog. You're doing things for trend, for money, not for your self drive 👎
1) "earning up to $1 million" means proceeds, not sales. This is what we get after Apple's cut. "up to" means $999.999
2) "if they earned up to $1 million in proceeds during the previous calendar year". This means that if $1M is surpassed, the standard rate (30%) kicks in for the rest of the year, and also next year.