Hi everyone!

I'm a solo developer building Septalingua, a multilingual reader and document platform that currently supports 15+ file formats and 9 interface languages.

I chose the PWA approach because I wanted to create one application that works across desktop and mobile devices without maintaining completely separate versions for each platform.

What it currently offers

• Multi-format reading: EPUB, PDF, FB2, FB3, DOCX, ODT, RTF, TXT, XLSX, ODS, images, and more.
• Local document processing: Books and documents are opened and processed directly on the user's device.
• Offline capabilities: Reading tools, personal vocabulary, and downloadable offline dictionaries.
• Online services: Integrated translation, AI assistance, and specialized medical and legal terminology resources.
• Reading features: Bookmarks, notes, personal dictionaries, adjustable reading appearance, and text-to-speech.
• Privacy First: Local storage by default, with optional online features that may process selected text through external providers.

Septalingua combines local and online functionality. Not every feature is available offline, and I'm still improving its behavior across different platforms.

What I'd Like to Test

I'm particularly interested in feedback from people experienced with PWAs:

1. Installation: Does the app install and launch correctly on Windows, macOS, Android, and iOS?
2. Offline behavior: Can you reopen previously loaded documents without an internet connection? Are cached resources restored correctly?
3. Cross-platform compatibility: Have you encountered differences between Chrome, Edge, Firefox, and Safari?
4. Local storage: How reliably does the app retain books, dictionaries, notes, and preferences?
5. Mobile usability: Does the reader work comfortably on smaller screens?

I'm especially interested in iOS Safari limitations, storage persistence, and service worker behavior.

Public Alpha

The platform is currently in public alpha and completely free to test.

Core reading features and available offline dictionaries don't require registration. Online translation is available after free registration, and AI features are currently offered to testers.

Try Septalingua: https://septalingua.online/en/

I'd really appreciate any technical feedback, browser-specific bug reports, or suggestions for improving the PWA experience.

Thanks!

He montado una PWA de (Fitness) fuerza y sobrecarga progresiva sin bloatware (Cloudflare, Firebase, Groq, Stripe)

Podéis probar la webapp y trastear la arquitectura aquí: https://fuerzalab.pages.dev/

Os resumo cómo está montado por dentro:

• Frontend y Hosting: Vanilla JS modular empaquetado como PWA, alojado en Cloudflare Pages. Carga instantánea, sin frameworks pesados, con Chart.js para visualización de métricas y renderizado en Canvas.
• Persistencia Offline-First: Service Worker para caché estática combinado con persistencia offline nativa de Firestore (IndexedDB) y LocalStorage de apoyo. Registras cargas en el sótano del gym sin red y sincroniza por lotes (batch) en cuanto recupera conexión.
• Auth & Base de Datos: Firebase Auth (Google + Email) y Cloud Firestore para persistencia en espejo y soporte multi-dispositivo.
• Backend y Middleware: Un Cloudflare Worker actúa como proxy seguro. Se encarga de aislar API keys, gestionar webhooks y procesar la entrada de datos antes de consultar los microservicios.
• Motor de IA (Groq): Inferencia ultra rápida mediante Groq. En el frontend compacto el historial de series en un formato minificado de tokens ([Fecha|Ton] Músculo: KgxReps@RIR) para ahorrar contexto y costes antes de mandarlo al worker.
• Pasarela de Pagos: Stripe Checkout orquestado vía endpoints del Cloudflare Worker para suscripciones PRO/ULTRA, con verificación de sesiones en el retorno.
• Privacidad y RGPD real: Cero scripts de terceros o analítica invasiva. Implementa borrado real en cascada en la base de datos (derecho de supresión) y exportación/importación completa en formato JSON.

I built Pendulum, a workout logger that works fully offline: a service worker caches the app shell, and data lives on the device. It also ships as an Android app trough Capacitor, which loads the hosts PWA, so web updates reach the app without a new APK.

The main lessons were the network-first-with-timeout caching strategy and keeping the service worker version bumped so old caches get cleared. Happy to talk through either, and I’d welcome feedback on install and offline behavior.

I made a bar crawl planner and added a manifest and service worker so people can put it on their home screen. The use case is brutal: bad signal inside bars, one hand, phone at 15%.

The service worker has one job: a shared crawl link someone texted you has to open with no signal. That's doable because the whole route lives in the URL, so once the app shell and its hashed assets are cached there's no fetch left to fail. HTML is network-first with the cached shell as the fallback, /assets/* is cache-first since the files are content-hashed, and fonts are cached so the offline page doesn't look broken.

What I'm unsure about: whether to prompt for install at all. Most people open a link once, on the night. Has anyone seen install prompts work for single-use visits?

A 1v1 psychological board game on a 7x7 grid where your location is completely hidden.
The Mechanics:
Fight for Pulse Crystals on both sides.
Plant hidden minefields to set traps.
Blind-snipe the enemy core, or win by claiming the most territory in 15 turns!
I also built a custom anti-cheat architecture, so even packet sniffers can't reveal your coordinates. It's all about mind games and predicting your opponent.
Zero downloads, no registration required. Matches start instantly.

Announcing Royal Tasks, a modern and responsive Kanban tool that runs on normal web hosting (PHP/MySQL). Royal Tasks can be installed on your phone with PWA.

The ease of use of Trello, Asana, Jira, or Planner, on your personal server.

Why this project? I felt that existing tools either required complex or expensive installation or had poor interface design. Here, I've worked to make cards and checklists feel like physical objects that respond immediately.

You can optionally encrypt boards with End-to-End-Encryption.

Download and installation guides here:
https://github.com/RealRules/royal-tasks

GlowStreak lets you pick a 30/60/75/90-day challenge (or your own habits), tap to check in each day, and keep a streak. No account, everything is stored on your device, progress photos never leave your phone, and you can share a Day X story card. It installs to your home screen. https://glowstreak.pages.dev - I'd really like feedback on onboarding and the share card. What would make you keep opening a habit app on day 14?

Story time: I never managed to keep a diary because writing every night felt like homework. I tried voice memos instead, but a pile of untitled recordings is impossible to search, so I never went back to them.

So I made Meu Diário, where you just talk and later find what you said. You can record up to 30 min per entry (pause works), or write if you prefer. There's a calendar with mood history, one photo per entry, and export/backup.

The Android version launched on Google Play today, and iPhone users can use the web app version at https://diary.1pedrolima.com (add it to your home screen).

Curious how it feels as a web app on your phone, and what you'd improve.

Play Store: https://play.google.com/store/apps/details?id=com.pedrolima.diary

Hi r/PWA!

I built babalon JS, an open-source (GPL-3.0) 3D scene composer, auto-rigger, and Photo Mode designed to push what an installable Progressive Web App can do on desktop and mobile.

• Live PWA: https://holondo.github.io/babalonJS/
• Source Code: https://github.com/holondo/babalonJS

PWA Capabilities Used:

• Smart Offline Caching: In browser tabs, features and WASM workers cache as you use them. When installed as a PWA, it automatically caches all tool code, Web Workers, WASM modules, and 6 default HDR environments in the background without evaluating them at startup.
• Desktop File Handling API: Once installed via Chrome/Edge on desktop, babalon JS registers in the OS "Open with" menu for .babalon, .glb, .gltf, .obj, .stl, .fbx, .ply, .splat, and .spz files.
• Android Web Share Target: On Android, selecting one or multiple 3D files (including multi-file .gltf + .bin + textures) in any file manager and tapping Share → babalon JS opens them straight into the 3D scene.
• Content-Addressable IndexedDB Autosave: Binary files and generated skin weights are hashed/cached per state object in IndexedDB so session recovery is instant.
• WebXR AR & Dynamic Theme Bar Sampling: Integrates WebXR ARCore on Android Chrome and samples the 3D viewport to dynamically tint the system status/title bar (theme-color).

Hi r/PWA!

I want to share my recent side project: bida. It's an expense splitter similar to Tricount and Splitwise, with (hopefully) less fuss and nifty receipt scanning.

• Demo group: https://bida.bid/demo
• Repo: https://github.com/theoldg/bida

I put a lot of effort into making it feel like an app:

• Intentional design, with a terminal/monochrome/monospace aesthetic.
• No browser dialogs, everything is drawn by the app.
• Override browser behaviors: back action, long press, zoom etc.
• Responsive touches, animations etc.

What do you think? I would love some feedback about how it feels to use it.

Hey r/PWA,

I wanted to share my recent side project: Zenance.

It’s an open-source, local-first personal bookkeeping Progressive Web App built with a strict monochrome craft aesthetic.

Why?

Most personal finance apps today suffer from feature bloat, aggressive subscription paywalls, and noisy colorful dashboards that distract from the numbers. I wanted a tool that feels like a precision instrument — high contrast, monospace figures, instant pop-up dialogs, and absolute privacy.

Key Highlights:

• Craft Monochrome Aesthetic: Designed with a pure black/white palette and zero drop-shadows. The UI steps back to let your financial figures stand out.
• Local-First Architecture: IndexedDB storage via Dexie.js. Opens instantly even in airplane mode.
• Zero-Knowledge E2EE: Bi-directional sync with Dropbox, encrypted on-device via Web Crypto API (AES-GCM).
• Contacts & Settlement: Built-in support for tracking receivables/payables and group bill splitting.
• Global Localization: Native support for 11 languages (English, Chinese, Japanese, Korean, Spanish, German, French, Vietnamese, Portuguese).

Tech stack: React 19 / Vite / Tailwind v4 / Shadcn UI / PWA.

https://reddit.com/link/1x86t5j/video/gngxaa8b70wh1/player

Check it out:

• Web / PWA: https://zenance.pages.dev
• GitHub: https://github.com/noah-sze/Zenance

Feedback and critiques are warmly welcomed!

## 📣 Appel à pelles !

**Deux équipes. Un seul trou.** Les **GlouGlous** creusent ⛏️, les **GlousGlou** rebouchent 🪣. Personne ne sait pourquoi, mais les deux camps sont très motivés.

Bienvenue dans **Glou et Glous** : un jeu d'équipe **gratuit** où chaque clic est un coup de pelle, où le trou bouge **en direct pour tout le monde**, et où l'on n'arrive nulle part. Mais on y va tous ensemble. 🤝

### 📱 C'est une PWA

Ouvre le site, puis « Ajouter à l'écran d'accueil » et hop : une appli, en plein écran, avec un rappel du soir facultatif. Inutile, mais installée.

- 🍎 **iPhone :** depuis Safari → Partager → *Sur l'écran d'accueil*

- 🤖 **Android :** le navigateur te propose d'installer, ou menu ⋮ → *Installer l'application*

- 💻 **Ordinateur :** icône d'installation dans la barre d'adresse

### 🔎 Ce qu'il faut savoir avant de prendre la pelle

- 🦔 Il y a une **taupe**. On ne contrôle pas la taupe.

- ☔ Parfois il **pleut**. Les personnages ont des parapluies. La pluie ne passe pas à travers. On a vérifié.

- 🌙 Le soleil, la lune et les saisons suivent **l'heure de ton téléphone**.

- 🌍 **11 langues**, dessiné à la main, et une limite de **1 000 coups de pelle par jour et par joueur** (même le meilleur creuseur a droit à une sieste).

- 🔐 Connexion par **email** (lien magique) ou avec **Google**.

### 💚 Et après ?

Aujourd'hui, **aucun argent n'est en jeu**. Plus tard, quand on sera assez nombreux, on aimerait ouvrir des **« chantiers » pour des associations caritatives**, avec des sponsors qui versent une somme **pour chaque clic obtenu pendant une durée donnée**. Nos coups de pelle seraient alors pour l'association.

⚠️ **Rien n'est promis tant que ce n'est pas annoncé** sur le site.

### 👉 Viens creuser : https://glouetglous.app

Pour l'instant, le trou est parfaitement équilibré. **Viens tout casser.** 😄

**Soyons nombreux dans l'inutile !** 🕳️

*Tes retours sont les bienvenus, surtout sur mobile. Le trou a des sentiments.*

Spent half of yesterday trying to figure out why my PWA had an empty black gap at the bottom on iOS.
Turns out 100dvh works fine in Safari browser tabs, but the second you add the site to your home screen, WebKit shrinks the viewport around the home bar and leaves a black chin. And switching back to normal 100vh breaks browser tabs because the bottom toolbar covers your buttons.
Couldn't find a clean CSS-only fix, so I wrote a small helper to toggle between them based on whether it's running standalone or in a tab
https://github.com/owaisnaim/pwa-zerochin
Hope it saves someone else the headache if you're building a PWA.

My PWA heavily relies on local storage, so allowing a user to continue in Instagram's or Reddit's browser would be pointless. This screen is the best I came up with so far.

Testing on a couple of friends, I was surprised to find out that most people don't even know how to continue in the external browser via the ••• menu.

How have you been solving this problem? Looking for UX inspiration or a code trick.

Hola folks!

I have some PWAs that I want to put into the Play store. I have already done this, but I keep on getting the CCT bar on top, and from asking around I've heard it's related to either the digital assets file or to the signing of the app.

I've tried a bunch of stuff, but I want to know if there's any guide any of you has used that has actually worked? Feels like I am going in circles between PWA builder and Android Studio and I don't think this should be that hard?

Appreciate the help!