Create a JSON file, call it manifest.json, fill out the fields recommended by Google. Then create a JavaScript file, cal

http://startup.munich.es/xuo/video-Primeiro-de-Agosto-Kaizer-Chiefs-v-en-gb-kjr30122020-.php

http://team.vidrio.org/rtr/Video-ibiza-eivissa-v-celta-de-vigo-v-es-es-1vta-21.php

http://startup.munich.es/xuo/v-ideos-Primeiro-de-Agosto-Kaizer-Chiefs-v-en-gb-yuc-.php

http://startup.munich.es/xuo/video-Primeiro-de-Agosto-Kaizer-Chiefs-v-en-gb-uty-.php

http://startup.munich.es/xuo/v-ideos-TS-Galaxy-Baroka-v-en-gb-jwc-.php

http://team.vidrio.org/rtr/video-ibiza-eivissa-v-celta-de-vigo-v-es-es-1dqd-7.php

http://old.cocir.org/media/cla/Video-Konyaspor-Galatasaray-v-en-gb-1uys-17.php

http://startup.munich.es/xuo/videos-TS-Galaxy-Baroka-v-en-gb-pnd-.php

http://team.vidrio.org/rtr/videos-ibiza-eivissa-v-celta-de-vigo-v-es-es-1nla-6.php

http://old.cocir.org/media/cla/videos-UD-Ibiza-Eivissa-Celta-Vigo-v-en-gb-1dzg30122020-.php

http://startup.munich.es/xuo/v-ideos-TS-Galaxy-Baroka-v-en-gb-wkb-.php

http://startup.munich.es/xuo/videos-Sirens-Birkirkara-v-en-gb-bxl30122020-.php

http://old.cocir.org/media/cla/Video-UD-Ibiza-Eivissa-Celta-Vigo-v-en-gb-1ffq-17.php

http://elta.actiup.com/mto/v-ideos-Coton-Sport-Green-Eagles-v-en-gb-1tiv-2.php

http://startup.munich.es/xuo/Video-Sirens-Birkirkara-v-en-gb-lml-.php

http://team.vidrio.org/rtr/Video-ibiza-eivissa-v-celta-de-vigo-v-es-es-1diw-20.php

http://team.vidrio.org/rtr/v-ideos-Konyaspor-Galatasaray-v-en-gb-1lve-.php

http://startup.munich.es/xuo/video-Sirens-Birkirkara-v-en-gb-sad30122020-.php

http://www.ectp.org/cqt/Video-Al-Bidda-SC-Al-Shamal-v-en-gb-1gfi30122020-24.php

http://startup.munich.es/xuo/v-ideos-Ermis-Aradippou-Nea-Salamina-Famagusta-v-en-gb-hys-.php

show past on the left and the future to the right. The list goes on. Designing contrary to this visual vernacular will only cause confusion. As an example, check out the line graph in this graph, which was released by Reuters in 2014 and quickly incited political debate.

Or we could also talk about the appinstalled event. It would be really useful if it wasn’t for the fact that this event is never triggered at all on iOS/Safari or Android/Samsung Internet. After the app is installed, you’ll likely want to hide or disable the install button. How do you do that when you’re not even sure the app was installed in the first place?

And on the web… things evolve. Pretty fast. So if tomorrow Apple, Samsung or Google make a change I’ll have to 1- find a way to make sure I’m aware of it and 2- rewrite my code accordingly.

So do yourself a favor, sign up for a Progressier account, replace your hard-coded PWA implementation with it, and let me take care of that boring stuff for you. All it takes is 1 line of code. 2 minutes of your time. And $0 of your money.

You don’t have to deal with what happens when the user is on iOS. Or has a device that’s not compatible with PWAs. Or has installed your app. Forget that crap. Progressier deals with this for you. And just like that, you turned two weeks of work into 25 seconds of work.

Oh yeah and… what happens when I change my logo? Am I supposed to remember that it’s in the meta tags of my HTML document but also referenced somewhere in my JavaScript to dynamically create the assets that iOS needs? No way I’m going to remember that 2 years from now.

In fact, the greatest strength of PWAs is also its biggest weakness. With apps living on the open web, nobody is really in control of the format. And when nobody is in control, things often end up being messy.

And even on Chrome — when beforeinstallprompt is fired, it means the app is installable. But what does it mean when it… doesn’t get fired? Does it mean the app can’t be installed? Or that the app is already installed? And what am I supposed to do with my install button while I wait for the beforeinstallprompt to fire or not fire?

My PWA is essentially only 4 variables: a name, a domain, a color and a logo (I’m simplifying a bit here but you get the idea). I want to tell someone what my 4 variables are. And let that someone figure out the rest.

With Progressier, building a PWA is precisely what I described above. You tell the platform your 4 variables. That’s it. The software generates the right assets in the right place in the right size. And when Google or Apple make changes, we update our code — not yours — so you always have the latest PWA implementation on your site. Goodbye, maintenance.

So since I was dead set on solving that problem, I thought that I could just as well try to solve it for everyone else too. And that’s exactly what I did with Progressier.

Google is the reference when it comes to PWAs. So if you create one yourself, chances are you’ll read their documentation. It’s pretty good, except it’s really just good for Chrome.

On Windows/Chrome, the beforeinstallprompt will also sometimes be emitted several times per session. And sometimes after the app has been installed. Meaning that by relying on that event, you could ask users to install the app… after they’ve installed it. On iOS/Safari, it never gets triggered at all. So you never even get an opportunity to tell your users your app is installable.

And that — ladies and gentlemen — is called reinventing the wheel. And while some wheels can be fun to reinvent to learn how things work, this particular wheel is no fun at all. Nor does it teach you anything valuable.

And that’s just one example of what Progressier does. It also automatically tracks app installs, lets you set up rules to decide when to promote installation of your PWA, generates all the right logos, and so much more. And that’s just version 1. Push notifications, offline, caching strategies, automated app store submissions — there’s a lot of pretty cool stuff in the roadmap.