[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Aerogear-dev] AeroGear tagline, mission

Any more comments or thoughts on this before I make some updates?

On May 29, 2012, at 5:49 PM, Jay Balunas wrote:

An updated version:

"AeroGear facilitates the development of mobile applications of all kinds (mobile web, native, and hybrid) with JBoss & JavaEE via examples, tutorials, client libraries, RAD [Forge] extensions, and enhanced testing techniques with Arquilian.  This includes the latest application development methodologies including one we call Plain Old HTML5 (POH5) which uses a pure HTML5-based clients interacting with RESTful endpoints and services.  Combining maven archetypes, wizards within JBoss Developer Studio, quickstarts, and guides AeroGear makes it easy to access the benefits, and power JBoss has to offer, while fully embracing the polyglot nature to modern mobile applications."

On May 29, 2012, at 5:45 PM, Bruno Oliveira wrote:

My 2 cents... 

On Tue, May 29, 2012 at 9:54 AM, Jay Balunas <jbalunas redhat com> wrote:

Some points that could be clearer:

* Some of these client libraries are not mobile only

Indeed, but they have something in common, they're hybrid applications. Currently we have some projects like: kitchensink-cordova (Objective-C  + html5 + js), kitchensink-html5-mobile (java  + html5 + js), kitchensink-torquebox-mobile (ruby + html5 + js). 

Maybe to be easier to newcomers, I would like to have JS + html5 stuff as a separated project, so we can bring up POH5 to java, ruby, clojure applications...My concern is that people should be allowed to use POH5 (client side library) without care about the server side programming language. 

In our latest examples we had some success with hybrid applications on Ruby, Java and Objective-C. Why not extract what those libraries have in common to be used by the server side applications? 

In those cases we really had different backends, but all using the POH5 client paradigms.  I'll try to draw a little diagram to so this - might help with our understanding.

* Imo, AeroGear main deliverable is the client libraries, and any server-side integration that they require - agree?

+1 we need client libraries that are easy to use + server side integration as a bridge. 

aerogear-dev mailing list
aerogear-dev redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]