Hi

So anybody here utilising HTML5 as mobile counterparts and how are you finding it?

Where would one draw the line between choosing a native app or going with a HTML5 web app?

I'd start it off with saying:

• HTML5 is cost effective and any update applied to the website can instantaneously be applied to its mobile counterpart
• Native Apps make better use of the mobile in question as it allows full use of the phone's feature

But what if the website doesn't require the full power of a phone and relies on the internet for its content/usage? Surely a HTML5 web app is better ?

I'm asking this because there has been debate amongst my peers so I'd like to hear some thoughts of others.

Thanks

I haven't been building web apps in general so none with html5, however I am planning on using html5 from here on out to develop most sites. I've experimented with it enough to feel like I can use it in practice for most sites.

I think the choice of html5 web app vs native app comes down to the app itself and what it's meant for. The idea of whether or not it needs to interact with the phone/table hardware or software is one large consideration.

You also have to consider the market for your app and ask which they'd prefer. Personally I'm much more likely to use a native app than I am a web app. I find web apps generally don't perform as well. They seem to me to run a little slower than their native counterpart. If you're building an app for a non tech savvy crowd I'd guess native app would be the way to go since tapping an icon is easier than typing a url.

At the same time I couldn't possibly have an app for every site I'd want to visit. It would just be too many. And if you're native app is simply your web app inside a shell it's kind of pointless.

Originally Posted by vangogh

I haven't been building web apps in general so none with html5, however I am planning on using html5 from here on out to develop most sites. I've experimented with it enough to feel like I can use it in practice for most sites.

Yes, I agree. I've been reading HTML5 books and following articles for months but only started offering it as standard when it comes to web development since last month.

The differences aren't monumental (thus far) but I am finding it much cleaner to work with and the CSS3 features are a real treat - I'm cutting down on graphics where I'd normally use it (buttons or headings and typography).

I think the choice of html5 web app vs native app comes down to the app itself and what it's meant for. The idea of whether or not it needs to interact with the phone/table hardware or software is one large consideration.

You also have to consider the market for your app and ask which they'd prefer. Personally I'm much more likely to use a native app than I am a web app. I find web apps generally don't perform as well. They seem to me to run a little slower than their native counterpart. If you're building an app for a non tech savvy crowd I'd guess native app would be the way to go since tapping an icon is easier than typing a url.

At the same time I couldn't possibly have an app for every site I'd want to visit. It would just be too many. And if you're native app is simply your web app inside a shell it's kind of pointless.

So what's your take on on a website which relies solely on the internet and doesn't require any fancy features (such as phone vibration or alarm clock / camera light usage) -

In addition to this, the client works on a very tight budget but is rather ambitious (something that seems to be oxymoronic but quite abundant with clients nowadays)

Would you consider an HTML5 App in this case as it's cheaper and cost effective?

I have a third party disputing that a native app is superior for this scenario and that a 'HTML5 app is just a clone and the client is paying twice for what is essentially the same thing'

I think this person is incorrect in saying this - what would you say to the above statement?

The more interaction an app has with a web server the slower the app will be, by definition! As to paying twice for the same thing, it isn't the same thing - the situation is akin to someone paying for two different orchestrations of a song recording: same tune, different sets of musicians.

Some of it depends on how you define a web app. Technically any website is a web app, but they aren't necessarily what we think of as an app.

If a site is simply delivering content I'd build it as a web app
I'd build a native app to collect content from a variety of sites and present them in one place.

I don't think it's paying twice for the same thing either. It's two different things. I have a tv and a computer. Both let me access some of the same content, but I don't ever see it as paying twice for the same thing.

It's really up to the client which to go with. I don't think the decision should come down to the technical. There are pros and cons to both web and native apps, both in technology and more important in business.

I don't at all see an html5 web app as a clone of a native app. Each is a different way of delivering something. Your client's customers might have preferences for which delivery method they prefer.

One advantage you can mention with web apps is by default they'll be more widely available to any device with a browser, whereas a native app will only be available to the device that app is native to. Not a big deal if all your client's customers use only one phone or tablet, but that's probably not very realistic.

Main advantage of native app will be the customer acceptance to it. People more often will visit the content via their iPhone app of same website than using their website in browser. (for instance news app). The decision goes mainly on the type of content you deliver.

Originally Posted by neema19s

Main advantage of native app will be the customer acceptance to it. People more often will visit the content via their iPhone app of same website than using their website in browser. (for instance news app). The decision goes mainly on the type of content you deliver.

So are you suggesting there are more people with "iPhones" than with "computers"?

HTML5 applications is most likely the future of the Internet. Instead of relying on the local desktop applications for tasks such as calendar management, code generation, or a photo montage.