2 ms·
Assuming your audience/customers use smartphones I would only have 2 buckets (otherwise just a): a) Desktop browsers b) Smartphone browsers I don't bother su
by dmix 17y ago
Assuming your audience/customers use smartphones I would only have 2 buckets (otherwise just a):
a) Desktop browsers
b) Smartphone browsers
I don't bother supporting feature phones because if its anything more then a small piece of data like the weather then browsing the internet on feature phones (and some early Blackberries) is pointless.
The web based vs native app question depends on a few things:
a) Do you need to use built in smartphone features (camera, GPS etc)
b) Have enough money to invest in developing for multiple platforms? (or you could use Rhomobile for rails)
c) Need a device-specific UI in order to deliver the content in a useful way?
d) App needs to work outside of 3g/CDMA networks? (business critical?)
I believe that web based is the way to go for most cases and will continue to be a better option over the next few years as more smartphone browsers are on level with iPhone/Android. But if the answer to the questions above are yes then native is the best bet.
- redsymbol 17y agoRe ignoring feature phones: Good point. Making a distinction between feature phones and smartphones gives us the choice to not support the former. At least in the USA, it's probably rarely worth the effort. (Don't know about other markets.) Native is sometimes the way to go, for the reasons you mention. It's also AT LEAST an order of magnitude more expensive - especially for several platforms... It's good to see things like geo-location.js [0] taking shape. cheers, thanks for the comments Aaron [0] http://code.google.com/p/geo-location-javascript/ http://code.google.com/p/geo-location-javascript/