Apps vs Mobile Web

0 views
Skip to first unread message

Hugh

unread,
Aug 23, 2010, 10:39:25 AM8/23/10
to Antiquist
Really interesting article for anyone considering developing an app.

http://www.mobileactive.org/mobile-web-not-apps

Hugh

Chris Puttick

unread,
Aug 23, 2010, 11:11:45 AM8/23/10
to anti...@googlegroups.com
Well expressed arguments. I'd suggest right now if you need to do
something, rather than provide something, an app is the way forward as
it is easier for the whole "connectivity is not guaranteed" thing; but
as mobile browsers mature the offline capabilities of web-apps should
improve.

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

Mia

unread,
Aug 23, 2010, 6:22:21 PM8/23/10
to anti...@googlegroups.com
Between Wired's 'the web is dead' and A List Apart's 'mobile app vs web', it's obviously an interesting issue right now.  The MCG list got going after a post on 'Historical Maps IPhone App' (https://www.jiscmail.ac.uk/cgi-bin/webadmin?A1=ind1008&L=MCG#11).

With cuts looming, my gut instinct is to build re-usable services that can pipe out web or app content as needed for the immediate use case and in the future.

cheers, Mia
--------------------------------------------
http://openobjects.org.uk/
http://twitter.com/mia_out

Sean Gillies

unread,
Aug 23, 2010, 6:39:38 PM8/23/10
to anti...@googlegroups.com
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. Mike Ellis points this out
in the JISC thread.

--
Sean Gillies
Programmer
Institute for the Study of the Ancient World
New York University

Mia

unread,
Aug 23, 2010, 7:00:14 PM8/23/10
to anti...@googlegroups.com
On 23 August 2010 23:39, Sean Gillies <sean.g...@gmail.com> wrote:
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.

I thought that was the point I was making!  

One caveat - I've found that you often need variations on shared content, interactions and IA for (in my case) gallery interactives, so possibly for mobile apps too compared to websites, because the design affordances and context of use can be so different.  How great the differences are would depend on the content and the users.

cheers, Mia
Reply all
Reply to author
Forward
0 new messages