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.

I like building small web apps for little tools, prototypes and game ideas. Lately I use AI to generate starting points, but I had no easy way to keep iterating and use them from my phone.

There are some good native code editors on iOS, but I wanted something simpler that doesn't need an App Store install or costly subscriptions for basic stuff. So I built VanillaPad as a PWA.

What it has:

• Multi-file HTML, CSS & JS editor
• Live preview while you code
• Built-in JS console
• Everything stays local on your device
• Optional GitHub sync if you want a backup or to continue on desktop

Some stuff that was hard to build as a PWA: making the mobile keyboard not annoying to type code with, and sandboxing the preview so your code can't break the app.

Not trying to replace desktop IDEs. Just wanted my phone/tablet to be a real place to build html apps when I am commuting or away from a laptop.

If you like tinkering with vanilla JS/HTML apps, or just want a simple way to code from your couch or bus ride, please give it a try using the link below and share your thoughts. Thanks!

https://vanillapad.dev/

⚽️ PizarrApp, una Progressive Web App de pizarra táctica de futbol.

Funciona 100% en el navegador, sin registro, sin anuncios, soporte offline, exportación a PNG/PDF, modo vertical para móvil, zoom táctil y marcador integrado.

Accede aquí: https://pizarrapp.vercel.app/

Hey everyone, I’m building TeamHub to completely replace messy paper schedules and group chats for coaches, parents, and players.

​I just locked in my Act 4 features: a master dropdown to switch between teams/clubs, a built-in scoreboard, a family linking system to keep parents synced, and a payment tab for gear/fees.

​Official launch is July 20th! I only have enough credits left for two more update phases (Act 5 & 6) before release. Would love to hear your feedback on the UI layout! What features are essential for your local sports teams?

I already have a Web app and iOS app that are feature identical. I don’t have an android phone or use android at all so I have avoided building a native app so far. Since I already have a fully functional web app, how big of a lift is it to wrap it as a PWA and release it to the Google play store?

[tangent](https://tangent.fyi)

Hey all,

I’ve been working on this for a while and could use some feedback. I’ll even pick and give a user that joins, and gives it a sincere try, a $20 gift card or something.

I made a cross media recommendation and library app. I’ve also built out a Claude mcp connector (more to come).

Essentially you create your account, select your “Tangent 10” across movies, tv shows, books, and/or podcasts. And then it starts giving you recommendations via email or push (if installed). It’s pretty good with recommendations now and uses a database, not pulling APIs every time.

The main draw is the Daily Deck. You get a few title cards each day and then you can pass, save, or indicate you’ve already enjoyed that piece of media and it gets added into the feedback loop.

I’ve worked to be able to import Goodreads and letterboxd outputs and then be able to automatically pull in updates from your account on a recurring basis if you don’t want to drop them.

Trying to keep it low tech and only take up a fraction of your day so you can actually enjoy the recommendations.

It’s free, it’s rough in a few places, and I’d genuinely love a few strangers to poke at it. Tell me what’s confusing, what recs feel off, what you wish it did.

Feel free to dm or post here.

Thanks!

Otagon (otagon.app) is a PWA that gives spoiler-free game hints from a screenshot. Went PWA-first because the use case is "second screen while gaming" — installable on phone, works alongside the game, no app-store friction, share-target for screenshots. Stack: React/TS, Supabase, service worker for offline shell, Gemini for the hints. Happy to talk through the PWA decisions — and feedback welcome.

Hi everyone,

I've been building a browser-based passport and ID photo maker and I'd really appreciate some honest feedback before I keep improving it.

What it does:

Resize photos for passport/ID requirements

Remove or replace the background

Adjust face position and zoom

Optional suit overlay

Everything runs locally in your browser (no uploads, no account, no server-side image processing)

I'm especially looking for feedback on:

Mobile usability

UI/UX

Bugs or things that don't work

Features you'd expect from a tool like this

Whether you'd actually use or recommend it

The app is completely free to test.

Link: https://global-photo-studio--appcom4788.replit.app/

I'm a solo developer, so even small suggestions are appreciated. Thanks!

Reviews, please. What would make it better?

Hey everyone,

​Like a lot of you, I’ve spent way too much time dealing with sports management apps that lock basic features (like player availability or messaging) behind subscription paywalls or force parents to sit through unskippable video ads just to see what time kickoff is.

​I decided to do something about it. For the last few months, I’ve been building TeamHub using React, Lovable, and Supabase. It’s launching tomorrow, July 15th.

​It is a completely free, ad-free Progressive Web App (PWA) that you can install directly to your home screen from the browser. I packed it with features that competitive clubs actually need:

​Real-time chat and PWA home screen push notifications.

​RSVP tracking including "Injured" status locks.

​A multi-child family calendar that combines different schedules into one color-coded view.

​A sideline live-scoreboard tracker with an approval queue for coaches.

​Automated payment tracking that lets coaches input Venmo/Cash App details so parents can copy/paste and pay directly without platform fees.

​I’m launching the first wave tomorrow. I’d love to get some feedback from coaches, league organizers, and parents here on what else we should add next (we're already mapping out an internal AI team assistant!).