As an update to my previous post, Adventures with Corona, Part 1: What Corona offers that’s better than Adobe AIR, I thought I’d take note of some new features in a recent release of Ansca’s Corona SDK. In particular, Corona developers now have access to more useful services. Services that we simply cannot use in AIR today, for various reasons.
Game Network
Last time, I noted that OpenFeint support in Corona could only be used with iOS. Thankfully, OpenFeint works on Android now too. Moreover, Corona developers have been given a choice between OpenFeint and PapayaMobile. Leaderboards and achievements for all. More and more, I’m finding that I’d rather integrate a service that focuses exclusively on this sort of thing because the experience can be far better than a home-grown solution (at least for an indie developer, like me).
Advertising
Ansca has also partnered with InMobi to bring advertising to Corona apps. Whether it’s to monetize a lite version or to go completely free and try to mimic the typical route of free web games, ads are extremely important. I’ve been waiting for quite a while now for the ability to try releasing a free game with ads. Since I’d rather not go fully native, I needed a supported library from an ad network (which apparently isn’t a priority), or ad support in my platform (thanks, Corona!).
Hold on there, AIR
Day by day, I realize that while AIR is getting some cool features that can wow the senses (like Stage3D), Adobe is forgetting, ignoring, or not prioritizing features that keep a roof over a developer’s head. Some things players expect or demand in games, like popular social networks for leaderboards and achievements. Others help us earn just a little more money, like advertising and in-app purchases (both of which can be useful outside of games too). I immediately felt limited without these essentials back when AIR on mobile was first introduced, and it’s been frustrating to see little support from Adobe or third-parties after so long. Maybe that’ll change with native extensions, but those are still a bit further away in the future.
Yep, definitely a shortcoming for AIR. And I would be surprised to see Adobe fill in this gap – although I hope I’m wrong.
Maybe, just maybe, there will be some Actionscript open source projects that fill in these gaps.
Right. I’d say Adobe definitely won’t be filling in these gaps on the runtime side. I hope they’ll consider starting with a nice collection of free example native extensions, though, and that they’ll strongly encourage the community (possibly with some incentives) to build more. Ideally, I’d like to see a thriving open source community or some sort of marketplace where I could drop a little cash to get something I don’t want to build myself.
ActionScript libraries are, of course, preferred. However, with AIR being a small fry in mobile, native extensions are what this community needs for services like those I mention above. I highly doubt the companies that create the services see any value in AIR currently, so we’ll be holding our breath forever if we don’t do something ourselves.
Adobe has committed to when native extensions will come out, but it looks like it will be with AIR version 3.0. We will have to wait until the final mobile version of the runtime and SDK are available.
Certainly that will be huge in filling all sorts of gaps in AIR and having some sort of library or marketplace where you can get these kind of extensions would be great.
Pingback: Nurturing and maintaining a relationship with a big corporation while choosing the best paths for your own needs and interests « Josh Talks Flash