3 ms·

Interesting, and congratulations on launching the site! How do you plan on growing and generating demand? I starting making exactly this back in 2018 but didn'

Interesting, and congratulations on launching the site! How do you plan on growing and generating demand? I starting making exactly this back in 2018 but didn't get people interested back then so I dropped it and let the domain expire, see the original (seems broken though): https://web.archive.org/web/20180901171627/http://web-app.store/ https://web.archive.org/web/20180901171627/http://web-app.st... It was my first time using a skeleton in CSS and using a Google Form as the way to submit a new app (with the spreadsheet as the database). I believe it was also my first PWA but I'm not 100% sure about that. While I learned a lot, some times I regret not having followed through, will keep an eye on https://progressiveapp.store/ https://progressiveapp.store/ to see how it goes.

mattpearl 7y ago
well I really just love PWA's and the freedom it brings to the developers and wanted to create a store to help show their potential. Appreciate it!
- aabbcc1241 7y ago
  PWA is definitely great for developers and users. But I often see users asking for native apps even when they're using PWA at hand. They say "It's more convenience to have app version".
  - julianwachholz 7y ago
    I'd argue that many people wouldn't know wether they were looking at a PWA or a native application written in a JS container format (like react-native). I can't think of a way that native apps are more convenient? With automatic updates it's even less convenient to have the updates go through the app store.
    - aabbcc1241 7y ago
      They may not distinct visually, but iPhone user without chrome can definitely tell. I totally agree with you, I developed a PWA and 'native app' which is mostly an webview of the same content. I often use the PWA version but it seems most (if not all) of my users are using the app version even when the app stores approve updates in a notifiable slower rate. My native app do used some native plugin, but those functions are not often used by the users. So I feel they just blindly ask for apps. Maybe they think native app loads faster than PWA? People don't want to wait for a SPA first-time loading but they won't blame the download and install time of native apps.
  - criddell 7y ago
    I don't think it's necessarily convenience. PWAs are loved by developers but they kind of suck for usrs. Native apps should use less battery, memory, and cpu. On a desktop machine, that might not be a big deal, but it is on mobile.
    - FridgeSeal 7y ago
      > Native apps are loved by developers but they kind of suck for usrs. Don’t you mean to say the opposite? Most proponents of PWA’s I see are devs claiming that writing native apps is too hard, but most users prefer native apps because of better integration and performance/efficiency.
      - criddell 7y ago
        Ha! I did mean the opposite. I made an edit.
julianwachholz 7y ago
I remember your site! I was planning on adding a service worker to my trivia game so I could eventually add it to your site but never got around to it!

mattpearl 7y ago

well I really just love PWA's and the freedom it brings to the developers and wanted to create a store to help show their potential. Appreciate it!

aabbcc1241 7y ago
PWA is definitely great for developers and users. But I often see users asking for native apps even when they're using PWA at hand. They say "It's more convenience to have app version".
- julianwachholz 7y ago
  I'd argue that many people wouldn't know wether they were looking at a PWA or a native application written in a JS container format (like react-native). I can't think of a way that native apps are more convenient? With automatic updates it's even less convenient to have the updates go through the app store.
  - aabbcc1241 7y ago
    They may not distinct visually, but iPhone user without chrome can definitely tell. I totally agree with you, I developed a PWA and 'native app' which is mostly an webview of the same content. I often use the PWA version but it seems most (if not all) of my users are using the app version even when the app stores approve updates in a notifiable slower rate. My native app do used some native plugin, but those functions are not often used by the users. So I feel they just blindly ask for apps. Maybe they think native app loads faster than PWA? People don't want to wait for a SPA first-time loading but they won't blame the download and install time of native apps.
- criddell 7y ago
  I don't think it's necessarily convenience. PWAs are loved by developers but they kind of suck for usrs. Native apps should use less battery, memory, and cpu. On a desktop machine, that might not be a big deal, but it is on mobile.
  - FridgeSeal 7y ago
    > Native apps are loved by developers but they kind of suck for usrs. Don’t you mean to say the opposite? Most proponents of PWA’s I see are devs claiming that writing native apps is too hard, but most users prefer native apps because of better integration and performance/efficiency.
    - criddell 7y ago
      Ha! I did mean the opposite. I made an edit.

julianwachholz 7y ago

I remember your site! I was planning on adding a service worker to my trivia game so I could eventually add it to your site but never got around to it!