Earlier quoted context omitted.
They actually can figure that out, though [0]. I hope this can solve some of it because their deployment model is the dumbest fucking thing. I'm glad they figured out how to backport async/await, it's just impossible to use in a serious library otherwise. [0] https://github.com/apple/swift-evolution/blob/main/proposals...
Over 80% of iPhones are running the latest version. I’ll take that any day as a developer over the Android hellscape of versions that need to be tested for and supported. https://www.macrumors.com/2023/06/01/apple-shares-ios-16-ado...
SwiftData
51–60 of 109 posts
Re: SwiftData
#52Earlier quoted context omitted.
Apple has like >80% of devices released in last 5 years on iOS 16. Nowhere near the fragmentation of Android. Given only a minority of users are not on the latest major OS, worrying about supporting older firmware, at least in this case, is not worth the time or money.
I know, but even with my small app I don't feel comfortable dropping support for the 20% users who are behind. And if I'm supposed to maintain both the old and the new API in parallel then why bother. Now for new apps I can see going all in with the latest SDKs.
Re: SwiftData
#53Earlier quoted context omitted.
A basic app or one you created a bunch of custom logic, cloud sync integration, etc? I can build a simple app in a minute or two.
Yes, custom logic and cloud sync. It tracks sprint workouts with GPS / pedometer. It's not Uber, but it's a good bit beyond a hello world.
Re: SwiftData
#54Re: SwiftData
#55One of the things I like about CoreData is that all the relationships and entities are defined in one file, and its easier to browse the history of that schema to see how the models evolved. One of the things I dislike though is that it doesn't interop well with swift types and almost everything has to be marked as optional. It looks like this SwiftData solves the second problem, but since definitions are spread acro…
put them in one file then.
Re: SwiftData
#56One of the things I like about CoreData is that all the relationships and entities are defined in one file, and its easier to browse the history of that schema to see how the models evolved. One of the things I dislike though is that it doesn't interop well with swift types and almost everything has to be marked as optional. It looks like this SwiftData solves the second problem, but since definitions are spread acro…
Re: SwiftData
#57I still prefer Realm though. It has a much more flexible days model and I can use it both on iOS and Android with seamless sync between the two.
When Apple adds cross-platform sync to SwiftData I’ll consider it. Until then it is dead in the water.
Re: SwiftData
#58Earlier quoted context omitted.
Over 80% of iPhones are running the latest version. I’ll take that any day as a developer over the Android hellscape of versions that need to be tested for and supported. https://www.macrumors.com/2023/06/01/apple-shares-ios-16-ado...
> Over 80% of iPhones are running the latest version. If the past is any indicator, the number will be over 90% by the time iOS 17 ships this fall.
Re: SwiftData
#59Earlier quoted context omitted.
> Over 80% of iPhones are running the latest version. If the past is any indicator, the number will be over 90% by the time iOS 17 ships this fall.
I doubt iOS 17 will be adopted faster than previous versions. For one, they are dropping support for multiple device generations this time.
Re: SwiftData
#60Earlier quoted context omitted.
Apple has like >80% of devices released in last 5 years on iOS 16. Nowhere near the fragmentation of Android. Given only a minority of users are not on the latest major OS, worrying about supporting older firmware, at least in this case, is not worth the time or money.
I know, but even with my small app I don't feel comfortable dropping support for the 20% users who are behind. And if I'm supposed to maintain both the old and the new API in parallel then why bother. Now for new apps I can see going all in with the latest SDKs.