Monetization is crucial for mobile apps to succeed (or any kind of software for that matter), so we want to make sure you always have plenty of different ways to make money from your apps made with Corona. With our previous Corona SDK release, you could make money from paid apps, in-app purchases, virtual currency, and a single ad network.
Since then, we’ve heard about issues with low fill rates which caused dissatisfaction with some developers. Well, we’ve been listening closely and wanted to provide you the best solution we possibly could.
So with this new release, you’ll be happy to know that we’ve partnered with yet another ad provider: inneractive. But this is no regular ad provider. The inneractive network is what’s known as an “ad mediation network”, which means that inneractive is really a way to connect to, and optimize across, many different ad networks — giving you access to ads from over 100 different ad networks across the globe!
With this new release, you now have more monetization options and should see better results.
To get started, see the Implementing Ads guide. Also see the new inneractive sample at /SampleCode/Ads/Inneractive in the CoronaSDK folder for a working example. The inneractive ad network allows you to utilize banner ads, text ads, and even full-screen ads to be integrated in your app however you see fit.
Kindle Fire and NOOK
It’s always exciting to support a new platform, because as always with Corona, you get to use the same project, choose a build target, and deploy! With the this latest release, we’re happy to announce that Corona SDK now supports two additional platforms: Amazon Kindle Fire and Barnes & Noble’s NOOK Color!
But there’s one important caveat: Although both platforms are technically Android under-the-hood, they both plug into completely different app ecosystems, each with their own special requirements, so we’re treating them as a completely new platform.
The benefits of building for the Kindle Fire and NOOK platforms now include (but are not limited to):
- Establishing a presence in the brand new up-and-coming markets before they become saturated with competition.
- Reaching completely different audiences (not everyone who has a Kindle or NOOK has an iPad, and vice-versa).
- Taking full-advantage of Corona’s cross-platform capabilities. Going the traditional route, it could take several months to port a single app across four different platforms. With Corona, you can knock four down at once!
- And of course, targeting these platforms gives you the perfect excuse to present your spouse as to why you just HAVE to buy the hottest new tech gadgets.
Our official solution to scene management and transitions — the Storyboard API — includes:
- Easily create scenes with a single function call (or split scenes up into separate, external modules).
- Manage scenes and transitions through Corona events.
- Tons of great-looking scene transition effects.
- Auto-freeing of unused scene resources on low memory.
To get started using this brand new API, and to see everything it has to offer, please see the Storyboard API documentation. Additionally, you can see a working example at /SampleCode/Interface/Storyboard in the CoronaSDK folder.
Native UI in Mac OS X Simulator
We’ve made a significant addition to the Mac simulator in this release, and that is the ability to see and test native UI elements (such as text fields, message boxes, web popups, etc) in the Corona Simulator!
Previously, you had to build for device (or the Xcode simulator) to test out things like text fields, web popups, etc. but now—for Mac users—you get to skip those extra steps and test these elements directly—this helps make already-fast Corona development even faster!
NOTE: Mac OS X native UI elements differ slightly from their iOS couterparts, so there may be minor differences in behavior here and there. Overall, you should be able to test basic functionality of your UI elements just fine.
Posted by Jonathan Beebe. Thanks for reading...