In recent years smartphones have become part of many people's daily lives. They are used to communicate, stay updated, take photos, listen to music and entertain us with hundreds of thousands of apps. People carry their cellphones around with them wherever they go. They wake up with them, eat with them and go to bed with them.
For companies this presents another opportunity to market and reach out to customers. If you or your company is considering a mobile presence there are two main paths to getting there: an HTML mobile web site or a native app built specifically for one or more mobile devices.
Determining whether to create an HTML mobile web app or a native mobile app is a significant decision. A mobile web app is an app that users reach using their phone's browser. These apps are usually a combination of HTML and Javascript and function similar to web sites. A native mobile app in contrast is an app that is designed and compiled specifically for a mobile device. These apps must be installed onto the device and work only on the device it was designed for.
This article does not discuss whether you should or should not create a mobile presence. This article presents 10 reasons why you might want to consider creating a mobile app instead of or in addition to an HTML mobile site for both companies and developers.
Whether or not you decide to build a native web app depends mostly on what type of app you want to create. In most cases a native app is not needed, but if your app could benefit from several of the reasons above it might be worth considering creating a native app for your company or service.
Comment
Definitely good points.
I also agree with Brian's comment about how a bad app (or a bad release) will tank your app's support and ratings. There's also few things worse than an app that doesn't give the functionality that your users want, or offer *less* functionality than your current web application (Credit card, bank apps, etc) . This isn't a reason *not* to build a native mobile app, but the costs of developing a native mobile app and continued support can be costly (which often results in features being cut or not implemented). Sometimes having a mobile web application is a better solution for companies with lower budgets.
It comes down to knowing who your users are, and what they want. I was just discussing this with my wife the other day; she remarked that our local credit union needs a mobile app. "They're just easier to use" she said, which I agreed with. So I asked, "What mobile platform should they develop for? We're both iPhone users, but how many of our banks customers use iPhones vs Android vs other platforms? How many of those users are currently using the banks web site from their mobile browsers?" In this case, I made the argument that creating a mobile friendly version of the site might be more ideal, since it would work on any platform and would be cheaper to implement for our small credit union.
Great post Douglas. I would love to go all native, but at this point I'm more into the hybrid way Dan described. I just started playing with PhoneGap which allows me to use native functionalities (e.g., camera) and still make an app using technologies I'm more confident with (HTML5, CSS, JavaScript). With frameworks like Sencha, jQuery UI, etc. it makes web apps look more like native apps as-well. PhoneGap Apps can be also published in app store (well in it's core it's just a webkit object and javascript bridge to native api).
I completely agree that there is a performance difference. It is just the question if you need that performance boost or not. Probably good case would be games, but then again, there is Unity and other frameworks..
Maybe I should write a blog post after some more experience with phonegap:)
Good points.
For point 8, you can't (yet) use the platform's payment services to pay for goods or services. You can purchase certain things directly related to the app however such as subscriptions/virtual gold/app features, etc...
Nice post Douglas! Another option is a hybrid app, which lets you leverage web content across devices but also gives you access to native capabilities. The new LinkedIn iPad app is a hybrid (primarily HTML5).
© 2024 Created by Daniel Leuck. Powered by
You need to be a member of TechHui to add comments!
Join TechHui