Set Minimum Deployment Target for iOS

[Anke]

Is there a way we can set the Minimum Deployment Target to iOS 16 or 17? On older iOS devices (iPhone < 10 with iOS < 16, especially my iPhone 6s with iOS 15.8.6), the layout and handling (switching screens) of my apps is completely different than on newer iPhone models with e.g. iOS 26.x. So I have to exclude older models from the App Store.

Adjusting the Info.plist later might be somewhat complicated.

[ewpatton]

I'll see what we can do.

[Akash_Gite]

We implemented a similar feature on Android where users can configure the minSdkVersion at build time instead of hardcoding it.

Perhaps we could consider introducing a comparable setting for iOS, allowing the Minimum Deployment Target to be configurable during the build process rather than modifying Info.plist manually afterward.

This could provide more flexibility and maintain consistency across platforms.

[Anke]

@Akash_Gite

We implemented

Who is "we"?

[Akash_Gite]

I meant contributors — I worked on the Android minSdkVersion configuration feature recently. Apologies for the ambiguity.

[Anke]

@Akash_Gite

I worked on the Android minSdkVersion configuration feature recently.

It shouldn't be a problem, as it has been possible for a long time in all other AI2 distros (Kodular, Niotron, ...).

[Akash_Gite]

If it's already supported in other AI2 distributions, it may be possible to introduce a similar configuration layer in the iOS build system rather than requiring manual Info.plist edits.

I’d be happy to look into how they implemented it and see if we can adapt a clean approach here.

[fbeleznay]

I have a question related to the content of your message rather than the title. Please let me know if I should start a new thread instead of asking my question here.

You say that the layout is different depending on the iOS version. Can I please ask a bit of details on this? Does this mean that the layout I set in the designer can look different on different iOS versions? I am using all options for setting width and height of components in the designer. For some I use "automatic", for some I use "fill parent" for some I use the dimension in "pixels" for some I use the dimension in "percentages". Is any of these problematic? Should I avoid any of these?

I also use a few vertical scroll arrangements, and my overall screen is not scrollable.

Can I also ask how the switching screens is different? Is it about how the old screen visually disappears and how the new one appears?

Sorry about these general questions, but I am in the process of developing an app with the aim of working on both Android and iOS and it would be good to know the problematic parts to avoid using.

[Anke]

@fbeleznay

Can I also ask how the switching screens is different?

Switch screens on iOS — (1) Screen1 is not closed (2) Screen1 is closed

Here's a small, simple test AIA for iOS that switches between two screens. Using Button1 follows method 1* (i.e., Screen 1 isn't closed). Using Button2 follows method 2 (Screen 2 opens while Screen 1 is closed). Tests must be performed using the IPA. Using method 1 (Screen 1 isn't closed), even this mini-app experiences a noticeable delay when loading Screen 2 (some components like sliders and checkboxes appear distorted for about 1 second). This behavior doesn't occur with Method 2. Of course…

@fbeleznay

You say that the layout is different depending on the iOS version.

Yes, I tested my app(s) on different iPhones / iPads with different iOS version (iOS 15.8.6 - 25.x). And there are significant differences that can't be masked by scrollable arrangements. Of course, it also depends on the size of older devices. You'll need to test your app yourself on various physical (real) devices.