Hi Summers,

 

Yes, this is tremendously helpful.

 

As to your remark

“I'm afraid I don't understand your question.  Are you asking why would
someone use AeroGear instead of writing code to consume those services
directly or are you asking why won't someone go to your mobile web page
and skip the native app all together? “

What I meant here is that we are in a situation wherein a web based portal communicates with a server via a web service. We would like to extend the functionality of the portal to an iOS and Android App. Most of the work done is in terms of [invoke service -> get data -> present the data] and so on. So, to accomplish this, we had started looking at invoking a SOAP service from objective-C. Then we heard about AeroGear and were wondering where AeroGear fits in.

 

Hope this clarifies what I was asking.

 

Thanks a lot.

 

Regards,

Ashish

 

 

Ashish, I will respond inline.

On Wednesday, April 17, 2013 12:46:59 PM, ashish wrote:
> Hi,
>
> We are building an application using JBoss middleware. This application has
> a web based front end. We are thinking of extending this web application's
> reach to mobile devices (iOS and Android). I came across the AeroGear
> project and have some questions.
>
> 1. What is AeroGear about? How can it help someone in my situation?
AeroGear is about providing libraries to make it easier to expose Java
EE services to remote clients AND to make those exposed services easier
to consume.

> 2. Why would someone not build a native application (using Objective-C for
> example) and invoke a web service made available via our server side
> application? Where does AeroGear fit?

I'm afraid I don't understand your question.  Are you asking why would
someone use AeroGear instead of writing code to consume those services
directly or are you asking why won't someone go to your mobile web page
and skip the native app all together?

> 3. I read about hybrid mobile app development tools so how does AeroGear
> relates to things like PhoneGap, JQueryMobile and Apache Cordova.

PhoneGap is Adobe's commercial offering of Cordova.  Cordova is an
Apache project which provides an API and a container to Javascript
applications.  This API and Container bridge the Javascript
application's WebView to the underlying OS and allow you to write
applications which use a phone's camera, accelerometer, etc.  This lets
you write native-ish apps with HTML5, CSS, and Javascript and submit
the to the various app stores.

Jquery Mobile is a library which provides mobile focused themes,
events, styles, widgets, and utilities to a Jquery based JavaScript
application.  This can be used with a website hosted on a server or in
a Cordova Application.

AeroGear in this situation serves as a communication library.  It
provides a wrapper around native storage, networking life cycle, object
marshalling, and networking error handling.  We try to have our APIs
among the various platforms be similar enough that knowledge and design
lessons learned on one platform can be applied to other native
platforms.

I hope this helps some.

Summers

---

View this message in context: RE: [aerogear-dev] What is it about
Sent from the aerogear-dev mailing list archive at Nabble.com.