Since they are designed for a specific operating system, they “feel right” and behave the way the user expects. They are glassy smooth, fast and super reliable. Native apps are those developed specifically for a smartphone operating system, such as iOS and Android. What’s more, consolidation among these tool vendors will result in many businesses locked into a technology vendor that may not be around in a couple years.Īn app that is designed to simplify workflows should be built as a native app today. To illustrate, I recently met with the CIO of a large financial institution that is in the process of moving away from these tools because they delivered a substandard user experience. The only problem is that most apps created using PhoneGap simply can’t provide the complete user experience that native apps can achieve and that users expect. Executives really should be asking: what is the app expected to do?Ĭompanies that are developing workflow apps to help employees do their jobs better, what we call business-to-employee apps, should not make the mistake of only considering HTML5 because “that’s where the future is headed.” HTML5 simply isn’t ready yet for prime time.įor example, look at PhoneGap, a popular cross platform development framework that facilitates quick and cheap hybrid app development. Whether apps should be native (built specifically for iOS or Android based smartphones) or HTML5 is the wrong question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |