Corona Splash Screen Control - supports different resolutions?

Solar2D General Questions/Discussion
#1

Hello there,

I’ve just bought the annoying Splash Screen Control plugin. 

Reading the documentation I’ve found something I don’t understand:
 

The image will be displayed on a black background and it will match the default orientation of the app, scaled to fit the screen of the current device. You may need to experiment to arrive at the ideal image for your splash screen , but if it’s large enough for the largest device your app is intended to run on, you only need one image.

Does this mean that your plugin doesn’t support different resolutions? We can only choose one image for Android and another for iOS and see if it works?

 What about the 12 different splash screens that were supported on iOS before? (screenshot below)

It looks like I’m paying 99$ and getting worst features than before.

Please help.

#2

Let me help clarify a few things for you.  Our splash screen control does not bypass Apple’s UILaunchImage system. You still need them to prevent iPhone 6, 7, and 6 plus, 7 plus phones (and their "s"models) from going into iPhone 5 compatibility mode. You still need to have the various launch images in your project and you need that large table in the settings->iphone->plist table if you are deploying to iOS.

Corona’s splash screen shows after UILaunchImages. On Android, there is no equivalent to UILaunchImages and the splash screen you had previous to our adding this plugin was to pick up the two lowest resolution, 1.51. aspect ratio files (which would stretch to fill the screen)

Now with the splash screen control plugin, you manage that image file. We will take whatever image you give us, scale it up or down to fit while maintaining it’s aspect ratio so it doesn’t get stretched. But we don’t use the typical Corona scaling (@2x, @4x) for this. You should provide an image that’s large enough to look good on large devices, but memory efficient  enough that it will work on older devices. It’s a balancing act. Remember images look better when scaled down rather than when scaled up. 

Rob

#3

Thanks Rob.

In any case, you should clarify this for everybody, not just for me. This information is not clear in the official documentation.

Regards,

Pablo

#4

Let me help clarify a few things for you.  Our splash screen control does not bypass Apple’s UILaunchImage system. You still need them to prevent iPhone 6, 7, and 6 plus, 7 plus phones (and their "s"models) from going into iPhone 5 compatibility mode. You still need to have the various launch images in your project and you need that large table in the settings->iphone->plist table if you are deploying to iOS.

Corona’s splash screen shows after UILaunchImages. On Android, there is no equivalent to UILaunchImages and the splash screen you had previous to our adding this plugin was to pick up the two lowest resolution, 1.51. aspect ratio files (which would stretch to fill the screen)

Now with the splash screen control plugin, you manage that image file. We will take whatever image you give us, scale it up or down to fit while maintaining it’s aspect ratio so it doesn’t get stretched. But we don’t use the typical Corona scaling (@2x, @4x) for this. You should provide an image that’s large enough to look good on large devices, but memory efficient  enough that it will work on older devices. It’s a balancing act. Remember images look better when scaled down rather than when scaled up. 

Rob

#5

Thanks Rob.

In any case, you should clarify this for everybody, not just for me. This information is not clear in the official documentation.

Regards,

Pablo