The launch image does not fully fill the screen?

Solar2D General Questions/Discussion
#1

I created several launch images  (as the project build setting tutorial suggests: http://docs.coronalabs.com/guide/distribution/buildSettings/index.html#launch-images)

Default.png 320 × 480

Default@2x.png 640 × 960

Default-568h@2x.png 640 × 1136

Default-Portrait.png 768 × 1024

Default-Portrait@2x.png 1536 × 2048

Default-Landscape.png 1024 × 768

Default-Landscape@2x.png 2048 × 1536

However, for many devices, when the app starts, the launch image does not fully fill the screen. I use white background, so it’s obvious that some area is black.

My config.lua is 

content = {         width = 320,         height = 480,          scale = "letterbox",         imageSuffix =         {             ["@2x"] = 1.5,             ["@4x"] = 3.0,         },     }

Do I miss some sizes for the launch image?

#2

Are you building for iOS or Android?

#3

Both.

I can see there is black area on the left and right in iPad simulator already.

There are black area on the top and bottom in Galaxy S3 simulator.

I tested with real device, such as Galaxy Tab 3, there is black area on the top and bottom.

iPhone 4S has no black area.

#4

Android does not actually use a Launch image.  Corona attempts to load Default.png because it was something Android users wanted.  We don’t look for specific images based on the aspect ratio of the device.   Ideally you would not include an Default.png for Android and if you want a Splash screen, you would build your own, but iOS uses them and many people want to use that Launch image to be their Splash screen.

Probably the best thing is to only include a solid black Default-568h@2x.png file (640x1136) to trigger tall mode on the iPhone 5’s.  By making it black, it will match the way Corona starts up.  Then you can implement your own splash screen that matches the right Aspect ratio of the device you are on. 

#5

Ok, I see… I think I got it now.

You are right, I also use the launch image as the splash screen. And I see Apple doesn’t suggest so.

If I make my own splash screen, the only concern is that the splash screen does not come immediately after the app is launched. Instead, it’s the launch image, which gives users better responsive UI experience.

#6

Corona should load pretty quickly and if your splash screen is the first thing and you hide your rest of your loading behind it, it shouldn’t be much of a difference.

#7

Are you building for iOS or Android?

#8

Both.

I can see there is black area on the left and right in iPad simulator already.

There are black area on the top and bottom in Galaxy S3 simulator.

I tested with real device, such as Galaxy Tab 3, there is black area on the top and bottom.

iPhone 4S has no black area.

#9

Android does not actually use a Launch image.  Corona attempts to load Default.png because it was something Android users wanted.  We don’t look for specific images based on the aspect ratio of the device.   Ideally you would not include an Default.png for Android and if you want a Splash screen, you would build your own, but iOS uses them and many people want to use that Launch image to be their Splash screen.

Probably the best thing is to only include a solid black Default-568h@2x.png file (640x1136) to trigger tall mode on the iPhone 5’s.  By making it black, it will match the way Corona starts up.  Then you can implement your own splash screen that matches the right Aspect ratio of the device you are on. 

#10

Ok, I see… I think I got it now.

You are right, I also use the launch image as the splash screen. And I see Apple doesn’t suggest so.

If I make my own splash screen, the only concern is that the splash screen does not come immediately after the app is launched. Instead, it’s the launch image, which gives users better responsive UI experience.

#11

Corona should load pretty quickly and if your splash screen is the first thing and you hide your rest of your loading behind it, it shouldn’t be much of a difference.