Mobile Strategy – HTML5 vs Native applications

I wanted to write about this for a very long time, never had a chance.

In most of the businesses, it has become a ‘necessity’ to think about ‘mobile strategy’.  There is so much being written about HTML5 and how it is going to make your mobile service delivery easy etc. The fact that you develop ‘once’ and support on all the major mobile devices is a very tempting option. But, this is where you have to make tough choices. We did a prototype using HTML5 and started using the application. It did not take us long to realize that UX (user experience) was very poor. It was nowhere close to the UX you get from the native applications.

We had to make a call; it was not an easy decision to make (or is it?). If you go with native applications, your cost and time will increase tremendously (separate development tools, resources, code base, testing, deployment etc.).  In this competitive world, if you do not provide the best, customer will go somewhere else. In spite of cost and time issues, we decided to go with native applications. Today, we are glad that we took that path.

At Palisha, we do have a ‘Mobile Solutions Practice’. If you need to talk or have any questions, please send an email to

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: