3 ms·

I’m actually really looking forward to this. I tried building a few apps in 100% SwiftUI coming from React/Node.js and it was a pretty major pain. I also don’t

I’m actually really looking forward to this. I tried building a few apps in 100% SwiftUI coming from React/Node.js and it was a pretty major pain. I also don’t know UIKit so I couldn't easily fallback.

koinedad 3y ago
The typing of NSPredicate seems like a big upgrade as well. I went through all the old outdated docs for core data but still things aren’t very clear in my mind. Hoping the typing helps
yreg 3y ago
I had the same experience as you. Using CoreData with SwiftUI feels strange. Unfortunately if we start using this now we can only target iOS 17+.
- valianteffort 3y ago
  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.
  - yreg 3y ago
    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.
    - valianteffort 3y ago
      I mean it's not too complicated to add OS specific exceptions in Swift. You can build your app for the lowest version you want to support and add newer OS features a la carte.
    - szundi 3y ago
      While you're finishing it, it goes to 5%
      - yreg 3y ago
        So be it. I released a year ago and for now I support iOS 14.0 and above. I just think it's the right thing to do when reasonable enough. I will probably rewrite some parts to more modern SDKs and cut that support at some point, but I don't want to do it just for the sake of using the newest thing.
    - Jaxan 3y ago
      Thanks! I appreciate this attitude as I’m stuck on iOS 15, but still like my phone as it is.
  - myko 3y ago
    > Nowhere near the fragmentation of Android This is irrelevant, though, as the hottest Android framework (Jetpack Compose) is usable on devices released 9 years ago. This is the advantage of the way Google deploys major improvements vs Apple.
  - tadfisher 3y ago
    If I look at our stats (banking app targeting startups), over 99% are using Android 9 or later, which is in the same ballpark. I think for both platforms, OS fragmentation depends heavily on your target audience, moreso than the platform stereotypes.
mritchie712 3y ago
Try it with ChatGPT. I've never built an iOS app and it took me 5 minutes to get a SwiftUI app running with gpt-4.
- koinedad 3y ago
  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.
  - mritchie712 3y ago
    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.
    - koinedad 3y ago
      That’s pretty amazing, don’t think I have access to GPT-4, need paid subscription for that right?

koinedad 3y ago

The typing of NSPredicate seems like a big upgrade as well. I went through all the old outdated docs for core data but still things aren’t very clear in my mind. Hoping the typing helps

yreg 3y ago

I had the same experience as you. Using CoreData with SwiftUI feels strange. Unfortunately if we start using this now we can only target iOS 17+.

valianteffort 3y ago
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.
- yreg 3y ago
  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.
  - valianteffort 3y ago
    I mean it's not too complicated to add OS specific exceptions in Swift. You can build your app for the lowest version you want to support and add newer OS features a la carte.
  - szundi 3y ago
    While you're finishing it, it goes to 5%
    - yreg 3y ago
      So be it. I released a year ago and for now I support iOS 14.0 and above. I just think it's the right thing to do when reasonable enough. I will probably rewrite some parts to more modern SDKs and cut that support at some point, but I don't want to do it just for the sake of using the newest thing.
  - Jaxan 3y ago
    Thanks! I appreciate this attitude as I’m stuck on iOS 15, but still like my phone as it is.
- myko 3y ago
  > Nowhere near the fragmentation of Android This is irrelevant, though, as the hottest Android framework (Jetpack Compose) is usable on devices released 9 years ago. This is the advantage of the way Google deploys major improvements vs Apple.
- tadfisher 3y ago
  If I look at our stats (banking app targeting startups), over 99% are using Android 9 or later, which is in the same ballpark. I think for both platforms, OS fragmentation depends heavily on your target audience, moreso than the platform stereotypes.

mritchie712 3y ago

Try it with ChatGPT. I've never built an iOS app and it took me 5 minutes to get a SwiftUI app running with gpt-4.

koinedad 3y ago
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.
- mritchie712 3y ago
  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.
  - koinedad 3y ago
    That’s pretty amazing, don’t think I have access to GPT-4, need paid subscription for that right?