Comparing Native Apps with HTML5:

Transcription

1 Comparing Native Apps with HTML5: What is the right approach for your organisation? Website: 1/11

2 Native and HTML5: What s the difference? HTML5 HTML5 is device-neutral, written in traditional web coding and viewed through the browser of a device. Valued above all as a one size fits all solution, it can be a cost-effective way of managing a organisation s mobile presence. However, it is known to be limited in its ability to work with the native features (such as GPS or offline functionality) of a mobile device. Native Apps Native apps are written in the language of a specific platform: ios apps in Objective-C; Android apps in Java, for example. With access to native platform resources, these are powerful apps, performing computing on the device whilst using local authority data to personalize mobile services. Native apps work with the features of the device itself, offering benefits such as robust persistent storage, location awareness, and offline working. HTML5 Benefits HTML5 offers cost-effective development and maintenance, benefits which have an undeniable appeal in today s challenging budgetary climate. Only one generic HTML5 app is needed, making savings in ongoing app management. That said, HTML5 developments have to negotiate browser incompatibilities and the varying levels of support for JavaScript and HTML5 among mobile devices. HTML5 works across all mobile platforms and browsers. Developing native apps, on the other hand, requires specialist platform-based knowledge. HTML5 can act like native apps but they live on the Web. Organisations do not have to submit apps separately to each of the proprietary app stores figures 1 show Android and ios now account for 91 per cent of smartphone sales. Native Benefits Native apps provide a rich user experience and make the most of the capabilities of specific devices. Native apps support more device features than HTML5. Native apps support push notifications, which means that users can receive information without opening the app, something that is impossible with a browser approach. The look and feel tends to be more attractive, with superior graphical effects, and is also instantly familiar to the user. Native apps offer faster performance, precisely because of their access to all the device and platform features. Native apps offer more robust security. It is easier for device owners to locate and download native apps from the store; there is no central searchable repository for HTML5. Mobile users clearly favor native apps IDC findings, February The Future of Mobile Development: HTML5 Vs. Native Apps. Business Insider, April /11

3 Mobile users prefer native apps In 2013, two significant pieces of mobile industry research highlighted a strong preference for native apps among users. Equation Research surveyed 3500 smartphone users around the world 3 about their mobile experiences. An astonishing 85 per cent of respondents preferred native apps because of speed, highquality interfaces, and platform features, that even the best of HTML5 developments cannot provide. Meanwhile, the widely-reported BiTE Interactive survey 4 revealed that 66 per cent of iphone users and 63 per cent of Android owners prioritized native apps over HTML5; they were well aware of the value of making full use of smartphone capabilities. Only 19 per cent of overall respondents were indifferent to the distinction between native and HTML5. and students prefer native too In Higher Education, Purdue University conducted a survey 5 to pin down student preferences in the native versus neutral debate. The survey was underpinned by rigorous research methodology. 85% of users prefer native apps 76% of students prefer native apps Native Apps Native Apps HTML5 HTML5 Across the board, in academic functions from reviewing and sharing course material to finding out assignment grades, the marked preference was for native apps. When accessing course timetables, for example, 76 per cent of respondents preferred native apps, compared with 15 per cent who favor the mobile browser. Students also found native apps to be both faster and easier to use compared with browser access to the equivalent information. 68% of students say apps are faster The study concluded that there was a strong preference, in almost every way, for using native mobile apps. 70% of students say apps are easier 3. Research commissioned by Compuware APM and reported in The Register, March Reported in eweek, March Business Insider, April Student Preferences for Mobile App Usage. Authored by Purdue University and published by ECAR, September /11

4 Comparing citizen experiences of Native & HTML5 We have seen that citizens indisputably prefer native apps. But besides the speed and ease of use, what are the native capabilities that citizens value the most? Lets take a look at some scenarios and the very different user experiences that HTML5 and native apps deliver: Scenario One Early in the morning a school staffmember discovers a boiler failure. The school will have to close for the day and must inform all parents immediately. HTML5 solution: In order to find out about unforeseeable school closures, parents would have to take the time to look at the specific web page proactively first thing every morning. Native App solution: The school or local authority can quickly write a notification and publish it on the school s native app. Parents will see the notification immediately on their mobile devices without even opening up the app. HTML5 offers nothing over and above the communications that existing (non-mobile) channels such as the school website or already deliver. Push notifications, which are unique to native apps, are a zero-cost and speedy communication channel. They behave just like SMS text messages, so they are clearly visible on the device screen and do not require the user to be in the app. They are popular with mobile users and can be applied to a whole range of services, from bin collections to forthcoming events, as well as emergencies such as transport disruption and flood warnings. Above: Native App solution 4/11

5 Comparing citizen experiences of Native & HTML5 Scenario Two A motorist drives into a pothole, puncturing a tyre and damaging the car. The pothole is in a hazardous location and the driver is anxious to report it as quickly as possible. HTML5 solution: In order to report the pothole on the spot, the driver would need internet connectivity at the very least. Without GPS, the driver would need to know the postcode of his location, which is unlikely. And because HTML5 rarely makes use of the device camera, the driver is left to the onerous task of typing in a full description of both the pothole and the incident. Native App solution: Because the native app remains available and fully-functioning when offline, the driver can simply open the app, select the appropriate menu option, confirm the current location on a map and then submit a photograph taken on the spot. This fast and efficient process makes good use of the in-built features of the device. The native app will send the report as soon as connectivity is re-established. In situations like this, the workflow needs to be efficient and reliable or users simply will not bother. The device is unlikely to have an internet connection, which is where the native app, with its offline capabilities, really comes into its own. The native app can also make effective use of device features for recording date, time, and location, as well as providing supporting images. Should the local authority combine this service with push notifications, the app will be able to send confirmation of receipt, and send ongoing status updates of the complaint, right up to the final resolution. Above: Native App solution 5/11

6 Comparing citizen experiences of Native & HTML5 Scenario Three A mobile user is looking for information on child benefits, but has temporarily lost her internet connection at home. HTML5 solution: With HTML5, the mobile user can access the relevant information through the browser view, but only when the device is connected to the internet. Without connectivity, the user has no way of finding the information. Native App solution: With native provision, the user only has to access the internet once to download the app. Once the app is on the device, the user can search for information held in the app without connectivity, and in a mobile- friendly view. Mobile users frequently find themselves with only intermittent connectivity or none at all. Offline access to information is particularly useful for hard-to-reach service users and other people who are on the move. Offline provision assumes critical importance for the population as a whole in emergency situations. Above: Native App solution These native features and integrations with other apps give citizens a powerful resource to work in, and in many ways make their lives easier. Native apps are firmly in the ascendant 6, and with good reason: as mobile technologies mature, today s discerning users are demanding the best. The native environment showcases the organisation to its best advantage, making full use of mobile-related technologies. 6. Apple reports that downloads from its App Store hit the 50 billion mark, May /11

7 Comparing Native Apps with HTML5 Good Ok Bad NATIVE APP HTML5 Cost High initial cost and ongoing investment. Modest initial investment. Portability Separate version required for each operating system. Easy creation of cross platform versions. Maintenance Complex to maintain and slow to roll out changes. Relatively simple to maintain with instant updates. Speed of Delivery Starts from scratch, slow to develop, and requires a lot of testing. Starts from scratch or optimized from desktop solution. Moderate time to develop; requires a lot of testing. Performance Runs locally with quick loading and fluid interaction. Internet reliance results in slower load and response. User Experience Made for mobile: smooth, fast, and intuitive to use. UI performance is slower and normally optimized from desktop, so less satisfying. Integrated Device Features Integrates with all device features and other apps. Very limited device integration. Push Notifications Cost-free notifications can be sent directly to users devices in real time. Not possible. Offline Features Best support for offline features, native data storage. Limited offline support. Future-Proof Native apps can take advantage of device innovation instantly. Slow or impossible to adopt device innovation. 7/11

8 Which road to take? When offered a stark choice between managing a single HTML5 development on the one hand, and a range of native apps all coded in different languages on the other, it is not surprising that some technologists turn to HTML5 first. Yes, native apps out-perform HTML5 in just about every area of mobile delivery, as many technologists are aware, but budgetary challenges can rule out the choice of native apps. In response to this problem, cross-platform tools promise that their customers can have it all, with a single HTML5 codeline that offers a develop once, deliver many route to a full range of native apps, generated automatically from the HTML5. The efficiencies soon fall away, however, when developers discover that they need to code a second HTML5 solution, structured in the way that the cross-platform tool specifies. And in reality, what these products generate from HTML5 is simply a native wrapper; the resulting hybrid apps turn out to deliver clunky user experiences and partial solutions in key areas such as offline working. Of all the available options for mobile development, this is probably the worst possible outcome. Is there another way? As you embark on your mobile journey, remember that there is a road that offers both IT efficiency and excellent user experience. The governmentm platform provides everything you need to deliver a range of native apps and HTML5 responsive web with ease, impressing every stakeholder, from citizen to technologist to budget holder. governmentm offers a third way, giving your organisation the best of all worlds - the flexibility and cost-effectiveness you get from HTML5, but with pre-built native apps for excellent user experience. 8/11

9 Introducing the governmentm platform governmentm is unique in bringing together pre-built native apps, an HTML5 responsive web solution, and a full set of tools for updates and extensions, all in one mobile platform, delivered as PaaS. Native apps covering over 90 per cent of smartphone sales are built into the governmentm platform. governmentm apps are native to the core, complying with the standards of all leading mobile operating systems. Tools for updating content and extending the app are integral to the governmentm platform. The App Manager is used to publish updates to mobile content instantly. For in-house customizations of screens and features, we offer a App Extension Kit (AEK), with a customer forum to share our innovative developments. Both tools operate on a change once, update many basis, right across the platform s native apps and HTML5, and onto all user devices instantly, eliminating time-consuming upgrades to the different app stores. The governmentm HTML5 responsive solution scales to any screen size, on smartphones, tablets or desktops, offering the best possible web experience on any device. 9/11

10 governmentm Platform 10/11

11 Comparison Summary Good Ok Bad GOVERNMENTM PLATFORM Cost Modest initial investment. Portability Instant creation of native apps and responsive web. Maintenance Simple to maintain with instant updates that eliminate timeconsuming app store upgrades. Speed of Delivery Quickest to deploy. Designed for local authorities - lots of pre-built modules & user features. Performance Runs locally with quick loading and fluid interaction. User Experience Made for mobile: smooth, fast, and intuitive to use Integrated Device Features Integrates with all device features and other apps. Push Notifications Cost-free notifications can be sent directly to users devices in real time. Offline Features Best support for offline features, native data storage. Future-Proof Native apps can take advantage of device innovation instantly. NATIVE APP HTML5 CROSS- PLATFORM TOOLS (CPT) Very high initial and ongoing investment Modest initial investment. Modest initial investment, however likely to need a separate HTML version for CPT. Separate version required for each operating system. Easy creation of cross platform versions. Straightforward creation of native apps, however likely to need a separate HTML version for CPT. Complex to maintain and slow to roll-out changes. Relatively simple to maintain with instant updates. Changes need to go through App Stores so slow to roll out. Starts from scratch, slow to develop and requires a lot of testing. Starts from scratch or optimized from desktop solution. Moderate time to develop; requires a lot of testing. Likely to need separate HTML version for CPT and requires a lot of testing, Runs locally with quick loading and fluid interaction. Internet reliance results in slower load and response. Internet reliance results in slower load and response. Made for mobile: smooth, fast, and intuitive to use UI performance is slower and normally optimized from desktop, so less satisfying. UI performance is slower & normally optimized from desktop, so less satisfying. Integrates with all device features and other apps. Very limited device integration. Limited device integration. Cost-free notifications can be sent directly to users devices in real time. Not possible. Depends on the crossplatform tool. Best support for offline features, native data storage. Limited offline support. Limited offline support. Native apps can take advantage of device innovation instantly. Slow or impossible to adopt device innovation. Slow or impossible (depends on CPT) to adopt device innovation. 11/11