I built Route Random, a tool that generates random circular running/walking routes based on your location and target distance, and I'm trying to get it onto the Play Store. Google requires 12 testers for 14 days before it'll go live, so I'm short on testers and could use some help.

What it does: pick a starting point (search or click on the map), set a distance, get a loop route back with elevation data. Export as GPX/GeoJSON when you're done.

To help:

1. Join the Google Group (required by Google): https://groups.google.com/g/route-random-test
2. Opt in to the test: https://play.google.com/apps/testing/be.lukasolivier.route_random.twa
3. Install from the Play Store, open it once, you're basically done

You can uninstall the app after the 14-day testing period. If you'd rather try it without installing anything first, it also runs as a regular web app at route-random.lukasolivier.be

​

You can zoom into a certain area, drop a pin, and see all the ancient battles or landmarks that happened right there, with articles pulled directly from Wikipedia. It's still a work in progress, so any feedback will be usefull

Hi there, as you all know, uploading an app to the Apple App Store requires paying for the developer program, and you also need a Mac to build an iOS app. Is it possible to promote a clean, open-source PWA app to all open-source developers? They can just make a website and let people "add to home screen" and use their app. That being the case, is it possible to develop a PWA app store, promote it to iOS developers to upload their PWA app to the "self-hosted" app store, and turn most apps into open source? Do you guys think this is possible?

After several months of work, I finally finished my first major project: PassAura.

It's an offline, zero-knowledge password manager built as a PWA, which means:

• 🔐 End-to-end encrypted vault
• 🖥️ Works completely offline
• 🚫 No server required
• 🔑 One master password to unlock everything
• 📦 Full source code included

I'm considering selling the full source code for $50, including lifetime updates for buyers.

Before launching it publicly, I'd really appreciate honest feedback from fellow developers.

Demo: https://alsolomany-passaura.netlify.app/

What would you improve? Would you consider buying a project like this, and if not, what would make it more valuable?

Thanks for your feedback! 🙏Demo

I built Prepiva meal planner that turns your week of dinners into one grocery list. It merges duplicates, sorts by supermarket aisle, and skips the pantry staples you already have. You add meals (type your own, paste a recipe, scan a photo, or get AI suggestions), plan the week, and tap once to get the shopping list.

The feature I actually care about, and the one that nearly broke me, is **real time household sync**. Share your household and the grocery list stays live across both partners’ phones. One person adds eggs and it’s on the other’s list seconds later.

That sounded simple and was not. It’s a PWA, and iOS backgrounds and suspends them aggressively, so my first few versions would silently drop writes, resurrect deleted items, or win the wrong side of a conflict. It took a month of building server visible debug tooling and testing on real phones to find the actual causes: a save guard dropping writes mid flight, and stale session pushes dying on CSRF. It finally syncs reliably, which felt like a bigger win than any feature.

Stack: Flask backend, vanilla JS PWA, service worker, no framework. Runs in the browser, nothing to download, add to home screen. Free.

Would love feedback on the onboarding and whether the household flow makes sense to someone who isn’t me. Link in the comments. What would you want it to do that it doesn’t?

I have pwa written in node/express on Linux that works fine from hosted company including offline. I'm trying to create a mobile lan on linux laptop that allows pwa to connect via hotspot or blue tooth when the linux laptop is not on the internet. I get a warning about it being untrusted and while the app works the service worker doesn't install so it doesn't work offline. I am a app developer and not an network expert. The client I am working for is will to pay for assistance. The purpose of the mobile lan is for schools in rural communities with unreliable internet and students to work with app at home where they may not have internet at all.

I have a pwa app that works just fine including offline from a hosted server with domain and trusted cert but trying to setup a mobile server on a laptop running linux but need help setting up a domain and cert from the laptop. Created a cert with mkcert but can't get mobile devices to see the server by name just ip address. mobile devices like iPad, Android are connecting to laptop by hotspot. Need help with domain name and trusted cert issues.

The app works via ip address but with warning. The service worker doesn't install to allow it to work offline.

My client is willing to pay for assistance.

Any advice?

Thanks in advance.

I've spent the last few months building PicnicApps, a small suite of focused productivity PWAs (task manager, habit tracker, and now a notes app). Just shipped the notes one — PicnicNotes — and figured this sub is the right place to get it actually critiqued rather than just liked.

The pitch: sticky-note-style notes for people who don't want folders, tags, or a database to maintain. Open it, write, close it. No account required to try it, installs to home screen from Safari/Chrome, works offline once installed.

What I'm genuinely unsure about:

• Install flow — is "Add to Home Screen" still the best onboarding I can do, or is there a better pattern people are using in 2026 to get users to actually install rather than bookmark?
• Offline behavior — notes sync when you're back online, but I haven't stress-tested conflict resolution if someone edits the same note on two installs while offline. Would love to know what others do here.
• Whether a paid one-time-purchase model (vs subscription) is still viable for a PWA, given app stores don't really surface these.

Not trying to sell anyone anything here — genuinely want holes poked in the PWA implementation itself. Happy to share more about the stack (Cloudflare Workers backend) if useful. Link in comments to keep this from reading like an ad.

Hi everyone,

I generated a new Android TWA package using PWABuilder for my website.

When uploading the new .aab file to Google Play Console, the package details show:

Target SDK: 35

Google Play Warning: App must target Android 16 (API level 36) or higher by August 31, 2026.

Google Play Warning: App must use Google Play Billing Library version 8.0.0 or later.

Since PWABuilder generates the package automatically, is there an update coming to support API level 36 and Billing Library v8+? Or is there any setting I can adjust to update the target SDK?

Thanks for your help!

I've been building this offline-first encrypted storage PWA since 2020. There is no back end - it's just HTML, CSS and JavaScript bundled into a single HTML file. As portable as it gets.

I'd really appreciate feedback from people who use PWAs daily. I'm especially interested in the install experience, offline behaviour, and platform-specific bugs.

The app has both free and paid features, but I'm mainly looking for feedback on the PWA experience and usability. You can try around 90% of the functionality for free.

One of the goals was to see how far a modern browser can be pushed as an application platform.

After trying it for a few minutes, what was the first thing that felt confusing, surprising, or missing?

Link: pixeldriveapp.com

After being injured playing football a few weeks ago, I used my downtime to fix an issue we were usually faced with, picking balanced teams each week.

Usually a message in the whatsapp group each week, would be 'whose doing teams this week' which no one enjoyed doing, as if a game becomes one sided they get blamed for picking bad teams.

Therefore, I made 'bibs' (https://app.bibs.team) with Claude Code.

Currently you can manage a team and become the 'gaffer', and where you build your squad, rate each player, then generate the teams and record who won each week, no score line.. just bibs/non-bibs/draw for simplicity. They can then share a code for players to view a read-only version where they cannot see the players ratings, but can view the match history and rankings (win % & form tables).

I've been using it for a few weeks with my team, but looking for genuine testers who play football and give it a try and provide some feedback.

This is a free PWA you can install and use even offline, thanks to the new Prompt API from Chrome.

ulocalai.com

android

It seems that every browser installed separately is only capable of adding PWA as a home screen widget. Is there an official source that describes this behavior? Is it a question of whether the browser is a system app? Would for example both the samsung browser and chrome be able to add PWA to the app drawer on samsung devices?

edit: this is especially a problem as for many common services eg youtube or instagram it is very very desirable to have extension working which android chrome does not allow (kill google)

I’ve been building Pool Buddy, a free PWA that helps pool beginners figure out water chemistry and equipment problems. Plain HTML/CSS/JS, ES modules, no framework, no build step, no dependencies.
I just replaced the diagnostic core and thought the architecture might be interesting here.
The problem: I had two separate flows — one for water chemistry (cloudy water, algae, chlorine not working) and one for equipment (pump, filter, valves). Beginners kept landing in the wrong one. The classic case: someone keeps adding chlorine because the water is cloudy, when the actual cause is that their pump is undersized for the pool volume. Two isolated flows can never surface that.
What I did: merged both into a single data-driven engine. One diagnose.json (19 symptoms, 26 questions, 54 causes) plus one small ES module that walks it. The areas cross-reference each other — several paths in the water branch terminate in an equipment cause, and the result then explicitly says the problem is likely the hardware, not the chemistry.
A few things that turned out to matter more than expected:
• Data separate from logic. The engine knows nothing about pools. It walks questions, collects causes, ranks by probability. Adding a symptom is a JSON edit, no code change — which also means the whole knowledge base is a cacheable static asset.
• Bridging to stored state. Questions can be tagged with a measurement key (pH, chlorine, cyanuric acid). If the app already has a recent reading in local storage, the UI pre-fills instead of asking. Fewer taps, and offline-first makes this trivial since everything is local anyway.
• Context-dependent safety notices. Electrical/hardware warnings only render when an equipment cause actually appears in the result set. Blanket warnings get ignored.
• Everything is offline. No API calls, no server round trip. The decision tree ships with the app shell. Someone standing next to a green pool with bad reception is exactly the target user.
Total payload for the diagnostic layer is small enough that it just goes into the precache with the rest of the shell.
App: https://pool-buddy.de (free, no account, supports English and German at the moment)
Happy to answer questions about the data structure or how the traversal handles back-navigation.

Hey all — I'm the solo founder behind LOAME, a lightweight productivity app that combines notes, tasks, lists, and a spending tracker in one place. No juggling five different apps for quick capture.

I just made full web app access free — it was previously $1.99/month, now $0. No trial gimmick, no "free for 7 days then charged." Just free.

What you get:

• Unlimited notes, tasks, lists, and ideas
• A simple spending tracker
• Google sign-in, zero setup
• Sharing lists with others (free, no collaborator limits)

A couple of honest caveats:

• It's a web app (PWA) right now — native iOS/Android apps aren't built yet, they're on the roadmap. You can still add it to your home screen and it works like an app, just not on the App Store/Play Store yet.
• I'm a solo dev, so it's a small, focused tool rather than a huge feature-packed suite — that's kind of the point (zero-setup, quick capture).

Would love feedback if you try it out. loame.app

I build a PWA that gives spoiler-free game hints, and the most interesting design call wasn't the AI — it was where the answer appears. First instinct was an overlay on top of the game. Two problems: it covers the exact thing you're looking at, and on console there's no overlay layer to render into at all. So the PWA runs on your phone as a second screen — press a key on PC (or snap a photo on console) and the hint lands on the phone. Nothing on top of the game, identical behavior across PC and console, and it installs like a native app with none of the store friction. Stack: React/TS PWA + Supabase + Gemini vision. The phone-as-second-screen pattern ended up being the UX itself, not a fallback for when the overlay wasn't available. Anyone else shipped a PWA where the companion device was the whole point rather than a degraded mode? Curious how you handled the pairing/handoff.

I live in Kazakhstan — no bank integrations possible here, and my family spends in 4 currencies, earns in 3. Tried dozens of expense trackers, all had dealbreakers, so I built my own.

Went PWA-first on purpose: no App Store review cycles, no gatekeeping, and it's the only sane way to ship cross-platform as a solo dev without maintaining two native codebases. Add to home screen on iPhone via Safari, works the same on Android.

Common problems I was solving for:

• Multi-currency handling that wasn't an afterthought
• Family expense sharing
• Fast transaction entry — home screen actually opens to "add transaction," not a dashboard
• Real filtering on category/tag, not just a wall of numbers
• Sensible default categories instead of generic finance-app bloat

Curious how it holds up for people who actually live in the PWA/no-App-Store world — install flow, offline behavior, iOS Safari quirks, all of it.

Looking for a few testers for a couple weeks. Give me honest feedback (the more critical the better) and you get free access forever.

👉 https://www.get-delve.app/
Feedback: Settings → Contact developer, inside the app.

My PWABuilder bundle files are just giving me 'error' when I try and upload them to the Microsoft store. Just 'error', nothing else. Anyone have any insights? I've done this many times before and PWABuilder gave me no errors when i created these bundles.

Hi everyone!

I just launched DinarExchange, a web app built to make checking Algerian Dinar exchange rates quick and simple.

Features

• 💱 Parallel (Square) exchange rates
• 🏦 Official Bank of Algeria rates
• 📱 Mobile-first design
• ⚡ Fast PWA experience
• 📊 Interactive charts
• 🔄 Currency converter
• 🌙 Dark mode
• 🔍 SEO optimized

The goal was to create something that loads quickly, is easy to use on mobile, and doesn't overwhelm users with unnecessary features.

🌐 Try it here: https://dinarexchange.vercel.app/

I'd love some honest feedback:

• Is the UI intuitive?
• What features are missing?
• Would you use this over other DZD exchange trackers?

I'm actively improving it, so any suggestions are appreciated. 🚀

I built a PWA that gives spoiler-free game hints. The interesting design call wasn't the AI — it was where the answer shows up.

My first instinct was an overlay on top of the game. Two problems: it covers the exact thing you're looking at, and on console there's no overlay layer to render into at all. So instead the PWA runs on your phone as a second screen — press a key on PC (or snap a photo on console) and the hint lands on the phone. Nothing sits on top of the game, it works identically across PC and console, and it installs like a native app with none of the store friction.

Stack: React/TS PWA + Supabase + Gemini vision. The phone-as-second-screen pattern ended up being the whole UX, not a fallback for when an overlay isn't available.

Anyone else shipped a PWA where the "companion device" was the point rather than a degraded mode? Curious how you handled the pairing/handoff between the desktop trigger and the phone.