There are plenty of choices, and everyone can pick what they like. I also mostly just use Jumble on desktop, haha.

But I don’t really see the points you listed as disadvantages of PWAs:

- Forced updates mean an early client can quickly fix bugs and ship features. You might be worried about β€œmalicious” updates, but does an APK really solve that? How many people actually review Amethyst’s source code, and even if they do, how many compile it themselves?

- Jumble is a purely static site and could even be deployed directly on nostr via https://nsite.run/ . If needed, I’m sure someone would mirror it, it’s open source after all. Isn’t that actually more decentralized than an APK?

- Depending on the browser means Jumble runs anywhere a browser exists. An APK, in contrast, depends on Android and doesn’t easily run elsewhere.

Reply to this note

Please Login to reply.

Discussion

Zapstore signing is something that’s better in apk’s. PWAs rely on SSL certs that live on CDN or server: easier to hack when the code itself is not signed.

It's easy to wrap browser apps with tauri btw. Iris is on Zapstore, and I might try my luck with play store and ios app store one day. Why not have both options. I've grown a bit weary of cloudflare.

That’s a good idea.

I’ve thought about packaging it with Tauri / Electron, but then I can’t resist bundling a local relay inside, haha. And that’s when I start procrastinating.

Please pack it. People like to install things.

The real security is in keeping your keys safe and not signing events blindly, haha. When I use Jumble, every event (except AUTH) asks for my consent before it’s signed. I know that with this configuration, many apps become almost unusable.

Yes, many apps assume that as soon they detect an extension the sign is immediate, and miserably fall with some sort of timeout if the user take some seconds to approve (or didn't approve at all).