Using #available(iOS 17, *) for Swift Student Challenge

Hello there,

Are we allowed to use iOS 17 features if they’re wrapped in an ‘if #available(iOS 17, *)’ check? I.e. the app would still function fine on iOS 16, but perhaps have an optional feature that works slightly better on iOS 17”

Thanks!

Up vote post of snoopdog144 Down vote post of snoopdog144
419 views
Posted by
snoopdog144
Reply
Add a Comment

Accepted Reply

For the latest info on this topic, see Swift Student Challenge deployment targets.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Post marked as solved
Add a Comment

Replies

That's what's happening everyday in many apps. And it is recommended by Apple to adopt most recent features.

Eligibility criteria state:

Your app playground must be built with and run on Swift Playgrounds 4.4 or later (requires iPadOS 16 or macOS 13.5, or later) or Xcode 15 on macOS 13.5, or later. You may incorporate the use of Apple Pencil.

So you are safe with iOS 16 (I even assume they will test on iOS 17).

So this approach to take profit of most recent API whilst maintaining compatibility with previous releases is OK. I could not see any reason for different conclusion.

Good luck.

Posted by
Claude31
Up vote reply of Claude31 Down vote reply of Claude31
Add a Comment

Playgrounds may be built to target iOS 16/iPadOS 16 or later. This includes the use of iOS 17/iPadOS 17 only.

Posted by
aivanovski
Post not yet marked as solved Up vote reply of aivanovski Down vote reply of aivanovski
Add a Comment

For the latest info on this topic, see Swift Student Challenge deployment targets.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Post marked as solved
Add a Comment