uk-netmarketing Archive (2011-2015)

Hey Miko,



Hope all well with you!



This really this depends on whether you are actually building a software
application,  or mobile sites.



If you were creating a software application, predominantly operating as an
on-board tool and utilising lots of system and device resources then a
native app may be the only path,  although you might use web UX technology
to manage interfaces in a consistent way.



If I were creating mobile sites,  that might utilise some of the standard
mobile device tools (GPS, accelerometer) via a thin client wrapper, but
predominantly looking at web experience using HTML5 (offline cache, for
offline browsing & no roaming charge  etc.) then your support of
development across multiple devices and on-going support will be less,
assuming you follow design patterns and standard web browser technology
across devices.



When we last scoped that for a travel client,  offline content, GPS, etc.
the hybrid approach made a lot more financial sense given the limited
device resource requirements, and the size of the potential user market
opened up in a low cost way.



You can always build up more native application code on a device by device
basis as required,  if you choose the right hybrid approach.



If you want your apps in the stores you’ll need an application wrapper (at
least) anyway.



I’d recommend web standards based approach if this is predominantly a web
project.



Have a look at the LinkedIn strategy.   They take a web standards based
approach to ‘app’ development,  but use very different device specific
design patterns – which is probably your best case scenario.



angus



--

Angus Phillipson

Byte9 <http://www.thebyte9.com/>



angus at thebyte9.com

+44 (0) 771 043 8972

+44 (0) 0208 780 6350



*From:* uk-netmarketing-bounces at mm.chinwag.com [
mailto:uk-netmarketing-bounces at mm.chinwag.com<uk-netmarketing-bounces at mm.chinwag.com>]
*On Behalf Of *Miko Coffey
*Sent:* 06 March 2013 16:31
*To:* uk-netmarketing
*Subject:* [uk-netmarketing] To app or not to app, that is the question



Hi lovely digital marketers,



I have a question for your brains... I am getting mixed messages from my
various trusted sources on this, so I thought I'd ask you guys for your
tuppence, too.  Let's assume you're a medium-size company, and you already
have a mobile optimised website, whose primary function is eCommerce within
the travel industry. Do you need a set of apps, or not?



On one side of the fence, we have the "Don't Bothers" who say that apps are
a waste of time & money in the longer term, as their crystal balls say that
consumers will rely more & more on browser-based interaction on their
mobiles as HTML5 beds in. With the increasing diversity of mobile OSes, the
cost of building and maintaining apps for all platforms would be better
spent on marketing your mobile (and desktop) site.



On the other side of the fence, we have the "App Lovers" who point out the
fact that good apps can perform functions not possible within the browser,
and as you're in the travel industry, those roaming charges can be a real
killer. Focus your app development on utility and/or fun, and give your
customers something so useful or entertaining that your apps become agents
for brand awareness, reputation-building and act as a differentiating
factor between you and your competition. Besides, the app market is not
going anywhere but up.



Which side of the fence are you on? Because I'm still sitting and not quite
sure where to plant my feet ;-)



Thanks all!

Miko



-- 
---------------------------------------
Miko Coffey, BFA FRSA

Independent Web Consultant
http://www.usingmyhead.com
email: miko at usingmyhead.com

Freelance Photographer
http://www.mikocoffey.com/photography
email: mail at mikocoffey.com

phone: +44 (0)20 8678 0860
mobile: +44 (0)794 100 5431
skype: miko.coffey
twitter: mikosoft
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.chinwag.com/cgi-bin/mailman/private/uk-netmarketing/attachments/20130307/869bfd39/attachment.html>