To support this, we had to provide means for engineers to test and develop their menus within Pick’n’Mix itself, adding

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.

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

We used Wardley Mapping to understand where each of the technical components required to ship our apps on Pick’n’Mix sits in terms of the maturity (and thus cost) against the value they deliver to our audience.

http://team.vidrio.org/xpy/Video-Rauman-Lukko-Mikkelin-Jukurit-v-en-gb-1ehf-3.php

http://old.cocir.org/media/qas/v-ideos-stavanger-oilers-v-valerengens-v-no-no-1bia-22.php

http://main.ruicasa.com/tgq/Video-espana-v-croacia-v-es-es-1slv-10.php

http://molos.bodasturias.com/qxz/videos-avtomobilist-v-tsska-moskva-v-ru-ru-1vtk-8.php

http://www.ectp.org/kzz/video-norge-v-hviterussland-v-no-no-1qlx-13.php

http://team.vidrio.org/xpy/video-Rauman-Lukko-Mikkelin-Jukurit-v-en-gb-1lqg30122020-12.php

http://www.ectp.org/kzz/v-ideos-norge-v-hviterussland-v-no-no-1bnc-13.php

http://main.ruicasa.com/tgq/videos-espana-v-croacia-v-es-es-1zbo-1.php

http://old.cocir.org/media/qas/video-stavanger-oilers-v-valerengens-v-no-no-1gda-26.php

http://molos.bodasturias.com/qxz/v-ideos-avtomobilist-v-tsska-moskva-v-ru-ru-1cdq-13.php

http://elta.actiup.com/cqn/videos-Al-Duhail-Al-Sadd-v-en-gb-joy-.php

http://old.cocir.org/media/qas/videos-Baskonia-Alba-Berlin-v-en-gb-1jyq-.php

http://elta.actiup.com/cqn/Video-Al-Duhail-Al-Sadd-v-en-gb-dmi30122020-.php

http://elta.actiup.com/cqn/v-ideos-Al-Duhail-Al-Sadd-v-en-gb-mbq-.php

http://old.cocir.org/media/qas/videos-Baskonia-Alba-Berlin-v-en-gb-1met-1.php

http://main.ruicasa.com/tgq/videos-espana-v-croacia-v-es-es-1ckr-9.php

http://www.ectp.org/kzz/videos-norge-v-hviterussland-v-no-no-1sai-20.php

http://molos.bodasturias.com/qxz/v-ideos-avtomobilist-v-tsska-moskva-v-ru-ru-1jjg-23.php

http://molos.bodasturias.com/qxz/video-avtomobilist-v-tsska-moskva-v-ru-ru-1zmi-22.php

http://www.ectp.org/kzz/video-norge-v-hviterussland-v-no-no-1ecj-23.php

ak for people whose ancestors we silenced. We get to listen. We get to stop hogging the space. We aren’t giving anyone space, because the space was never ours to take and it is stolen. So if anything we are belatedly giving it back. We need to be uncomfortable. I am writing this essay in praise of discomfort because discomfort is where we need to be. For years, for decades, for centuries if you looked like me you got to live in a world that was very specifically designed to make you comfortable. (The fact that you, individually, didn’t achieve it doesn’t mean it didn’t exist. It means you couldn’t score from third on a double.)

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.

Pick’n’Mix was monolithic, it was a semantically versioned framework that every app had to depend on and bundle itself into. Pick’n’Mix did not stipulate how apps should build themselves, none of our apps were running on the same version of Pick’n’Mix and each time an app needed to take a new version upgrades were laborious and expensive from a development and testing perspective.

This also led to us having significant amounts of duplication across our portfolio of apps. UX patterns implemented time and time again written imperatively with WebGL/Canvas, several integrations and duplicated business logic around how downloads should be handled under certain network conditions, inconsistent bundling tools and inconsistent config approaches across apps.

From this map, and our experience and knowledge of building hybrid web apps over the years, it was clear the majority of our time and money was being spent building our in-house app wrapping technology, and not on the app experiences themselves.

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.

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.

Due to Pick’n’Mix’s un-opinionated stance on how things should be built, each app had to maintain its build pipelines and menus/games had to orchestrate their own interaction with the GMI, ultimately there was no sharing or composability between apps. On the surface, abstracting native functionality and business logic behind the GMI seemed sensible and good value for money, a single, well-defined API for fetching remote data, right?! Digging into this further though, it was clear that we’d simply offset the cost away from agencies having to build the native functionality (which is good in itself) to agencies having to integrate with an API that was just as complex and potentially more un-intuitive than if we did nothing at all.

The web is an amazing thing; it can turbocharge your ability to get things done and ship content anywhere, but it’s flexible too, making it easy to box yourself into a corner of unsustainable bespoke implementations, before you know it your once esoteric requirement is a web standard.

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.