12 Years of PWAs: Why I Ditched the App Store for the Open Web
If you’ve been following our journey at TravelVirgins, you know that Anne and I value freedom above all else. But while we usually talk about the freedom to travel, today I want to talk about a different kind of liberty: the freedom to build without barriers.
For the past 12 years—since around 2014—I made a conscious, professional commitment to build my apps using the Open Web format known as Progressive Web Apps (PWA). Back then, it was a bit of a contrarian bet. The tech world was screaming, "There's an app for that!" and developers were rushing to build heavy, expensive native apps for the Apple App Store and Google Play.
But I saw a different path. I saw a future where you didn't need to download a massive file just to look at a menu or play a simple game. I saw a future where apps lived instantly in your browser, accessible to anyone, on any device, anywhere in the world. That future is here, and I’m all in.
For the past 12 years—since around 2014—I made a conscious, professional commitment to build my apps using the Open Web format known as Progressive Web Apps (PWA). Back then, it was a bit of a contrarian bet. The tech world was screaming, "There's an app for that!" and developers were rushing to build heavy, expensive native apps for the Apple App Store and Google Play.
But I saw a different path. I saw a future where you didn't need to download a massive file just to look at a menu or play a simple game. I saw a future where apps lived instantly in your browser, accessible to anyone, on any device, anywhere in the world. That future is here, and I’m all in.
From Well Drilling to Food Trucks: My PWA Portfolio
My commitment to PWAs isn't just theoretical; it’s been my livelihood. Over the last decade, I’ve built commercial applications for a wide range of clients who needed reliability without the fluff.
Take, for instance, the work I’ve done with well drilling records. These clients are often out in the middle of nowhere, miles from the nearest cell tower. They can't rely on a cloud-based native app that crashes without a signal. I built them PWA solutions that work flawlessly offline, allowing them to input critical data on site and sync it later when they're back in range. That is the power of the PWA "Service Worker"—it caches what you need so the app works when the internet doesn't.
On the other end of the spectrum, I’ve built menus for restaurants and food trucks. Think about it: when you walk up to a food truck, you are hungry. You do not want to download a 100MB app, remember your Apple ID password, and wait for an install just to see if they have tacos. With my PWA builds, customers scan a QR code and the "app" is there instantly. It’s frictionless.
And then there are the games and utilities. I have a passion for building custom games that are actually fun to look at. I believe software shouldn't be boring. By using PWAs, I can easily implement my signature simple-to-use User Interfaces (UI) and splash them with fun, colorful themes. I don't have to fight with Apple's strict design guidelines; I can make the app look exactly how I want it to look, and how I know you’ll enjoy using it.
My commitment to PWAs isn't just theoretical; it’s been my livelihood. Over the last decade, I’ve built commercial applications for a wide range of clients who needed reliability without the fluff.
Take, for instance, the work I’ve done with well drilling records. These clients are often out in the middle of nowhere, miles from the nearest cell tower. They can't rely on a cloud-based native app that crashes without a signal. I built them PWA solutions that work flawlessly offline, allowing them to input critical data on site and sync it later when they're back in range. That is the power of the PWA "Service Worker"—it caches what you need so the app works when the internet doesn't.
On the other end of the spectrum, I’ve built menus for restaurants and food trucks. Think about it: when you walk up to a food truck, you are hungry. You do not want to download a 100MB app, remember your Apple ID password, and wait for an install just to see if they have tacos. With my PWA builds, customers scan a QR code and the "app" is there instantly. It’s frictionless.
And then there are the games and utilities. I have a passion for building custom games that are actually fun to look at. I believe software shouldn't be boring. By using PWAs, I can easily implement my signature simple-to-use User Interfaces (UI) and splash them with fun, colorful themes. I don't have to fight with Apple's strict design guidelines; I can make the app look exactly how I want it to look, and how I know you’ll enjoy using it.
Why I Choose PWA Over Native (And You Should Too)
As a developer and a traveler, my needs—and the needs of my users—are specific. We deal with data roaming caps, spotty WiFi, and older devices. Here is why the PWA format wins for me every time:
The Big Players Agree
I’m not the only one. Major tech giants are quietly moving their focus to PWAs because the experience is simply better.
For 12 years, I’ve been building on the web because I believe technology should be simple, colorful, and accessible. Whether I'm coding a utility for a drilling company or a fun game for a long flight, PWA is the tool that lets me do it best.
As a developer and a traveler, my needs—and the needs of my users—are specific. We deal with data roaming caps, spotty WiFi, and older devices. Here is why the PWA format wins for me every time:
- No "App Store" Gatekeepers: I don't need permission from Silicon Valley to publish an update. If I fix a bug in my game or update a price on a food truck menu, you get it instantly. No "Update Required" pop-ups.
- Data Efficiency: Native apps are bloated. A standard app might be 150MB. My PWAs are often less than 1MB. When you are roaming or on a slow connection, this is the difference between the app loading instantly or not loading at all.
- Universal Access: I build once, and it works on your iPhone, your Android, your tablet, and your laptop. I love this inclusivity. It means nobody is left out just because they have the "wrong" phone.
The Big Players Agree
I’m not the only one. Major tech giants are quietly moving their focus to PWAs because the experience is simply better.
- Uber: Their PWA loads in 3 seconds on 2G networks.
- Starbucks: Their PWA is 99.84% smaller than their iOS app and lets you browse the menu offline—similar to the tech I use for my food truck clients.
- Spotify & Pinterest: Both use PWAs to ensure speed and engagement without forcing a download.
For 12 years, I’ve been building on the web because I believe technology should be simple, colorful, and accessible. Whether I'm coding a utility for a drilling company or a fun game for a long flight, PWA is the tool that lets me do it best.
Scan to read on mobile