Marketing?
How and where do you guys market your pwa and get users for it?
I currently am „stuck“ promoting on Facebook in some groups but it doesn’t seem to do the trick. Been doing that for about 2 months now and don’t really have any users.
How and where do you guys market your pwa and get users for it?
I currently am „stuck“ promoting on Facebook in some groups but it doesn’t seem to do the trick. Been doing that for about 2 months now and don’t really have any users.
Kennt sich hiermit jemand aus oder hat es bereits genutzt?
Meine Frau möchte mich bei meiner Selbstständigkeit unterstützen, jedoch unentgeltlich. Sie ist aktuell arbeitssuchend gemeldet.
Im here because I also need testers.
I created an app for first time pool owners. It’s completely free, got a pool school, all data stays on your device and much more.
Please send me a mail for the closed testing at info@pool-buddy.de
Thanks in advance
I always had a grip case (started with the OnePlus 3 Bumper). Now I got an iPhone 17 pro max today and need a good case. So now I'm wondering whether to go with a grip again or take the Tank.
Can anyone report on the pros and cons of both?
Been building a small PWA (a pool-care app for beginners, but the subject matter isn't really the point here) and figured this sub would actually care about the PWA guts, so here's roughly how it's put together and the stuff that caused me pain.
It's offline-first. The service worker precaches the app shell on install, HTML is served network-first so content stays fresh, and everything else is cache-first. All the app data just lives in localStorage, so there's no backend and no account, nothing to log into. It's plain HTML/CSS/JS with Tailwind, no framework, which keeps it tiny and makes the install basically instant.
The update flow took me a few tries to get right. Early versions would reload the page out from under people while they were using it, which is awful. Now a new version only activates when the user agrees, and I listen for controllerchange to reload exactly once. That "once" matters, because without a guard flag you get a reload loop that looks and feels exactly like the tab freezing. Learned that one the hard way.
iOS was the other headache. Cross-document view transitions are unreliable in standalone iOS PWAs, so I dropped them and do JS-driven page transitions with a fallback instead. Less fancy, but it actually works everywhere.
One thing that helped a lot: I only revalidate the files that actually change (html/js/css/json) and let icons and fonts come straight from the HTTP cache. That alone made updates roughly 10x faster, since it stopped re-fetching a pile of fonts and SVGs on every update.
It's at pool-buddy.de if you want to peek at the manifest and SW. Mostly posting to compare notes: how are you all doing the "new version available" nudge without it being annoying? That's the part I'm still not happy with.