20 y/o iOS dev at a job I know won't last.
Building indie apps on the side, not as a hobby, as an exit plan.
Currently going deep on SwiftUI and clean architecture. Documenting everything as I go.
I’ve been stuck lately on App Store Connect and Revenue Cat configuration.
So I decided to test my app with no paywall with all the premium features on. Until I hear back from Apple.
I still have to fix few things in my two apps. All while working my full-time job. But the plan is to do a small circle test as soon as possible.
Trying not to overthink it too much, but I’m already feeling behind
@nalinrajput23 The new MacBooks work so that they almost ignore the battery when it’s full, if it’s charging and just take the power directly from the charger.
It’s not fully ignored, and it’s a little bit more complicated than that, but this is the main idea
@S_N_SH_E_ If this is a start line and they both can learn what the other has, then CS grads win. Just because it's faster to pick up, and a person with CS fundamentals is better with AI than a person who only learned from AI.
@marclou It is a really good question when it's intended to be, and when the other person takes it seriously, too.
Unless you're talking just business, then just ignore it :).
SwiftData vs CoreData
Both persist data on Apple platforms. But they're very different to work with. Here's the quick breakdown:
SwiftData ( new )
Pure Swift, @Model macro
SwiftUI-native
iOS 17+ only
Less boilerplate
Auto schema migration
-------------------------------
CoreData ( battle-tested )
ObjC roots, verbose
Works everywhere
iOS 3+ support
More setup required
Fine-grained control
Bottom line: Starting fresh on iOS 17+? Use SwiftData. Supporting older OS or need advanced queries? Stick with CoreData.
I even tried having them both in the same project for fun, it works. ( it was a side project of course )