The Disappearing Difference between Web and Native Applications

Does your business need a web app, native app, or both? The triplicate costs of developing and maintaining separate applications for each platform – Web, iOS, and Android – make this a high stakes question for any business invested in engaging digitally with its customers. And yet the technological landscape against which one might analyze this question is changing so rapidly that many businesses may choose the wrong product strategy based on outdated information.

 

So goal of this post clarify the difference between web and native apps as of July 2017.    

 

Case Study – Twitter

 

In February 2017, Twitter began redirecting all of its mobile web traffic from its native app to its new Progressive Web App (PWA), dubbed Twitter Lite, with the goals of increasing user engagement, achieving near-instant load times, and decreasing data consumption.

 

  • 65% increase in pages per session
  • 75% increase in Tweets sent
  • 20% decrease in bounce rate

 

<blockquote class=”twitter-tweet” data-lang=”en”><p lang=”en” dir=”ltr”>Today we moved all of Twitter&#39;s mobile web traffic (that&#39;s like, a lot) to our new web stack – Node.js, Express, React PWA.</p>&mdash; Nicolas (@necolas) <a href=”https://twitter.com/necolas/status/829128165314306048″>February 8, 2017</a></blockquote>

<script async src=”//platform.twitter.com/widgets.js” charset=”utf-8″></script>

 

Twitter Lite now uses only 3% of the local storage required by Twitter’s native app, and it requires only 600kb in bandwidth consumption for the initial load, as opposed to the 23.5MB required to download Twitter for Android. Learn more from this Google blog post.

 

To better understand how Twitter’s web app is able to achieve such significant advantages over its native app in terms of performance and data consumption, you need to understand the PRPL pattern, a web app architecture that has become possible over the past five years because of increasing browser support for the Service Worker and HTTP2, the latest version of the Hypertext Transfer Protocol. (We discuss HTTP2 at length in this article here).

 

Native app features that are now achievable on the web include:

 

 

As new browser updates roll out over the coming months, a host of new device hardware features will become accessible to web apps, further diminishing any advantage native apps may have may over PWAs. These forthcoming APIs will expose access to:

 

 

Advantages of progressive web apps over native apps:

 

Advantages of progressive web apps (PWAs) over native apps:

 

  • contacts, calendar and browser bookmarks access (lack of access to these could be viewed as a feature by privacy-conscious users)
  • alarms
  • telephony features – intercept SMSes or calls, send SMS/MMS, get the user’s phone number, read voice mail, make phone calls without the Dialer dialog
  • low-level access to some hardware features and sensors: flashlight, atmospheric pressure sensor
  • system access: task management, modifying system settings, logs

See the Pen Grab The GPS Location In Browser JS by Weft Digital (@weft_digital) on CodePen.light

See the Pen html 5 Vibrate Api by Weft Digital (@weft_digital) on CodePen.light

See the Pen Device Orientation API by Weft Digital (@weft_digital) on CodePen.light

See the Pen JS Battery Status API by Weft Digital (@weft_digital) on CodePen.light

See the Pen Compass in HTML5 Demo by Weft Digital (@weft_digital) on CodePen.light

How HTTP2 Changes the Game for Web Performance Optimization

By late 2015 almost all major browsers began supporting HTTP2, the latest version of the Hypertext Transfer Protocol, which has served as the foundation of the Web since it was first created by Tim Berners-Lee at CERN in 1989.
“A test of blockquote here we go” – Tim Berners Lee
The update to this fundamental protocol opens up an exciting new chapter in the history of the Web and drastically changes how web developers ought to approach the performance optimization of their applications and web sites. However, less than 15% of sites on the

Web are currently taking advantage of HTTP2 technology, despite the widespread browser support. https://w3techs.com/technologies/details/ce-http2/all/all

http://caniuse.com/#search=http2

In the old days of HTTP1, one of the most common causes of slow page speed times, was an excessive number HTTP Requests. Developers would seek to minimize network latency and the total number of requests needed to render a website by combining assets like scripts and stylesheets into as few files as possible. While this strategy proved effective for improving loading speeds over HTTP1 connections, it also created some headaches for developers. The monolithic file structure required for optimal loading times over HTTP1 is the exact opposite of the modular file structure which is ideal for fast and efficient development.

To solve this problem, developers began to rely on build tools like Grunt and Gulp to prepare their assets for optimal delivery. These tools allow developers to maintain a modular, well-organized codebase of human readable files, which can then easily be concatenated, minified, and obfuscated for production by an automated build process.

While build process tools still have their place in the web developer’s toolkit, the performance optimization benefits these tools provide have rapidly become obsolete because of technological improvements to browsers, web servers, and to the protocol that allows the two to “speak the same language”, HTTP.

HealSuite CTMS

Intuitive CRF Designer

  • Effortlessly build out your study data model, database, and case report forms through a simple yet powerful WYSWIG interface.
  • Hundreds of standards compliant CRFs and form templates available in forms library, so you don’t have to reinvent the wheel.
  • Design, approval, and version control processes built in.
  • Conditional logic, input validation, file uploads, live audio/video capture, speech-to-text recognition, and basic web design capabilities

GroupDiscover abstracts away medical coding required for data compliance for a faster data capture workflow


Auto Medical Coding

  • Effortlessly match your preferred terminology to industry standard medical and health vocabularies.
  • Data collection points mapped across multiple vocabularies and data models published by the FDA, NCI, NLM, ClinicalTrials.gov, and CDASH.
  • Enables CDASH and SDTM compliance now required for FDA approved New Drug studies and automated regulatory submissions to the FDA.
  • Enables interoperability and easy integrations with other medical and bioanalytics software.

Realtime Analytics

  • Sophisticated outcome analysis and data visualization tools
  • Automatically identify linear regressions across outcome data sets
  • Scalable cloud infrastructure enables complex data search, aggregations, and analyses in near real-time