[–] 4 points 6 months ago

Why is this called 2.0? PWA without offline is assumed to be 1.0?

I don't like them randomly defining and attributing version numbers to standards. These versions don't exist. And they don't even define them.

PWA and offline capability has been around for a while. PWA typically raises the question of offline capability. That's not a new thing or a new standard.

  • source
  • [–] 2 points 6 months ago

    While it might not work for everything, I have a number of sites that are used for field work that would benefit from these approaches. Things like dashboards an configuration tools.

    Arguably, the tools should be desktop apps, or something of the like, but the reality is that using PWAs in this way is easier for everyone (the developer, the distributor, the user).

  • source
  • [–] 2 points 7 months ago

    Given the nature of Steam and previous executed data extraction, I'm scared installing and running niche/indie games now. Windows lacks

    A unified GUI framework hasn't happened yet, not between OSes, nor really within each OS ecosystem. I'm not hopeful about leaps in native interoperability in that regard.

    Web tech interoperability is so established and widely used, packaging and running those natively seems much more viable than any hope for supposed native long term efforts.

    Not everything will be covered by web tech. But for many things, it's already viable, and exploring native integration of these web technologies is interesting.

  • source
  • parent
  • context
  • [–] 3 points 7 months ago

    Correct. The degree that a native app could invade your privacy on the desktop is insane. For mobile, thanks to sandboxing it has a much smaller surface but still annoying nonetheless when an app could just be a web. Especially if all they do is just a glorified form filing app.

  • source
  • parent
  • context
  • [–] 3 points 7 months ago (2 children)

    Mozillas vision of phone apps was this. It's one reason PWAs were made and part of why WASM is where it is. One of the largest barriers to adoption against it is that apps allow for tight control from the dev, not just technically, but also from a legal standpoint. For that reason I would rather have PWAs myself, a lot of apps actually suck and are just full of dark patterns.

  • source
  • parent
  • context
  • [–] 5 points 7 months ago (6 children)

    Now this puts a question for native platform. If web technology managed to get more and more approval to get native access like Web Bluetooth, should we move apps to the web instead? We have web authn as secure hardware backed secret storage. Personally, I like it if everything is not a native app.

    The other extreme is if the native platform provides the same interoperability and standard as web. Would you prefer every complex web to be a sandboxed native app instead? Say a youtube streaming desktop app.

  • source
  • [–] 4 points 7 months ago* (last edited 7 months ago) (2 children)

    Looks to me like it's mostly paywalled.

    Anyway, the maximalist web design trend that's popular there is really interesting. I like how low-techish it looks. But it is really hard to scan, especially when you're only sorta-kinda able to read the language anyway.

  • source
  • view more: ‹ prev next ›