That would be nice, however you can install the page as a program on Android, and the time and cost to develop mobile apps is not small, and that effort may be better directed towards adding more functions to the base program esp adding more models
Aquamarine Pie
•
May 15
It looks like maybe there is a middle ground that would perhaps let you fix the broken behavior when the PWA is not in the foreground.
Capacitor lets you take your existing PWA/web code (HTML, JS/TS, React, Vue, Svelte, etc.) and wrap it in a native Android project. You keep most of your UI and logic while gaining access to native plugins for background work.
Advantages over pure PWA/TWA:
Use native Android background APIs via JavaScript plugins
Better push notifications (native FCM instead of or alongside web push)
Can show persistent notifications and run with higher priority
How easy is it? If you’re already a web developer, it’s quite approachable (CLI-driven). You don’t need to rewrite your app in Kotlin/Java.
High-level steps:
In your existing web/PWA project:
npm install @capacitor/core @capacitor/cli
npx cap init
Add the Android platform: npx cap add android
Copy your web assets: npx cap copy android
Install relevant plugins. Popular ones for background use include:
@capacitor/push-notifications (native FCM)
Community plugins for background fetch, background mode, or background tasks
You can also write or use plugins that expose WorkManager or ForegroundService
Open the project in Android Studio (npx cap open android) for final configuration, signing, and any custom native code.
Build and distribute via Google Play.
You can gradually migrate parts of your logic to use the plugins while keeping the rest as web code. Many PWAs have been successfully converted this way.
Log in to comment and vote
Comments4
Purple Pumpkin
Sep 14, 2025
Besoin en urgence de l'app native smartphone. Car utilisation laborieuse sur smartphone
Aug 13, 2024
as of now, you can add the app as PWA, it works like an iOS or Android app with the app icon on homescreen: https://docs.typingmind.com/getting-started/use-typingmind-as-a-desktop-or-mobile-app
Maroon Telescope
Apr 21, 2024
That would be nice, however you can install the page as a program on Android, and the time and cost to develop mobile apps is not small, and that effort may be better directed towards adding more functions to the base program esp adding more models
Aquamarine Pie
May 15
It looks like maybe there is a middle ground that would perhaps let you fix the broken behavior when the PWA is not in the foreground.
Recommended Approach: Ionic Capacitor (Best “Relatively Easy” Option)
Capacitor lets you take your existing PWA/web code (HTML, JS/TS, React, Vue, Svelte, etc.) and wrap it in a native Android project. You keep most of your UI and logic while gaining access to native plugins for background work.
Advantages over pure PWA/TWA:
Use native Android background APIs via JavaScript plugins
Better push notifications (native FCM instead of or alongside web push)
Background fetch, periodic tasks, foreground services, background location, persistent processing
Can show persistent notifications and run with higher priority
How easy is it?
If you’re already a web developer, it’s quite approachable (CLI-driven). You don’t need to rewrite your app in Kotlin/Java.
High-level steps:
In your existing web/PWA project:
npm install @capacitor/core @capacitor/clinpx cap initAdd the Android platform:
npx cap add androidCopy your web assets:
npx cap copy androidInstall relevant plugins. Popular ones for background use include:
@capacitor/push-notifications(native FCM)Community plugins for background fetch, background mode, or background tasks
You can also write or use plugins that expose WorkManager or ForegroundService
Open the project in Android Studio (
npx cap open android) for final configuration, signing, and any custom native code.Build and distribute via Google Play.
You can gradually migrate parts of your logic to use the plugins while keeping the rest as web code. Many PWAs have been successfully converted this way.