Earlier quoted context omitted.
Web Share Target API (manifest: share_target) - it allows a website to specify itself as a share target. Of course, it's not yet supported on iOS.
This is not a web standard. Google wrote the specification and only Google have implemented it. It’s an unofficial draft: > Editors: > Matt Giuca (Google Inc.) > Eric Willigers (Google Inc.) > Status of This Document > This specification was published by the Web Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track — https://w3c.github.io/web-share-target/level-2/ Firefox doesn’t im…
What PWA Can Do Today
151–160 of 285 posts
Re: What PWA Can Do Today
#152Earlier quoted context omitted.
PWAs are the next step in mobile Web, for most forms over data apps, it isn't really needed. When I came back to Web/Distributed Systems after my stint dealing with Windows desktop, all the applications I have been involved only had Web frontends, including for mobile devices, not Web views, the actual browser. They managed perfectly fine.
> PWAs are the next step in mobile Web For subscription app may be, but all ads revenue websites will reject it.
I reject them
I cannot tolerate apps with ads
Re: What PWA Can Do Today
#153The only thing holding me back from using PWA's right now is tabbed mode [1]. Browser tabs are so useful and having them open in new windows or in the system browser is a bad experience. Not sure why this is taking so long, there have been prototypes for years. Not like its even a security question just bringing over a UI that already exists in the browser. https://developer.chrome.com/docs/capabilities/tabbed-applic…
The PWA thing seems sick to me. Henry Ford listens to market research and rebuilds his car as a mechanized horse. For me, the UX is strictly worse in every way. (And I already knew how to put links to webpages on my home screens).
There does seem to be a browser display mode, but it's up to the app maker to decide for the user what mode the app will be in. Why?!
> Progressive Web Apps can run in various display modes determined by the display property in the web app manifest. Examples are fullscreen, standalone, minimal-ui, and browser.
It makes me so sad how much lesser a person a user of a PWA is. The utter lack of user agent, being cast to whatever is provided by the maker, is a horrifying loss. All to ape what felt to me like the descending losing old-guard technologies.
Re: What PWA Can Do Today
#154Re: What PWA Can Do Today
#155Re: What PWA Can Do Today
#156Earlier quoted context omitted.
Thanks for putting it in context, the Bluetooth API has been a big source of frustration in my exploration of PWAs. So many simple setup apps wouldn't need to be native. A cross platform Bluetooth API for the web would provide really easy PoC with MCUs.
Yes I really want random websites to have access to Bluetooth
The gatekeeping/FUD/wringing-of-pewrls over this seems absurd, cruel, and most of all arbitrary to me. Insubstantial naysaying.
Re: What PWA Can Do Today
#157Earlier quoted context omitted.
PWAs are the next step in mobile Web, for most forms over data apps, it isn't really needed. When I came back to Web/Distributed Systems after my stint dealing with Windows desktop, all the applications I have been involved only had Web frontends, including for mobile devices, not Web views, the actual browser. They managed perfectly fine.
> PWAs are the next step in mobile Web For subscription app may be, but all ads revenue websites will reject it.
Re: What PWA Can Do Today
#158How typical of PWAs that even a demonstration site, which should demonstrate the best that PWAs can be, has a glaring UX bug on iOS. Namely: if you swipe from the sides of the screen to go back/forward, you get a duplicate animation. If you swipe back from B to A, once the native (interactive) slide animation finishes, the page then jumps back to B and then does another (noninteractive) slide animation to A. Fixing t…
Re: What PWA Can Do Today
#159Re: What PWA Can Do Today
#160How typical of PWAs that even a demonstration site, which should demonstrate the best that PWAs can be, has a glaring UX bug on iOS. Namely: if you swipe from the sides of the screen to go back/forward, you get a duplicate animation. If you swipe back from B to A, once the native (interactive) slide animation finishes, the page then jumps back to B and then does another (noninteractive) slide animation to A. Fixing t…
Yes! And the visuals are horrific too, just look at that tabbar. If anything, it’s a showcase of just how hard it’s gonna be to build a good app this way.