Skip to main content
Inspiring
June 6, 2013
Question

Question about Apple's new iPad retina requirement.

  • June 6, 2013
  • 2 replies
  • 1185 views

Apple recently made it a requirement that apps support all retina displays for both iPads and iPhones.

What acceptable options are available in AIR for supporting the iPad Retina display and still meet Apple's new requirement?

Here's my situation :

I've been working on a universal app using AIR 3.6 that works well in all iOS resolutions other than for iPad retina (2048x1536).

When building native support for the iPad retina resolution, the app performance is very poor (due to having to animate and manipulate such large bitmaps). The coding approaches that I've used are supposed to be good on performance, so I doubt that I can optimize things to the point where the performance would be acceptable using the larger art assets.

In comparison, when I use an older version of AIR (3.2) and let the iOS compatibility mode automatically scale up the app to fill the 2048x1536 screen, the performace of the app is just fine (and looks almost identical).

Would using this type of approach cause an app to be rejected by Apple now?

It appears that AIR 3.6 added the ability to restrict just the the iPad high resolution (without restricting iPhones ) using :

<requestedDisplayResolution excludeDevices="iPad3">high</requestedDisplayResolution>

It seems that this would solve my performance issue, but I'm not sure if Apple's new "retina support requirement" would result in my AIR app being rejected if I used this approach to disable iPad Retina support.

Does anyone know if Apple will now accept an app that was built with iPad retina support disabled through this approach?

Another option that I've tried that may be a workable solution is :

During launch when 2048x1536 resolution is detected, the app loads all of the 1024x768 art assets instead and then scales up the app by a factor of two (using scaleX = scaleY = 2).

The above seems to generate acceptable performance. The artworks looks a little blurrier and less crisp using this approach due to the scaling, but is acceptable to me personally. As this is technically using "standard" resolution art assets and scaling them up, would taking this approach get rejected by Apple?

I'm open to any other options/approaches/suggestions to adding iPad retina support that would allow me to address the performance issues on iPad retina and still allow my app to get approved by Apple. I'm just a little bit confused on what constitutes an app having "iPad Retina" support. Does the app just need to be compiled with a newer version of the iOS SDK to get through the approval process, or does this mean something else?

Thanks.

This topic has been closed for replies.

2 replies

Mark.fromOP
Inspiring
June 7, 2013

Seems like you have two options, if you are already scaling stuff down after launching at a higher res why not make it an option. Have a setting for "High Resolution" and one for "High Performance" the difference would is one would run in Retina mode and one would run in standard mode so users with iPad4 and iPhone5 could probably use the High Res but iphone 4 users can switch to the High Performance setting.

The way I have dealt with it is design everything to a 1024 width and 640 height, this is standard Kindle Fire resolution but almost all devices crop the app in a way where all the key features fit on screen, I just had an app approved 2 days ago by Apple using this technique so basically I am running 1024 graphics on the retina screen, they look great (we are only humans and we can't make out every pixel despite what Apple thinks) and the performance is nice as well. I think they worry about apps being stretched for some reason when apple ups a 1024 app to a retina width using their software it looks horrible but if it is done by the developer it looks great. Download a non retina app and try it on a retina iPad or export your app for Standard resolution and check it out vs exporting for high.

I think you will be fine either way.

Adobe Employee
June 7, 2013

We have not seen any rejection yet using <requestedDisplayResolution excludeDevices="iPad3">high</requestedDisplayResolution>. Please go ahead and update how it goes.

Regards,

Nimit