Posted on by

CoronaCards logoOver the last few years, it’s been great to see the Corona developer community grow worldwide. There are Corona developers literally everywhere! Of course, there are many others that are developing completely natively or using other tools. We know many of them would benefit from the power and ease-of-use of Corona, if only they could use it within their existing environments.

Well, that’s what CoronaCards is for! Think of CoronaCards as an “embeddable” or “overlay” version of the Corona platform. You can include it in any native app, in any configuration (full screen, partial screen, transparent overlay) and have it run rich, interactive Corona content. It can use almost all of our 1000+ APIs, from shader-based image filters, to physics, animation, audio and much more. It’s “Corona Everywhere”!

So what are some concrete uses of CoronaCards? Here are just a few:

  • Developers using frameworks like Appcelerator or PhoneGap, with limited ability to add rich content, can use CoronaCards in their app to easily layer on cool interactive features.
  • Developers (using any tool) that want to add a relatively complex feature like image filters (think of Instagram) can use CoronaCards and take advantage of our super-simple APIs to do this in just a few lines of code.
  • Developers using a tool like Unity could use CoronaCards to quickly add and iterate on simple 2/2.5D aspects of their game UI.

In addition, we are working on some extremely cool applications of CoronaCards that we can’t say too much about yet. But here is a quick taste: imagine mobile advertising that can do everything Corona can do! Yes, it would blow away anything else in the market. The engagement and conversion rates are off the charts, and the data/analytics you can get are also very unique. We’re working on this with some partners and will have more to say soon!

One important thing to mention is that CoronaCards is built on the exact same foundation as Corona SDK and Corona Enterprise. So new features will make it into all our products and benefit all our developers. And CoronaCards takes full advantage of the maturity of a platform that is already powering well over 30,000 apps worldwide.

Finally, CoronaCards is available now for iOS and Android, and will be available for Windows Phone 8 soon. It can also be used within tools like Appcelerator, PhoneGap, Unity and Xamarin. We are currently in a closed beta – please check out the CoronaCards page and apply to get access!

If you have any “non-traditional” but cool ideas about how to use CoronaCards, please contact us: coronacards@coronalabs.com.


Posted by . Thanks for reading...

33 Responses to “Introducing CoronaCards!!!”

  1. David Grant

    After struggling trying to figure out corona enterprise plugins this is music to my ears. Hopefully the documentation is better then corona enterprise is though. Yeah and the links aren’t working.

    Reply
  2. Chris

    This is quite interesting! Especially being able to make interactive elements…
    But most importantly, this lets us leverage our existing Corona skillset but explore other solutions that provide better access to device features and functionality (like barcode scanning or speech recognition).

    Reply
  3. Mike

    So is CoronaCards going to be part of the Corona SDK or is a separate product? Also if it is not part of Corona SDK will it be able to be used with the Corona SDK just like with the other SDKs mentioned?

    Reply
  4. Damir

    Interesting, guess there will be many nice usage of it.

    Can we now get the Admob banner height API ? :)

    Reply
  5. Raphael Salgado

    Well, this is certainly a welcomed game changer. So, for developers who didn’t want to work solely within Corona SDK and didn’t want to go with the Enterprise edition to create, design and embed their own native plug-ins, you’re bringing the power of Corona SDK to them in the form of a plug-in to their own platform? Ingenious.

    Will this change the need for Enterprise in any way? We could see users saying, ‘we don’t have to use Enterprise when we can build in X and just use CoronaCards for the good stuff.’

    Reply
  6. sunmils

    This are great news. Will it also be possible to call lua functions from native code? Or does it work independent?

    Reply
  7. Jeff Leigh

    FYI, David,

    All the “How it works” and “See what you can do” type links on coronacards.com pages take me to a blank/black popup with no content.

    Reply
    • David

      Jeff – those should show videos and work on all browsers we’ve tested. Can you let me know what OS and browser you are using?

      Reply
  8. Mike

    You are showing native objects with things over the top of them…so does this mean we will now be able to do the same with Corona SDK?

    Reply
  9. Alex

    All the way brilliant 10/10. Think of what can be accomplished!

    1. Create a shell iOS/Android app in Xcode or Eclipse
    2. Layer CoronaCard “plug-in” on the top
    3. Bake for 35 minutes, leave to cool on your windowsill
    4. $$$ profit $$$
    5. YACHTS

    I don’t see any other conclusion…

    Reply
  10. Ervin

    Very happy to be proven wrong!
    Is this is actually real, it’s tremendously exciting!

    Reply
  11. J. A. Whye

    Wait a minute — since Unity can target desktop and web, does that mean CoronaCards can be used in Unity games that target those platforms?

    Reply
  12. JCH_APPLE

    It’s certainly very interesting but why do you “spend” internal man power while the main SDK lacks many important features? To me, it would be nicer to focus on people that uses Corona for main development.

    Reply
  13. Gary Crook

    I’d be very interested to know how it integrates with Appcelerator, couldn’t find anything specific in the docs. Maybe it’s created as a module?

    Reply
  14. Doug

    So I can now just build my iOS apps in Xcode with embedded Corona (assuming the performance is the same)? I wonder how Xcode will handle Lua editing (and I wonder if this is why the Sublime Plugin isn’t as important anymore)?

    Reply

Leave a Reply

  • (Will Not Be Published)