----- Original Message -----
From: "Erik Jan de Wit" <edewit(a)redhat.com>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Sent: Tuesday, March 4, 2014 10:47:12 AM
Subject: Re: [aerogear-dev] AeroGear project structure and the website
> Makes sense to me. I think the current site does confuse me a
> the same exact code (aerogear.js) then my first thought is just to combine
> similar, but different between Web and Hybrid then it may be useful to
> clearly define the differences.
It’s a bit complex to explain and on the current site it’s not clear
Cordova and the functionality that is has a different api. So a developer
that will target Cordova will probably end up using both.
is that for those parts it makes sense to use native hardware because of
security, speed or integration, in other cases it doesn’t bring enough
Because of the way Cordova plugins work it has not always been
have the same API although they are close most of the time.
Hope this helps explain things a bit more.
Thanks. This does
aerogear-dev mailing list