Native application or web application


Having an android device, makes sense mainly if you have Internet access all the time. So if we can suppose everyone access the net, it is obvious to think, that a mobile optimized site/web application can be used instead of a native application.

As I see the main advantage of a web based solution is platform independence, the same code can run on on any mobile phone .

I'd like to make an overview of the possibilities, and defects of a web based solution.

Possibilities:

It has been a while since is possible to create complex html and JavaScript based web applications for PC browsers. You can check out for example the YUI Library which helps building a rich user interface for such web applications.
The present smartphone browsers are capable of running these, they have enough brandwith, screen resolution, processor capacity!

If you want the web app to be present among other installed native applications you can compile a simple apk with a webview, to hardcodedly display the proper webpage. This way you can be present on the android market too.

Deflects:

The possibilities are promising, but the browser based solution has a lot of serious deflects, for example you can not:
- vibrate the phone
- use GPS
- use local database
- access accelometer
- access camera...

And there are even more device specific features, like notifications on android that can not be accessed from a browser.

Of course the application won't be usable in offline mode, and even online the browsers don't do such a delicate caching like you can implement in a native app, so it can affect speed.

Solutions:

HTML5 is one of the promising coming solution for most general problems. For example the HTML5 specification contains:
- database handling
- GPS using
- delicate cache control
- 2d and 3d graphic acceleration...

Unfortunately we have to wait a little more for this, the current browsers have not enough HTML5 support, to start to relay on them right now.

Check out your browsers HTML5 compatibility level here.

The other thing, helping the developers, are projects like PhoneGap. This project offers access from JavaScript to device specific possibilities, supporting many platforms.

Summary:

Even now, we often can see applications which somewhere solves some part of the functionality using a webview, because thats the best way. In the future, as web will continue to develop, and will be used more in smartphone development too.

Check out www.dialaphone.co.uk today and see what packages are available on the top new mobile phones.

Comments

I'm glad that you've shared

I'm glad that you've shared the pros and cons of this web application. Now, we are aware of our strategy of how set-up things easily for us.Daniel Franklin

How Can I Appy..?

Great application for me, have you tutorial to apply this one...?

Thank's
Floating Diamond Necklace

If you want the web app to be

If you want the web app to be present among other installed native applications you can compile a simple apk with a webview, to hardcodedly display the proper webpage. This way you can be present on the android market too. gay cams - Webcams.com review

I like the way you presented

I like the way you presented the problems and solutions of native or web application. Now, the topic is much clearer to me. Thanks for sharing this stuff.
Daniel Woods

Well, I personally think that

Well, I personally think that accelometer and camera access are pretty serious deflects.
AAT Qualification

nice

nice i hope everyone is really going to have internet access all time. whether free or not. yep i like web applications on phones than installed applications.

Premium Gifts

Current State

Good article.
The current state of webkit (used in Android, iPhone and soon Blackberry) has some HTML5 support.
GPS currently works.
Google demoed the accelerometer at GoogleIO and said it was coming soon.
The same for the camera.

They also demoed Chrome to Phone, which is a way to push intents to your phone. But they haven't quite ported that into the Android browser yet.

Google is certainly going in the web app direction, but we just aren't at that point yet.

I hear there is some internal debate at Google about this. Apparently, this is why Google hasn't released a Google Voice app for desktops. They want to see it as a web app instead of a native one.

NextStop (recently acquired by Facebook) is one of the few companies I've seen do a really good web app for phones. They explain it here: http://www.youtube.com/watch?v=Jks-idxVrCs

Hero better than Firefox?

On the test site mentioned in the article, Firefox 3.6 scores 139, while the browser on a 2.0 Hero scores 151! Now that's surprising...