Tue, Dec 6, 2011
Single website browsers to users can initially look like dedicated mobile apps. However, it will quickly become clear that their influence is quite limited. On the contrary, native
mobile apps with wrappers are better off in many ways. They can bridge the worlds of surrounding app and the web and offer the potential for some integration. However, native apps do much less to integrate in the environment chosen by the users.
Mobile apps feel special, tailored and designed. They are targeted, crated and on the go, providing better value for the users.
Weighing the relative merits
While deciding between web and native mobile apps, every project must weigh the merits of each. However, the fact remains is that when the app is deployed on the internet, you may be starting off with a major disadvantage. The cognitive load that is associated with your app is that it is more of a bookmark rather than an experience. There will also be an implicit trivialization occurring in the mind of the user.
Providing users an experience
Users today do not buy anything based on how new the technology is or how fast the updates are provided. People are looking for an experience that will be tailored especially for them and they want to have an enjoyable experience. They want something that is designed, dedicated, special and specific to work with what they currently have without any aggravation or effort. They simply want something that can be subscribed to with a single click without any effort.
While all of that can be done on the internet and can be done well, if your goal is to make mobile apps that can delight the users, the technology part that gives just as it takes away. Beginning with a compromise is not probably the right way to start.
