inneractive Ads

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.

Storyboard API

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.

  1. Austin Patten says:

    Hmm, going to wait on this. Can’t simulate on iPhone 4 if not a pro-subscriber :(. Looks like I will be subscribing earlier than previously though :D

  2. How does the developer get paid from Inneractive? PayPal? Bank Transfer? Just signed up, and can’t find anywhere to enter financial info.

  3. I was going to wait til next year to upgrade! But that carrot is nice and juicy now! How do developers get paid from android, nook, and amazon?

  4. I suspect that secret feature is the new Ad company. Though I know many of us were looking for something that hadn’t been discovered and mentioned in the forums already.

  5. @Ingemar, they use Paypal and send it to the email address you signed up with. I wish I had known about that up front because may paypal account isn’t the same email address that I use for my iPhone related stuff.

    Gotta figure out how to change that.

  6. How can you strip a feature (iPhone 4 testing) which paid users previously had acces to? That’s like finding out the magic wand tool is missing from photoshop after updating.

  7. @Rob: Thanks for the info…
    I have the same problem. I’ll fire off an email to Inneractive and ask them to change it.
    Honestly, I’m not too impressed with their dashboard though. It seems like it’s put together in haste, and the categories are anything but logical.
    I’m hoping that Mobclix can be the next contender for inclusion in the Corona Ad API.

  8. @Ingemar Trust me, Mobclix isn’t the best….I’ve been using them for a couple years now, and their ad optimization and mediation has gone down in revenue and quality over the last little while.

  9. Jonathan Beebe says:

    To clarify, the iPhone4 simulator skin has been removed for trial and Indie/Android developers. Indie/iOS and Pro users have access to the iPhone4 simulator skin.

    However, Trial and Indie/Android users can *still* build for iPhone4 and test on the actual device just as before (or even Xcode simulator), the difference is just the simulator skin in Corona.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>