OTOH making an Android app is maybe easier than making an HTML5
web-app, and Android phones are more common than mobile phones with
HTML5 web browsers...
Chris
> --
> You received this message because you are subscribed to the Google Groups "Antiquist" group.
> To post to this group, send email to anti...@googlegroups.com.
> To unsubscribe from this group, send email to antiquist+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/antiquist?hl=en.
>
>
--
My employers website: http://thehumanjourney.net - opinions in this
email are however very much my own and may not reflect that of my
current employer, past employers, associates, friends, family, pets etc..
Documents attached to this email may be in ISO 26300 format:
http://iso26300.info
--
Sean Gillies
Programmer
Institute for the Study of the Ancient World
New York University
Right, reusable is the key, but I think there should be shared rather
than distinct app or web content. I don't see why a mobile app can't
use HTTP to access the same web JSON/XML/KML services that a browser app would access with XHR and javascript.