It's only the PWA without a real backend, so there is no server that could run any processes or certain extensions. That's also the reason why you don't have a terminal there. Same for github.dev
So as already suggested, Codespaces (or maybe a self-hosted instance of the VS Code PWA) is the only option here.
You could also try stackblitz.com, they give you a console and have a live server built in, that probably fits your bill.
I don't think that is the case.
My PWA (Journalistic) had zero organic web traffic in the beginning and generated more than 10k installs organically from the PlayStore. And even now, with more love from Google, the PlayStore still generates more than 90% of the downloads for the app despite having a relatively low install count for a journaling app (it shows 10k, you can check it out here).
I think the more important metric is good ratings and positive user reviews. Also, the ranking for certain keywords is quite important for the number of downloads.
It's possible, but you have to keep this in mind:
There are other concerns and limitations around your idea, but if the storage or security is important, my recommendation is to opt for a native app.
Also, if your list of tasks needs to be real time (scheduling is close to execution and/or high chance of cancellations) you will need to build an interface indicating last sync timestamp and logic to 'demand' an update before starting the task if the timestamp is older than 'x'..
Here is a good starting point course for PWA:
https://www.udacity.com/course/offline-web-applications--ud899
Depends where you are hosting. Btw on localhost you don't need the HTTPS for a PWA forgot to mention that so you can test it out there. To get a free certificate you can use let's encrypt.
I am planning to do something similar. I built my first PWA some years back so I am aware of some of the challenges.
I would suggest you look at Firebase (https://firebase.google.com/) and publish your app to it.
Basically a PWA app has more in common with an android or IOS app then it does with a website bookmark, if the developer treats it that way.
https://web.dev/progressive-web-apps/
So for starters, a PWA centers on a file called a manifest, which tells the browser what icon to use, what permissions it should have, and what other details are available.
Next up is the ability for service workers (a piece of javascript that runs in the background) to store whole parts of the webpage offline. Or just tell the user they're offline, or include a maze if you're trivago. https://www.trivago.com/offline
In pretty much every OS but IOS you can also connect websites to notifications through service workers.
A regular bookmark is just a reference to a location on the internet. A PWA, when taken as more then just a fancy shortcut, also includes other bits of browser technology that puts it more on par with a mobile app.
Microsoft, Google, and Apple have added the ability to install PWA apps from their app stores. Although PWAs don't have as good support in IOS.
CouchDB?
use a server to store the data, use indexdb and service workers to sync the data as it changes. PouchDB can already sync to a remote server so it might fit your use case.
I use https://quasar.dev - for the kind apps we build at work it’s amazing!
It’s geared towards Vue but ships lots of Material Design styled components.
PWA support is baked in too.
Worth a look if you are into Vue and Material Design.
Depending on the interface and animations complexity I would recommend to look into Quasar or Ionic. The advantage of these options is that they have a lot of prebuild components and options that would help you to bootstrap the application and also learn how to create components on your own.
Not to discourage you, but one thing to keep in mind is that sooner or later you would need to store data somewhere which is mostly done via database, backend and APIs. That's where knowing HTML, CSS and JavaScript (regardless of Node.js) are not going to be enough and you may need to find someone to help you.
This depends on the permissions and settings in your Friend OS app. Right now, we do not use geolocation in the available app (https://play.google.com/store/apps/details?id=cloud.friendup.friendup&hl=en&gl=US). But as the platforms grow, we will add features requested by app developers.
Keep in mind, that in Friend OS - multiple Friend apps are running inside one Android / iOS "super"-app. And as such, we need to regulate access to features based on the user's preferences.
It should give you the same location accuracy as native, once the user grants permission. Check out Google Maps Go - it's a PWA that runs in Chrome but can be installed from the Play Store.
I managed to get this PWA as a TWA on the Google play store, it wasn't as easy as I hoped it would be.
https://play.google.com/store/apps/details?id=xyz.appmaker.qbbnwz
Well... it depends on how much hardware access you need, but I can give you an example of something you seems to be talking about, which is already working.
I wrote a PWA, and an Android wrapper for it (so in essence, the PWA gets loaded in a WebView in realtime, when you start the app from the play-store). If you are offline it still runs from a service-worker, so if your app does not need server processing, it will work 100% offline too.
Although it all works directly as PWA, the android wrapper needed some "JS-interfaces" - for file download, JS-messages, and so forth.
So now, when I update the app on my server, the PWA and the Android app get updated instantly, next time you run them (without having to update anything from the playstore) ;)
I have not tested iOS app, but if they have a WebView, it should work fine, as long as you don't need to run it offline (I think iOS still don't have Service Workers).
Android: https://play.google.com/store/apps/details?id=com.kinoseed.matchcolor