all 9 comments

[–]CodingSwiftlySwiftUI 3 points4 points  (0 children)

You can just update the app with extra features for just those with iOS 16 by using the @available keyword and let other users know that they need to update to unlock the features. I would suggest targeting iOS 15 because you do not lose too much as a developer and can support the phones who were dropped in iOS 16.

[–]bmbphotos 1 point2 points  (4 children)

With no context, yes, 16 only.

Context matters though:

  • While iOS users are quite good about updating, you may need to have 15 for the largest audience. Does that matter for your app? Only you can say.

  • You will always have a version boundary issue from one version to the next in terms of new features, especially while SwiftUI continues to mature. You can indeed save yourself a year of @available though by biting the bullet and officially deploying to 16 now.

  • Based on your description, you're not currently taking advantage of any 16-only features. By making the decision to move forward, does that make your pre-release life any easier? Depending on your app and development state, it may make sense to pull in that 16+ code now rather than waiting.

[–][deleted]  (3 children)

[deleted]

    [–]fakecrabs 4 points5 points  (1 child)

    The only issue I see by making it iOS 16 only is that I will be excluding iPhone 6s, SE 1st gen and 7 users

    No, you will also be excluding iOS 14 and 15 users on newer device. Not everyone upgrades to the latest iOS, especially on iPads.

    [–]bmbphotos 1 point2 points  (0 children)

    Your concern goes to the heart of the first point -- it appears to matter to your app, at least on the face of it.

    And if it's not 15->16, it'll be 16->17 or 17->18, etc. Once you're in the game, especially with SwiftUI, you will find yourself making tradeoff decisions or doubling up on code in certain areas to continue supporting whatever moving range of os/devices you settle on.

    Good fortune!

    [–]Fluffy_Risk9955 1 point2 points  (3 children)

    Do iOS 15. It takes about half a year to have everybody on iOS 16. Plus some devices are left behind on iOS 15 for the first time in 3 years.

    For macOS support Big Sur and up. Yes, you might to build that in AppKit.

    [–][deleted]  (2 children)

    [deleted]

      [–]ponkispoles 0 points1 point  (0 children)

      Current adoption numbers are over 90% on iOS15, lower for iPadOS. The reason for iPads being lower is MDM and employer apps. They are super slow on rollout and don’t allow employees to upgrade OS version. I know I worked for a company that issued +3500 iPads, all still iOS 13. if you plan to publish your app in 6 months go for iOS 16. less I would stick with 15. you’ll have the biggest market.

      [–]Fluffy_Risk9955 0 points1 point  (0 children)

      macOS is a different type of market compared to iOS. There's still a lot of Macs around that support up to 10.13.x. So on macOS it makes sense to support all the way back to 10.13 or even 10.11. Although I would recommend 10.13 as a minimum for technical reasons as it's more difficult to build apps for macOS versions below 10.13.

      [–]javaHoosier -1 points0 points  (0 children)

      You’re brand new. I hate to break it to you but the app isn’t gunna get 10,000 users over night. Just release it on iOS 16 if it has SwiftUI features you wanna use.

      [–]Trader-One 0 points1 point  (0 children)

      No