On Sun, Feb 5, 2012 at 12:34 AM, Luciano Resende <[email protected]>wrote:
> On Fri, Feb 3, 2012 at 9:21 PM, Avdhesh Yadav <[email protected]> > wrote: > > Hi All > > > > Can anyone explain in more details what are pros/cons of Native Android > > Client and HTML5 client. > > > > I have created a separate module for PhotArk HTML5 > > client(photark-client-android-html5). > > The older one photark-client-android(It should be renamed > > to photark-client-android-native) will host native Photark Android > client. > > > > > > In summary, you can classify mobile applications in three categories : > > Native : native to the platform, have full access to device > functionality, and you have to build one application for every > platform (android, ios, etc). > > Browser : a html application hosted somewhere, maybe with a ui theme > that resembles the phone interface. in this scenario it's one > application for all devices, but you lose the ability to access device > specific functionality. > > Hybrid : using frameworks such as PhoneGap (a.k.a Apache Cordova) you > build one html5 application and the framework can generate a native > app for each supported device. In this scenario, you can still have > access to the device functionality. > Yes I think Hybrid is the way to go. +1 > > You can find some useful information on the HTML5 track from last QCon > > http://qconsf.com/sf2011/tracks/show_track.jsp?trackOID=513 > > What I was proposing is for us to work on a hybrid application that > leverage frameworks such as PhoneGap to help minimize the work needed > to support different platforms. > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > -- Avdhesh Yadav http://www.avdheshyadav.com http://twitter.com/yadavavdhesh
