You are viewing a plain text version of this content. The canonical link for it is here.
Posted to photark-dev@incubator.apache.org by Avdhesh Yadav <av...@avdheshyadav.com> on 2012/02/04 05:21:41 UTC
Native Photark Android Client Vs HTML 5 + PhoneGAP
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.
--
Avdhesh Yadav
http://www.avdheshyadav.com
http://twitter.com/yadavavdhesh
Re: Native Photark Android Client Vs HTML 5 + PhoneGAP
Posted by Subash Chaturanga <su...@gmail.com>.
On Sat, Feb 4, 2012 at 10:51 AM, Avdhesh Yadav <av...@avdheshyadav.com> 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.
>
Hi Avdhesh,
AFAIK, HTML5 is yet supported by some browsers on devices.
But native HTML browsers are relatively slow when we are going ahead with
the latest android app market where people expect
really polished, interactive interfaces. In such occasions HTML5 is ideal
and can done those stuff with less effort.
And one of the main advantage of native apps is the *disconnected*
functionality. HTML5 does include API's that should allow this
functionality, but AFAIK no one really supports it yet.( The user who waits
through a slow data connection to download once in our app,would not like
to so same EVERY time our app runs)
Other than that, there are many other advantages in HTML5 like powerful
audio/video support, good storage capacity and etc [1]
[1] -http://www.htmlfirm.com/blog/top-five-benefits-of-html5-arrival/
Thanks
>
>
> --
> Avdhesh Yadav
> http://www.avdheshyadav.com
> http://twitter.com/yadavavdhesh
>
--
Subash Chaturanga
Department of Computer Science & Engineering
University of Moratuwa
Sri Lanka
Blog - http://subashsdm.blogspot.com/
Twitter - http://twitter.com/subash89
Re: Native Photark Android Client Vs HTML 5 + PhoneGAP
Posted by Raymond Feng <en...@gmail.com>.
Apache Cordova is the name for PhoneGap incubating under Apache.
On Feb 22, 2012, at 10:40 AM, Subash Chaturanga wrote:
> On Sun, Feb 5, 2012 at 9:26 AM, Avdhesh Yadav <av...@avdheshyadav.com> wrote:
>
>> On Sun, Feb 5, 2012 at 12:34 AM, Luciano Resende <luckbr1975@gmail.com
>>> wrote:
>>
>>> On Fri, Feb 3, 2012 at 9:21 PM, Avdhesh Yadav <av...@avdheshyadav.com>
>>> 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
>>
>> Then shall we use Apache Cordova(seems it is pretty recently started
> incubating in Apache) or have any other concerns ?
> WDYT ?
>
>
>>>
>>> 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
>>
>
>
>
> --
> Subash Chaturanga
> Department of Computer Science & Engineering
> University of Moratuwa
> Sri Lanka
>
> Blog - http://subashsdm.blogspot.com/
> Twitter - http://twitter.com/subash89
Re: Native Photark Android Client Vs HTML 5 + PhoneGAP
Posted by Subash Chaturanga <su...@gmail.com>.
On Sun, Feb 5, 2012 at 9:26 AM, Avdhesh Yadav <av...@avdheshyadav.com> wrote:
> On Sun, Feb 5, 2012 at 12:34 AM, Luciano Resende <luckbr1975@gmail.com
> >wrote:
>
> > On Fri, Feb 3, 2012 at 9:21 PM, Avdhesh Yadav <av...@avdheshyadav.com>
> > 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
>
> Then shall we use Apache Cordova(seems it is pretty recently started
incubating in Apache) or have any other concerns ?
WDYT ?
> >
> > 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
>
--
Subash Chaturanga
Department of Computer Science & Engineering
University of Moratuwa
Sri Lanka
Blog - http://subashsdm.blogspot.com/
Twitter - http://twitter.com/subash89
Re: Native Photark Android Client Vs HTML 5 + PhoneGAP
Posted by Avdhesh Yadav <av...@avdheshyadav.com>.
On Sun, Feb 5, 2012 at 12:34 AM, Luciano Resende <lu...@gmail.com>wrote:
> On Fri, Feb 3, 2012 at 9:21 PM, Avdhesh Yadav <av...@avdheshyadav.com>
> 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
Re: Native Photark Android Client Vs HTML 5 + PhoneGAP
Posted by Luciano Resende <lu...@gmail.com>.
On Fri, Feb 3, 2012 at 9:21 PM, Avdhesh Yadav <av...@avdheshyadav.com> 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.
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/