Dynamic scaling and building

Getting Started Newbie Questions
#1

Hi,

When using dynamic scaling one ends up having multiple versions of the same image. When you build, this makes the end product unnecessarily huge, since when you submit your app to the marketplace you can upload different builds for different flavors of the devices. 

Does this mean that I need to keep multiple branches of my source, one branch per scale? Or is there a nicer way to make Corona just build the end product for a specific scale? What’s the most common way to handle this?

Thanks,

George

#2

Hi George.  A lot depends on the app itself.  For the longest period of time, only Apple needed @4x assets for the Retina iPads, and all Android devices could live with the @2x assets.  At that time I had my master folder for iOS since that’s the main market I was targeting.  Then I made a 2nd Android folder and copied everything over then removed the @4x assets to keep the app smaller.

However today, with the Nook HD, Kindle Fire HD, the Nexus 10 and several other android’s pushing that 1080p range (1900ishx1100ish) size, having those @4x graphics is going to make those devices look nicer.

Today you probably don’t have to split them.

#3

Gotcha. Thanks, Rob.

#4

Hi George.  A lot depends on the app itself.  For the longest period of time, only Apple needed @4x assets for the Retina iPads, and all Android devices could live with the @2x assets.  At that time I had my master folder for iOS since that’s the main market I was targeting.  Then I made a 2nd Android folder and copied everything over then removed the @4x assets to keep the app smaller.

However today, with the Nook HD, Kindle Fire HD, the Nexus 10 and several other android’s pushing that 1080p range (1900ishx1100ish) size, having those @4x graphics is going to make those devices look nicer.

Today you probably don’t have to split them.

#5

Gotcha. Thanks, Rob.