Monthly Archives: November 2011

MOBILE STRATEGY: XAML vs HTML5

As we all know, Microsoft was left behind in the Mobile Smart Phone market. Recently Microsoft developed a very powerful OS for smart phones. It is called Mango (Windows Phone 7.5). Nokia and Microsoft signed agreements to promote this for Nokia’s next generation smart phones. Samsung and other manufacturers have already released few phones with this OS.

At Palisha, we are developing some applications for this platform also. I just wanted to write about a practical scenario where you will have to choose between native windows phone application vs HTML5 application.

HTML 5 clients, no matter how impressive their interactivity and the emulation of native application interfaces they present may be, are still second-class clients. But they still lag.  They still feel like they’re emulating something.

If you’re building line-of-business applications, you need a first-class client and you need productivity.  A second-class client will erode user satisfaction, which is never good.  Worse yet, this erosion will be inconspicuous, rather than easily identified and diagnosed, because the inferiority of an HTML 5 client over a native one is hard to identify and, notably, doing so at this juncture in the industry is unpopular.

XAML combined with Visual Studio provides an unprecedented power to the mobile developers.It does not matter what is your LOB (Line of business) XAML/Silverlight has lot to offer to quickly develop stunning applications. In addition, Mango has a very good support for WCF stack (compared to iOS). For many applications, this is a huge help.

I only wish Microsoft came up with something like this two or three years ago. I still believe that, number of cool applications developed for Mango platform will very soon become a credible threat for Apple’s App store.

The following picture shows our windows phone application. This was developed using silverlight.

Mobile Strategy: Hybrid Approach

It is possible to combine HTML5 and Native application in your mobile solutions. You can make use  of HTML5, jQuery Mobile and other technologies to build part of your application which could be used as-is in all the mobile platforms.

The following picture shows how we used hybrid approach in our application.

 

If you have any questions or comments, feel free to email me at shanthu@palisha.com

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 shanthu@palisha.com