As it stands, I don’t know a great deal of Objective-C, so grabbing some company’s SDK may be a stretch for me, even if I had Corona Enterprise. But, if someone were to take the SDK and create simple Corona API functions to call it, I could easily handle that. That’s where Gluon comes in.
The way we’ve seen new commands and functions pop in to our API documentation, whether it be gameNetwork.* for Game Center and Corona Cloud, lfs.* for the robust Lua File System, we’ll likely see for other Gluon plug-ins as well.
This relieves the burden of having Corona Labs maintaining so many additional, different, and complex frameworks, and the ongoing, evolving changes (sometimes breaking) within those frameworks. We’ve seen OpenFeint come and go, as well as other services to which Corona had support for, made documentation for, but soon after had to be deprecated and removed. If Enterprise developers find that a plugin for things like Apoxee, face recognition, QR scanning, augmented reality, Anticrack, Bluetooth HID devices, etc. could benefit Corona SDK users, they could create and sell or provide the plug-in and make easy APIs for us to access it.
I would much rather have Corona Labs make sure they focusing on continuing to build the fastest and easiest engine to create games and apps for, rather than having to fix so many different provided frameworks that could really be handed off to developers who are either passionate about those particular frameworks, or who have close ties with the developers of those frameworks, or even the framework developers themselves.
Looking forward to Gluon, thanks for the update, David!