It's been a little while since I wrote about AeroGear (and we're still hiring by the way!) so I wanted to take a minute and give a bit of an update and preview some things we are working on.
For those of you that did not get a chance to make it to JBoss World it was a great conference for mobile, and AeroGear was everywhere! It all started at the opening keynote demo showcasing jBPM, mobile, and other JBoss technology. The AeroGear team worked with the rest of the demo team to create a JBoss toy store application, both in mobile web and native versions using Apache Cordova. We also deployed the application using AppBlade, a partner of ours that allows for enterprise provisioning of native mobile applications. You can check out this video by Burr Sutter for a technical run through of the various parts. You can also download the source, and try it all out for yourself here.
There were several other sessions, BOF's and labs related to mobile development and AeroGear. In one of the AeroGear sessions I discussed where the project is, and what our upcoming plans are. I wanted to share these more broadly, and from that this blog was born!
One of the first things I mentioned is that the AeroGear project site needed a revamp! It was authored using a content management system (CMS), and as such could not really showcase some of the advanced functionality that we wanted to use. We also wanted to update our roadmap and wiki pages with the items below, and have them be easier to maintain.
So we're moving our project site to use Awestruct, a great tool for developing project sites that look great and let you have more control. In this we are following the footsteps of TorqueBox, Immutant, Arquillian, and JBoss Developer Framework. This means our site will be developed on github, and hosted on JBoss.org just as before, only better :-)
For our docs and wiki we're going to be moving to AsciiDoc, which is a lot like markdown, but even more powerful and supported by github! This is another great option for open source projects that want their documents to be functional, beautiful and pull request-able.
We'll be getting these updates in place as soon as possible, hopefully in the next week or two!
As I mention in the current
In my presentation I talked about what these libraries would address:
- Persistence (secure content access via REST & Websockets, including bean validation and more)
- Security (authentication, authorization, content encryption, and IDM)
- Messaging & Connectivity (Integrated CDI eventing, JMS, native/non-native push, Websockets)
- Data Sync & Offline support (Auto sync of various content across clients/servers, collision handling, and local cache)
Providing a server-side foundation for some of this functionality is also a new, early stage light-weight MVC that QMX developed called AeroGear Controller. While our client libraries will not depend on this entirely, some of the advanced functionality may require it, a lot of that is still TBD. To join in, check out QMX's blog aerogear controller 1.0.0.Alpha is out!
So keep your eyes open for more from us in the near future, and jump into our IRC channel (#aerogear @ irc.freenode.net), forums, or mailing lists if you are interested in lending a hand or seeing whats going on!