What are Progressive Web Apps (PWAs)?

Even if every app feels similar to the inexperienced user, there are a few fundamentally different approaches to creating an app. An overview of the four more established variants:

Native apps are “classic” apps, so to speak. They are developed specifically for an operating system (iOS or Android) and therefore run optimally on every device in terms of performance and handling. In addition, there are no restrictions on the use of device functions such as the camera, GPS or motion sensors. However, the main disadvantage of native apps is that a separate app has to be developed for each operating system, which of course makes the whole thing a little more expensive.

A hybrid app is a web app that is packaged in a platform-specific “wrapper”. It has the advantage that it only needs to be programmed once, regardless of the platform, and can then be distributed via the app or Play Store. This also enables access to the extended device functions, similar to a native app. Users have to make compromises when it comes to the user interface, which consists of HTML elements and therefore has to do without the familiar device-specific navigation environment.

Similar to a hybrid app, the cross-platform app also manages with just one code base for different operating systems and allows access to the extended device functions. However, as they can access the native device components, they also feel like native apps in terms of handling.

Put simply, classic web apps are a slightly more interactive form of normal websites. Web apps are called up like websites in the browser and therefore function independently of the platform. This makes them relatively efficient to develop, but has the disadvantage that their range of functions is very limited.

And then there is the newest member of the “app family”: Progressive Web Apps. PWAs are a good example of what happens when technological possibilities evolve. Put simply, they are classic web apps, enhanced with a few important features that would actually be reserved for “normal” apps. This has been made possible by functional enhancements to mobile browsers in the last year or two.

But what features actually characterize a PWA?

1. A progressive web app is basically a web app. It is therefore called up in the browser like a classic website.
2. PWAs can be added to the home screen just like apps downloaded from the store.
3. They have certain app functionalities such as the option to receive push notifications, make data usable offline and store the app on the home screen.
4. Launched from the home screen, a PWA feels more like an app than a website, as no browser navigation is displayed.
5. PWAs are also closer to apps than websites in terms of user experience, although they are based on HTML – comparable to hybrid apps.

The use of a PWA naturally has a number of advantages over established technologies. Summarized in one sentence: Progressive Web Apps have all the advantages of websites, coupled with some of the advantages of “regular” apps:

1. The difficult task of convincing users to download an app is no longer necessary
2. As the content is accessed in the browser, only one programming language is required across all platforms
3. A PWA is less complex and therefore cheaper to produce than a native app
4. Content caching reduces data consumption for the user and enables offline use. It also speeds up the use of the app compared to a website.
5. For users who use the add-to-homescreen option, customer loyalty is comparable to classic apps.

Of course, not all that glitters is gold. And unfortunately, not everything new is automatically better. This also applies to progressive web apps. The use of web technologies means that the majority of app functionalities are no longer required:

1. No access to device sensors. This is a problem for augmented reality applications in particular.
2. The range of functions is still browser-dependent. On iOS, for example, PWAs cannot yet be added to the home screen in Google Chrome.
3. No TouchID, FaceID or Siri.
4. Battery consumption is higher with PWAs than with native apps.
5. It has proven to be very difficult to get customers to use the Add-To-Homescreen function

Of course, every technology has its advantages and disadvantages. The specific requirements of a project make the choice of a particular approach sensible – or not. However, PWAs are a good way of responding even more precisely to customer requirements and finding an optimal solution in terms of scope and functionality. However, they are not the solution to all problems but should be seen as one of many tools.

We also like to use PWAs where it makes sense. The most recent example of this is the LIstory app implemented for Liechtenstein Marketing. At the same time, this project also shows where the limits of the technology lie:

The LIstory app guides interested visitors to Liechtenstein along the Liechtenstein Trail, a hiking trail comprising 147 experience stations. These stations consist of text information, images, videos and audio files on the history of the country. Content that we were able to implement wonderfully with a PWA.

In addition to this, however, we also created ten augmented reality experiences, which was beyond the scope of what was technically possible within a PWA. So we decided to create the AR content in Unity and display the content PWA within this framework. A mixture of cross-platform app and progressive web app.

Which brings us to the last point: Categorizing things is all well and good. However, if circumstances require it, there are countless nuances and mixed solutions. For this reason, we always try to understand the project goals first and then decide which approach is the best way to achieve them.