The mobile market has a clear preference for apps over webapps.

I love webapps and they have a lot of positives but few devs stop and reflect on what the market is conveying.

I noted a few weeks ago:

PWAs are an effective way of distributing applications permissionlessly, especially on iOS, but there's a few drawbacks:

- Hard to install: the fact that you have multiple steps that need explanation (go to the hamburger menu, tap on install, but on iOS use Share...). As insignificant as this sounds, it's a major UX hurdle for users and why I think PWAs are not more widespread. Apple and Google know this very well.

- Harder to discover: though not needing an app store is an upside, it hurts discoverability, especially on app stores with a social layer like Zapstore

- Reliance on domain names: Not a huge problem but definitely not as sovereign as private keys

- Hard to verify releases: since you pull data and UI from a website, it's unclear when you have upgraded, impractical to sign and next to impossible to audit a particular release. Websites typically perform lots of deployments every day

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug why am I getting a Content Warning on this note on amethyst, any idea?

Same lol.

Did you fall under Amethysts' Authoritarianism too?

I have no idea! What are the rules for hiding content?

I think it's something like 5 identical posts out of the past 100, including replies.

Theres a content warning in the event tag. Did you use amethyst to write the event?

Yes. Why would Amethyst label it like that? Used the word "harder" too much?

You probably pressed the content warning button and didnt see it

One reason I hate Amethyst is that the little icons and shit are low contrast / hard to see unless you turn your phone screen's brightness WAY up. No thanks lol

You probably just accidentally hit the "sensitive" button while writing your post.

Or retarded users report their marketing as spam

Pretty sure that has zero affect. Also, I can verify that Zapstore has not been flagged.

By the way, sorry for not noticing earlier. Congratulations on all of your "hateful speech" flags. I'm proud of you.

No need for conspiracy theories. I pressed the wrong button.

I am not saying any conspiracy theories. For example, I am censored on Amethyst. Many users have told me they cant see my posts until they remove security filters. The developer even admitted it.

Ya, 'cause you spam shit. Don't get me wrong, I still follow you, but that doesn't mean you don't post spam sometimes.

Called marketing

It is possible to market something without spamming it. You can also do all your "marketing" on a separate account if you are worried about your shitposting account being censored.

I advertise three times a day a service I provide for Nostr

Thats too much for you?

For me? I think I was clear that I don't give a shit.

But even making identical posts just once a day wouldn't exactly be authentic and candid like most people's posts are.

TBH, I found your analysis awfully disturbing and offensive

Tell me more

I was just making a lame joke about the truth of your statements being offensive. That's all. I'll be here all week

I was a big fan of PWAs but I think the biggest downside is the last point you mentioned, not being able to verify or control which build you are on. The other points are really small in comparison to this one so ultimately I think PWAs have their place for very simple applications but ultimately native FOSS apps are the way to go for complex apps

Do you also include webapps in Zapstore?

Eventually yes

It has a label to make that warning. This is usually used for NSFW content. It's the seventh button on the new post page.

Ugh ok, thanks! I did not notice at all.

I hate PWO's.

In regards to discoverability, if you use PWA's (I can see the irony, lol) like Store this issue completely goes away.

Saw in another reply that you plan to add PWA support, so just take from their method and adapt as necessary.

https://store.app

That's right.

They are still hard to install for the average user which is the major roadblock.

If only there was a "prompt install" JS API in the browser

I know for PWA's on Chromium-based browsers (at least on Android) you'll either get a bottom bar with an app store-like listing (most commonly seen on sites like Xitter) or a prompt right below the omnibox with an install prompt.

It's inconsistent though, since some sites and services with PWA support that don't have the manifest included somewhere in their code won't have either show up. And don't even get me started on iOS' "support" outside of the EU.

What I ran into, in addition to the points you mentioned, working on software for mobile and moving from a webapp to a native client:

• I do not want to be a sysadmin

• Frontend development is a hellscape and it is mainly JavaScript frameworks