From this map, and our experience and knowledge of building hybrid web apps over the years, it was clear the majority of

Progressive Web Apps are yet to make an appearance across any part of the Apple ecosystem, but we know Safari has been adopting more and more modern web standards which we can use to our advantage as we develop this technical strategy.

A declarative, component-driven architecture will allow us to drive more re-use, increase consistency, and reduce platform-specific implementations across App Web. We chose React.js to enable us to build up this architecture

In 2020, the problem of wrapping HTML5 content for app stores is a well-solved one. Several open-source tools exist that can bundle HTML5 content into a native app, including PhoneGap, Cordova, Capacitor.js, Framework7, Ionic plus others. Progressive Web Apps (PWAs) and Trusted Web Apps are maturing as standardised ways of building portable, app like web experiences. As well as this, platforms are beginning to support PWAs/HTML5 apps as first-class deployment types, from Android via the Trusted Web Activity through to Amazon Fire TV sticks. Service Workers, Web Workers, and many other mature/newly emerging web standards are coming to fruition that makes building native-like apps on the web a reality.

We know, however, that there will be gaps in platform support. These gaps require us to have a flexible architecture that puts modern web standards at the heart of our engineering but retains the ability to patch in polyfills/native implementations where required.

Once we set out our principles, we ran some experiments to answer a series of questions. How hard can we push the web today? How close to an app store ready app can we get with little to no native engineering? Could we move all natively built user interface components out to web components? Could we avoid building our own hybrid app framework full stop?

There is no framework — the most important principle, we want to stand on the shoulders of giants and define a set of opinions that make building our experiences familiar to any developer who has worked on a modern web stack recently

Emerging technology and open source tooling give us the capability of shipping compliant Progressive Web Apps to all app stores. We identified Ionic’s Capacitor.js to be the best choice to wrap compliant PWAs for app store distribution

http://elta.actiup.com/cqn/Video-Umut-Akkoyun-Pavel-Kotov-v-en-gb-1mhs30122020-14.php

http://main.ruicasa.com/tgq/video-tecnyconta-zaragoza-v-nizhnii-novgorod-v-ru-ru-1shb-1.php

http://main.ruicasa.com/tgq/videos-Tecnyconta-Zaragoza-Nizhny-Novgorod-BC-v-en-gb-1yzg-.php

http://old.cocir.org/media/qas/Video-rungsted-v-esbjerg-energy-v-da-da-1ttm-13.php

http://main.ruicasa.com/tgq/Video-Tecnyconta-Zaragoza-Nizhny-Novgorod-BC-v-en-gb-1asj30122020-7.php

http://old.cocir.org/media/qas/video-Odense-Bulldogs-Frederikshavn-White-Hawks-v-en-gb-1iqp30122020-.php

http://main.ruicasa.com/tgq/Video-Tecnyconta-Zaragoza-Nizhny-Novgorod-BC-v-en-gb-1pjx-2.php

http://old.cocir.org/media/qas/Video-Odense-Bulldogs-Frederikshavn-White-Hawks-v-en-gb-1uim-16.php

http://www.ectp.org/kzz/videos-iokerit-v-khk-sochi-v-ru-ru-1oxn-26.php

http://www.ectp.org/kzz/videos-iokerit-v-khk-sochi-v-ru-ru-1pjh-9.php

http://old.cocir.org/media/qas/video-Odense-Bulldogs-Frederikshavn-White-Hawks-v-en-gb-1xib30122020-16.php

http://www.ectp.org/kzz/v-ideos-iokerit-v-khk-sochi-v-ru-ru-1hfg-14.php

http://main.ruicasa.com/tgq/Video-v-gr-gr-1ofu-15.php

http://old.cocir.org/media/qas/videos-Herning-Blue-Fox-Herlev-Eagles-v-en-gb-1gnv-.php

http://elta.actiup.com/cqn/v-ideos-Yertis-Pavlodar-Kazzinc-Torpedo-v-en-gb-lnx-.php

http://www.ectp.org/kzz/v-ideos-iokerit-v-khk-sochi-v-ru-ru-1afm-14.php

http://old.cocir.org/media/qas/videos-Herning-Blue-Fox-Herlev-Eagles-v-en-gb-1sgj-23.php

http://main.ruicasa.com/tgq/videos-v-gr-gr-1grh-3.php

http://main.ruicasa.com/tgq/Video-v-gr-gr-1whs-7.php

http://www.ectp.org/kzz/Video-avtomobilist-v-tsska-moskva-v-ru-ru-1ybj-2.php

ssential for machine learning. We will use statistics to understand the data prior to training a model. When we take samples of data for training and testing our models we need to employ statistical techniques to ensure fairness. When evaluating the performance of a model we need statistics to assess the variability of the predictions and assess accuracy.

We learnt that as of today, shipping Progressive Web Apps to many platforms is becoming a reality. Whether it is Androids support for PWAs in Google Play via a Trusted Web Activity, or support for modern web standards across a range of smart devices from Smart TVs to Fire TV Sticks — it’s clear this is a rapidly changing and improving field.

Our unique and immersive user interfaces also means that we don’t need to match the native system look and feel. Having our own design system that kids are already familiar with, across all of our experiences, places us in a unique position where a single code implementation makes sense.

It is clear that continuing to maintain our hybrid app wrapping framework in 2020 was unsustainable, so we decided to re-orientate ourselves around a series of principles to better inform a more sustainable technical approach to building experiences that can be shipped onto an app store.

Re-built our entire proprietary app platform in less than a year whilst rebuilding all our menu experiences to have highly reusable, declarative front ends at the same time

The Universal App Platform Architecture. The diagram illustrates the relationship between the Progressive Web App, the App shell for App Stores and how each are built and deployed respectively. High res image: https://github.com/bbc/uap-architecture/blob/main/container-diagram.png

Modern web standards like Progressive Web Apps now give us the ability to build app quality experiences with just web technology — we should embrace the PWA as our core development environment and optimise for this as a priority

This is a significant product and technical change for us. We’re shifting our focus away from “we build native apps” to “we build immersive experiences for any platform”. This new way of thinking enables us to build consistency into the platform as a whole whilst also reducing the cost of building our products, reducing cognitive load across all disciplines and making room for us to focus on new product propositions.