With all the new icon dimensions being created time-after-time with the release of new Android/iOS versions, it would be easier for developers if we could include a large app icon (ex. 512x512) with our project and then have Corona create the necessary icon files and (for iOS) the plist settings in the app bundle.
There are already lots of apps in the Mac App Store that do this (I use Iconify). Take your 512 icon and drag and drop it into the program, it’s that simple! I see no need for this to be part of Corona.
It’s just one more time saver towards that “x10 faster to develop & deploy with” promise… If it’s so simple then why not include it in the build process…
Would be nice, but we also have to remember that auto-scaled icon are not always the best (resolution, aliasing). However, if auto-scaling would give us satisfying results then it’s worth - I’m always the fan of making this automatic. +1
I’ve made a few observations. This is brainstorming, feel free to comment.
Observation 1: Since there is no real distinction between tablet and phone apps on Android, I’d suggest that all Android app icons would be generated regardless of any phone/tablet/phone+tablet setting.
Observation 2: There might be some who would still like to have manual control over the iOS icons (ex. different icons for iPhone/iPad versions). A suggestion would be that the presence of a CFBundleIconFiles entry in build.settings would disable auto-generation. This would also have the effect of being backwards-compatible with older projects where auto-generation wasn’t available.
Observation 3: Why not let CoronaLabs lead the way in vector graphics and give us the option to provide an SVG icon file, and have the build script spit out the appropriate PNG files from that.
There are already lots of apps in the Mac App Store that do this (I use Iconify). Take your 512 icon and drag and drop it into the program, it’s that simple! I see no need for this to be part of Corona.
It’s just one more time saver towards that “x10 faster to develop & deploy with” promise… If it’s so simple then why not include it in the build process…
Would be nice, but we also have to remember that auto-scaled icon are not always the best (resolution, aliasing). However, if auto-scaling would give us satisfying results then it’s worth - I’m always the fan of making this automatic. +1
I’ve made a few observations. This is brainstorming, feel free to comment.
Observation 1: Since there is no real distinction between tablet and phone apps on Android, I’d suggest that all Android app icons would be generated regardless of any phone/tablet/phone+tablet setting.
Observation 2: There might be some who would still like to have manual control over the iOS icons (ex. different icons for iPhone/iPad versions). A suggestion would be that the presence of a CFBundleIconFiles entry in build.settings would disable auto-generation. This would also have the effect of being backwards-compatible with older projects where auto-generation wasn’t available.
Observation 3: Why not let CoronaLabs lead the way in vector graphics and give us the option to provide an SVG icon file, and have the build script spit out the appropriate PNG files from that.