10 ms·
What PWA Can Do Today
- PaulHoule 3y agoSpam you with spam spamifications. Clutter your mobile device device with more twisty little icons that all look look the same. Attempt to store content with an unreliable storage service. Move on folks, nothing more to see here. PWAs are just another Google side project, talking about them in 2024 is like still being hung up on a chat app Google killed years ago or being that guy who did his whole house up in Material Design.
- exo-pla-net 3y agoWhatever their merits, PWAs are not a Google side project. The idea was first proposed by Steve Jobs and Microsoft is excited about it, too [1]. In other words, all the big players are in on it. It's a good idea and frankly superior to the current Store+PhoneApp approach to making stateful apps that can run on mobile devices. Contributing helps. Being sour, not so much. [1] https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/ https://learn.microsoft.com/en-us/microsoft-edge/progressive...
- JimDabell 3y agoSome of the functionality listed on this site is not part of the web platform, but rather Blink-only APIs Google implemented unilaterally that have been explicitly rejected by Mozilla and Apple.
- postalrat 3y agoApple wants to keep in control with the app store. PWAs threaten that control. So much so apple doesn't allow other browsers.
- JimDabell 3y agoThat argument would work if it were only Apple rejecting them. Mozilla rejects them on the same grounds.
- postalrat 3y agoMozilla rejects stuff like webusb while apple is blocking add to home screen, push notifications, etc. Stuff that is needed to replace many app store apps. Firefox supports both add to home screen and push notifications.
- JimDabell 3y agoPWAs already support push notifications and add to home screen on iOS. Or by “add to home screen”, are you specifically referring to BeforeInstallPromptEvent / prompt()? That isn’t a web standard. It’s something Google alone have implemented, it’s a Chrome-only feature. Firefox hasn’t implemented it either. > Status of This Document > This specification was published by the Web Platform Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. https://wicg.github.io/manifest-incubations/ https://wicg.github.io/manifest-incubations/
- tgv 3y agoWhile Google wants as much access to your phone as it can get. Why would that be?
- postalrat 3y agoWhat's with the FUD. What else besides PWAs promise to free everyone from app store rent and anticompetitive policies? PWAs would also open the doors to new mobile OSs beyond Google or apple control.
- PaulHoule 3y agoI think web apps are great. The average brand has no business making a mobile app when an web application would do. It's the "progressive" part I have a problem with. Web apps revolutionized our idea of what an application can do; everything in PWA makes web applications worse, not better. Just to take a simple example, when I want to visit Hacker news I just type n in the address bar of my iPad and click on the auto-suggest result and I am there. If I had an app for it, it would compete with all the other apps that have a burnt umber orange icon or that have an "H", an "N" or a "Y" as their own logo. (McDonald's might be the only brand that can pull that off) If I had an app for that I'd also be installing lots of other apps and have 4 or 5 pages of them to scroll through. If anything, brands should be asking for ways to make installed apps as easy to find as uninstalled web pages are. (Note all the things I complained about originally except the lack of a reliable storage facility, are problems with apps. What makes it a 'side project' is that PWA advocates keep denying that "it just doesn't work" and then act incredulous that nobody wants to waste time with them.) If anything, most app authors should just quit drinking the Kool-Aid and just make plain ordinary web applications without any of the PWA power-downs. It's like playing a Mario game and finding some mushroom that makes you smaller without any benefit (like being able to go in some hole.)
- janci 3y agoWhat are you even talking about? PWAs are an option on top of an ordinary web app. I guess all PWAs can be opened in the browser without "installing" them. Also "competing with all other apps" is the fault of OS built-in search. Nothing to do with PWA
- palata 3y ago> What else besides PWAs promise to free everyone from app store rent and anticompetitive policies? I don't know... laws? > PWAs would also open the doors to new mobile OSs beyond Google or apple control. Or force everyone into ChromeOS once and for all.
- cranberryturkey 3y agofirefox killed of pwas
- ricardobeat 3y agoHow? Did it even reach significant mobile share at any point?
- doodlesdev 3y agoAlso, Firefox on Android still supports PWAs, it was only removed on the desktop.
- riordan 3y agoIt’s good to hear that PWAs are still on Firefox Android, even though they’re out of Desktop. From my [fairly-out-of-the-loop-for-the-past-few-years] vantage point, Mozilla’s been a lot less invested in the PWA ecosystem since they abandoned their Firefox Phone / Boot2Gecko initiative, which was intended to create a middle tier between the expensive smartphones of the early 2010’s and ubiquitous and cheap feature phones (flip phones, classic Nokia candy bars), and expand access to the web across the world with it. All the apps were PWAs, which made it simple to build out. Eventually Mozilla stopped the project, but KaiOS became a commercial implementation and it still runs on a fair number of feature phones to this day. But without that pressure for PWA support in Firefox as a critical mobile feature, it was largely serving as an expensive bookmark launcher in the Firefox code base so that folks could alt-tab to the small number of sites that supported it on their desktops. Not a noble end for Mozilla’s support for what should have been / could have been an incredible leverage point for the web ecosystem and open development.
- mnau 3y agoHow so? FF has minimal market share, most of it on desktops.
- starfox64_ 3y agoIt's kinda sad that the website doesn't prominently display which features have "universal" support across iOS and Android. The whole point of PWAs is to provide cross platforms apps so if a feature isn't available on all/most platforms, I don't think it's fair to say that it's really usable at all in your PWA.
- worksonmine 3y agoKnowing what will come and be available is also a valid use case. If you want to know about support every feature has links to MDN and caniuse, just check there. The web isn't as simple as comparing iOS/Android. For example Firefox on desktop isn't Firefox on Android and Firefox on iOS is just Safari. The web is a complex ecosystem.
- throwawaymaths 3y agoDepends. What if your PWA is an in-house app for operators in your company? They all have an issued device with MDM, one or a few skus, all apple (or all Google). I think most in-house devs would rather not deal with the app store or the vagaries of getting the MDM side loading pathway working
- pjmlp 3y agoPWAs 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.
- phartenfeller 3y agoI'm wondering why there isn't a calendar API available. I wanted to create a simple PWA to track upcoming events for my favorite sports. It would be convenient to sync these events with my phone's calendar. Currently, downloading .ical files isn't a sufficient solution because it requires accepting prompts for each event and doesn't allow for modifications (as I am aware).
- wombarly 3y agoMost calendars have the option for you to subscribe to an ical by pasting in the web address. Which they will then keep in sync.
- lawgimenez 3y agoI track sport events with Fantastical’s interesting calendars.
- graphe 3y agoYou're looking for SOGo. https://en.m.wikipedia.org/wiki/SOGo https://en.m.wikipedia.org/wiki/SOGo
- augustohp 3y agoI might be missing something here but thet "Calendar API" exists for a long time: CalDav. You can have .ical for a whole Calendar, not only an (offline) event. The calendar can be synced with new events, through CalDav, when they are added to the calendar you shared. You would still have to accept the prompt once but that is it.
- jallasprit 3y agoCouldnt add it to homescreen on ios firefox because the option in the share menu wasn’t there
- JimDabell 3y agoThis should have big warnings on it. Some of these are not web standards; they are features implemented unilaterally by Google in Blink that have been explicitly rejected by both Mozilla and Apple on privacy and security grounds. Take Web Bluetooth, for example: Mozilla: > This model is unsustainable and presents a significant risk to users and their devices. — https://mozilla.github.io/standards-positions/#web-bluetooth https://mozilla.github.io/standards-positions/#web-bluetooth Apple: > Here are some examples of features we have decided to not yet implement due to fingerprinting, security, and other concerns, and where we do not yet see a path to resolving those concerns — https://webkit.org/tracking-prevention/ https://webkit.org/tracking-prevention/ This is Microsoft’s Embrace, Extend, and Extinguish bullshit applied to the web platform by Google. Google keeps implementing these things despite all other major rendering engines rejecting them, convinces people that they are part of the web, resulting in sites like this, then people start asking why Firefox and Safari are “missing functionality”. These are not part of the web platform, they are Google APIs that have been explicitly rejected.
- sberder 3y agoThanks 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.
- stephenr 3y agoAnd a massive exploit capability for malware.
- deleted 3y ago[deleted]
- scarface_74 3y agoYes I really want random websites to have access to Bluetooth
- fidotron 3y agoOn a purely technical level the main thing stopping PWA adoption is the JS front end universe being addicted to front end frameworks which destroy the UX of websites and PWAs, but there is a key value add with app stores which PWAs will never have: trust, and much as the Apple haters will hate it it is much stronger on the iOS App Store because of the very things they hate about it. Chrome, for all of Google's sins, is a modern miracle of software engineering. Safari is nothing like as far off as people make out either.
- jwells89 3y agoThe front end framework mess is just a symptom of the actual problem, which is that the building blocks provided by browsers are too crude/limited to allow for consistent quality, and so Rube Goldberg machine frameworks arise to try to paper it all over. I think browsers can be a good platform but for that to happen they need to be a bit more batteries-included, with built in APIs for UI and other essentials that rival those of desktop platforms so crazy frameworks are rendered unnecessary.
- fidotron 3y agoHonestly, I believe you have this backwards; the problem with browsers is they are too flexible and complicated. If you delivered a consistent MVC framework in the style of the classic NeXT APIs the major complaint would be the imposed look and feel, which from the point-of-view of a user is a feature, but for whatever reason people are drawn like moths to a flame towards that which is at the edge of reasonably possible and so devs and designers will forever be pushing at the limits until this state of chaos recurs.
- jwells89 3y agoIt depends on what part of browsers are being spoken about. They’re plenty flexible and capable for the case of traditional pages and server-side apps, but it’s a totally different story for interactive widgets and especially full blown SPA’s. For example, browsers don’t furnish a tableview/datagrid or even a basic single column recycler view, meaning one has to find a third party library to do those things that’s still maintained, fits into your stack, and has holes in functionality that are tolerable for the use case in question, or if none meet those criteria write it themselves. The result is a million reimplementations of the same thing nearly all of which have major shortcomings (some of which are present only because they aren’t implemented as a native browser control). I totally get that styling is a pivotal part of web apps but I think that can be maintained without requiring devs to build castles from grains of sand instead of giving them more appropriate building materials to use.
- SigmundA 3y agoThe 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-application-mode https://developer.chrome.com/docs/capabilities/tabbed-applic...
- jauntywundrkind 3y agoTabbed isnt enough for me. I don't want an app. I want a website. I want my user-agent! My user agent is what I know, affords me URLs & extensions and a powerful UI with lots of options. 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.
- jauntywundrkind 3y agoI assume I'm being down voted by pro-native people for calling their preferred tech descending losing old-guard technologies. Does anyone actually have any comments or reactions to what I was actually arguing about? PWAs being such brutal downgrade over what the web browser offers seems glaringly obvious to me; I'm shocked there's not more outcry. If people actually feel otherwise, please leave some arguments out in support of blowing away the user agent. This feels like it always has been the nexus of power where the web gets consistent enriching capabilities and affordances. It's what has made the web powerful & better, rather than every user being cast naked &bat the mercies into whatever app a company decides to cook up. There's a submission right now on The Eight Golden Rules of Interface Design & the browser alone satisfies 6 or 7 of these, by my judgement, whereas native & PWA apps require the app to carefully construct it's own paradigm that can fully meet these user needs. The user agent is a helpful baseline, and it seems mad that PWAs throw it away to me. https://news.ycombinator.com/item?id=38916663 https://news.ycombinator.com/item?id=38916663 https://www.cs.umd.edu/~ben/goldenrules.html https://www.cs.umd.edu/~ben/goldenrules.html If people think PWAs offer anything or make any sense versus the web browser, I'd love to hear why. Tabbed design was sooo late relatively to emerge in PWA space, and it feels like just one of a million affordances that are going to be half baked recreations of what we already had in the browser. How is being an app in an OS better than being a tab in a much more powerful & competent & featureful user-agent?
- SPBS 3y agoCall me back when PWAs can be registered as share targets on iOS (i.e. it appears as an app on the share sheet when you click "share" on a web page). I really want the ability to bookmark sites I browse on my phone and save it to a self-hosted web application.
- taknil 3y agothis is foreseen to come eventually, the APIs are there https://web.dev/articles/web-share?hl=en https://web.dev/articles/web-share?hl=en
- wojciechpolak 3y agoWeb 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.
- JimDabell 3y agoThis 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/ https://w3c.github.io/web-share-target/level-2/ Firefox doesn’t implement it either: https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 Apple raised a concern about spoofing which seems to have gone unaddressed by the spec authors in over a year: https://github.com/w3c/web-share-target/issues/109 https://github.com/w3c/web-share-target/issues/109 This may yet turn into a web standard given more work, but please don’t hold up a Google spec. implemented only by Google as if it were a part of the web platform that Apple are late in implementing.
- bensecure 3y agoThe only relevant browsers on mobile are google's and apple's, and (modern) web standards are created by enough popular browsers implementing them. Literally all it would take for this to be a reliable web standard would be apple choosing to implement it.
- smokeydoe 3y agoiOS PWA notifications are a pain in the ass to set up without using something like firebase, but they are so nice to have finally.
- kevincox 3y agoWhy are they a pain? Do they have extra requirements over the standard Web Push API?
- dannymoerkerke 3y agoThey don’t
- esskay 3y agoSlightly misleading domain when a large number of those arent actually supported in major browsers, certainly not at enough consistency.
- bob1029 3y agoWe push PWAs to iPads & Surface Go devices via Microsoft InTune for some of our clients today. This path started out very nightmarish (circa 2020) but it's going much smoother today. One of our customers actually came back to us with a slightly improved process based upon the one we gave them. They switched from iPad to Surface Go and used some extra endpoint management to make the PWA experience into a sort of kiosk mode. The #1 constraint for us is the quality of the environment-facing camera and the level of access we have to its capabilities via the browser. iOS/Safari started out extremely weak on this but is quite good today. I can get a solid 2k environment scan at 30fps from the rear facing iPad camera in Safari today. Things like 2D barcode scan and document capture are 100% feasible now. These items used to make us extremely nervous on product demos but we don't worry anymore. We almost capitulated and went back to native iOS apps because of the camera issues, but the pain of maintaining a native build chain when you are otherwise a 100% Microsoft shop (with barely 3 developers) was pushing back hard too. We were signing enterprise IPAs for all of our clients for half a decade before we switched to web/PWA. I will never go back to native apps. I'll find a different career path and hobbies if the web goes away. I don't have a clean answer for B2C other than... I use HN and Twitter in Safari and I don't even process that it's not a native app. Neither of these web properties had to spend a single second worrying about a native app to acquire my business.
- thekingshorses 3y ago> 2D barcode Which JS library do you use? I couldn't find a single library that can reliably scan PDF417 barcodes.
- martinald 3y agoI assume the built in one that OP has? https://developer.mozilla.org/en-US/docs/Web/API/Barcode_Detection_API https://developer.mozilla.org/en-US/docs/Web/API/Barcode_Det...
- sevenf0ur 3y agoSafari doesn't support that API whatsoever so a third party JS library is really your only option. The landscape of open source barcode detection libraries is bleak at the moment.
- asveikau 3y agoA GitHub repo with just a bug tracker and no source code is kind of lame. If they really want to promote PWA they should have full source on there.
- wackget 3y agoThey don't want to promote PWAs. They want to promote their own business.
- fudged71 3y agoI see there are a few features not available on my phone (iPhone 15 Pro Max). If possible it would be great if the feature icons could turn grey if they aren’t supported on the current device
- exabrial 3y agoMy estimate is there are 5,000-10,000 really poor PWA/SPA/etc for every actual good PWA/SPA. Going to a website and it loads some massive chunk of overengineered javascript when all I need to do is display one piece of text is infuriating.
- palata 3y agoI think we have to get used to it, it's the new engineering way. "I see potential profit with blockchain, let's rush and do whatever quick project I can imagine with blockchain". "I see potential with AI, let's rush and do the same with AI". It's not important to make a good product anymore: you need to be the first or the luckiest. Good products don't win because they are drowned in all the crap. And AI will soon make it infinitely easier to generate more crap.
- steve1977 3y agoPlease don’t call this engineering.
- sccxy 3y agoGatekeeping is strong here. Most apps do not need to be made by 10x developers who code in assembly.
- hanselot 3y agoWill wait for the next version of the website: whatpwacandosafely.never
- 2024user 3y agoI dislike that when you install a PWA it is browser specific. For example, if I use Chrome, the installed app will only open in Chrome. Use Firefox on Android and it overlays a Firefox icon on the installed app icon.
- self_awareness 3y ago> A PWA is much smaller than a native app. Your users no longer need to install tens of megabytes of code. I don't think we have the same definition what a "native app" means.
- nprateem 3y agoA big limitation is that pwabuilder doesn't support push notifications on ios
- palata 3y agoPWAs to me sound like "we want everyone to use the same OS (in this case something like ChromeOS), because that's more productive for us". I get that Google pushes for PWAs because that's how they conquer the OS world. But why do individuals push for that? Because they don't know anything other than webtech and don't want to learn? Have a look at Kotlin and Swift guys, it's kinda cool!
- marvinblum 3y ago> But why do individuals push for that? Because we don't have the resources to build a native app for every OS out there.
- palata 3y agoAre you using Windows? I am happy that the people who contributed Linux/BSD/Android/iOS did not have your mentality, otherwise I would be forced to use Windows everywhere.
- marvinblum 3y agoI'm on Fedora. Of course, there has to be a native UI, but I'm running a two-person company for example. How on earth are we supposed to manage three or more platforms (browser, Android, iOS)? We're not lazy but limited by our mortality. > Because they don't know anything other than webtech and don't want to learn?
- palata 3y ago> How on earth are we supposed to manage three or more platforms (browser, Android, iOS)? Are you sure you need three or more platforms? In my experience, when I ask small companies what they need, they say "everything". If I listen to them, they even need to run on a Gameboy. Then most startups fail, so apparently the problem was not the number of platforms. It feels like many times, selecting the platforms may be fine.
- 3y ago
- mvkel 3y agoAs soon as I tapped into this site, the browser's back button got hijacked and half of the features don't work. This is why (imo) PWAs should not try to replicate native app functionality, but instead recognize the web for what it is and play to its strengths.
- heax 3y agoThat it can break my back button is also what i took away from this before closing the tab and reopeing hackernews.
- deleted 3y ago[deleted]
- doublerabbit 3y ago> As soon as I tapped into this site, the browser's back button got hijacked and half of the features don't work. Sounds like common SPA application features to me.
- RomanPushkin 3y agoIs there such a thing as _live_ geolocation?
- sccxy 3y agoGeolocation API has "watchPosition", so it sends updates as often OS/browser decides. Was very unreliable in iOS, but is much better now.
- magnat 3y agoDoesn't work with JavaScript disabled.
- zamadatix 3y agoThis is an example showcase and PWAs require JavaScript to register the service workers for these features (as well as to operate them of course).
- comex 3y agoHow 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 this would be as simple as disabling the page's slide animation, but whoever made this site didn't notice or didn't bother. Apple does have some blame here. Disabling the page's slide animation wouldn't be a perfect solution since it wouldn't distinguish slide gestures from other ways to go back/forward (which ideally would still show an animation), like using the browser's back/forward buttons if accessing the site in a browser rather than as an app, or using a keyboard shortcut with an external keyboard. I don't think it's possible to easily detect which kind of gesture triggered navigation (in order to conditionally show the animation). Another option would be to disable the native slide gesture entirely in favor of a fully JS-based one. In the past it wasn't even possible to disable it, but that has been fixed for years now [1]. However, it's hard to exactly replicate the native behavior. Ideally there would be a more purpose-built interface to detect and customize the native swipe gesture. [1] https://pqina.nl/blog/blocking-navigation-gestures-on-ios-13-4/ https://pqina.nl/blog/blocking-navigation-gestures-on-ios-13...
- andreyvit 3y agoYes! 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.
- bbor 3y agoIs there anything about native apps or conventional websites/apps that would improve the visuals?
- FridgeSeal 3y agoNative widgets and UI elements, native navigation functionality. Web apps get worse the more they try and pretend to be native apps and implement things like their own scrolling, or their own back/forwards navigation.
- debacle 3y agoWhoever made this, this is incredible, thank you.
- Tepix 3y agoSeveral of the features in this demo app are broken (not just not implemented on iOS 17). That's how Apple likes it, i guess. On the other hand i have been using the Eclipse Emulator PWA https://eclipseemu.me/ https://eclipseemu.me/ on iOS for a few days and it works really well! The only issue i've had so far is choppy sound when emulating SNES.
- mvdtnz 3y agoI tried two of the features at random (face detection and vibration). Face detection told me my device wasn't supported, and vibration just straight up didn't work. Then I tried to back out of the website and it wouldn't let me. I'm on Android Firefox.
- account-5 3y agoI thought it was just me because I'm using uBlock. But even with the site first party scripts and line allowed it didn't work.
- majesticmerc 3y agoSame experience for me on Android Firefox. Couldn't return to HN via the back button, and most of the features were either "not supported" or just didn't work (e.g. Vibration) Seems that either the author is only working in Chrome (which is probably reasonable for a prototype or whatever) or Firefox is lacking many of these features.
- matt-tingen 3y agoUnfortunately, feature detection indicates that Firefox on Android supports vibration, but it doesn't currently work. https://bugzilla.mozilla.org/show_bug.cgi?id=1653318 https://bugzilla.mozilla.org/show_bug.cgi?id=1653318
- mvdtnz 3y agoPar for the course on Firefox I'm afraid. Every time I give it a chance it lets me down.
- TulliusCicero 3y agoThis is what happens for a lot of "this is just as good!" type features in any domain. Many advocates will tell you the thing is just as good, or at least more than good enough, and will deliberately avoid telling you about the many pitfalls and not-so-edge cases that they are very much aware of.
- lordofmoria 3y agoThings PWAs can't do: 1. On mobile, access full-definition camera/video as part of MediaDeviceCapture. There are new javascript APIs for this, but they're only partialy supported (the name of the new escapes me)
- turtlebits 3y agoI'm working on a minimal music player for Android that just plays from a directory on device. Can I do this with a PWA? I just tried the File System Acecss API -> Open directory but it did nothing.
- nolist_policy 3y agoFirefox doesn't support the File System API btw.
- judah 3y agoI have a music player PWA published on Android[0]. It works pretty good, my users are happy (rated 4.5 stars), and I haven't encountered any significant issues with it. For the file system access API, only the origin private file system is enabled on Android[1]. IMO, the file system access APIs are still a bit immature. [0]: https://play.google.com/store/apps/details?id=com.messianicradio https://play.google.com/store/apps/details?id=com.messianicr... [1]: https://caniuse.com/native-filesystem-api https://caniuse.com/native-filesystem-api
- account-5 3y agoI'm still glad I invested time in flutter for a cross platform framework.
- rock_artist 3y agoI really love how PWA goes. But one aspect for some use cases is monetizing. How can you “sell” PWA or have subscription for ad removal?
- judah 3y agoFor in-app purchases of PWAs in app Stores, you can use the Digital Goods API[0]. It works for Google Play and Microsoft Store. For non-free apps, one thing I've seen is app Stores launch the PWA with some flags indicating it was launched from the Store. If these flags are not present, the app is being launched via direct URL, in which case the app server can give a not authorized response. [0]: https://developer.chrome.com/docs/android/trusted-web-activity/receive-payments-play-billing/ https://developer.chrome.com/docs/android/trusted-web-activi...
- mcculley 3y agoThis page was the first time I had heard of the Contact Picker API. I tried to select the text to google it and this page has somehow disabled select/copy/paste of text. This is an ironic way to show that the web is just as capable/incapable as native apps.
- dannymoerkerke 3y agoI’m perfectly able to select the text.
- mcculley 3y agoI tried on Safari and Chrome. Maybe I need to install a special browser to use that web page. I wonder if they make an app.
- dannymoerkerke 3y agoJust tap and hold, works fine for me on iOS and Android
- mcculley 3y agoI see that it works fine for me also on mobile. Somehow they have managed to neuter the desktop experience. A perfect demonstration of PWA today.
- dannymoerkerke 3y agoDesktop works as well
- JimDabell 3y agoThe website applies -webkit-user-select: none to everything in the feature grid. The website author has intentionally disabled this functionality.
- Alifatisk 3y agoMan, the amount of ux bugs really describes the state of this. Is this the best experience we can give users through pwa?
- dannymoerkerke 3y agoWhat UX bugs specifically?
- Alifatisk 3y agoWhen swiping to navigate back, it stutters. There is a nested scroll view, sometimes when I scroll up / down, the bottom navigation bar follows with me.
- deleted 3y ago[deleted]
- synergy20 3y agothe elephant in the room is the lack of support from Apple, by this alone, its apps store should be legally challenged, before that happens, it's hard to sell PWA, which is great on a tech standpoint.
- Andrex 3y agoIt's rumored Apple may finally allow outside browser engines due to pressure from the EU (also behind the USB-C switch). https://9to5mac.com/2022/12/13/apple-mulls-opening-browser-engine-nfc-and-more-to-third-party-apps/ https://9to5mac.com/2022/12/13/apple-mulls-opening-browser-e... I very much hope it's true.
- judah 3y agoIt's not a rumor, it's reality: https://infrequently.org/2024/01/the-web-is-the-app-store/ https://infrequently.org/2024/01/the-web-is-the-app-store/ > "First, browser engine choice should become a reality on iOS in the EU in 2024, thanks to the plain language of the DMA. Apple will, of course, attempt to delay the entry of competing browsers through as-yet-unknown strategies, but the clock is ticking. Once browsers can enable capable web apps with easier distribution, the logic of the app store loses a bit of its lustre."
- tech234a 3y agoBlink can now be compiled for iOS, but without JIT or WASM: https://chromium.googlesource.com/chromium/src/+/main/docs/ios/build_instructions.md#Building-Blink-for-iOS https://chromium.googlesource.com/chromium/src/+/main/docs/i... https://bugs.chromium.org/p/chromium/issues/detail?id=1411704 https://bugs.chromium.org/p/chromium/issues/detail?id=141170...
- wbharding 3y agoSure would be nice if Firefox desktop would join the browsers that support PWAs. We build an app that has been PWA-first, but it is unfortunate that this generally requires users to have a Chrome instance running. Would much rather point people to Firefox, and it seems like it would be to their advantage to give apps a reason to recommend FF, if they built a smoother PWA integration than Chrome.
- ctoth 3y agoMozilla's removal of SSB support (single-site browser[0]) which is the key missing piece here is completely mystifying. I reckon that CEO salary has to come from somewhere though. [0]: https://www.reddit.com/r/firefox/comments/uwojh7/why_did_firefox_kill_pwa_support/ https://www.reddit.com/r/firefox/comments/uwojh7/why_did_fir...
- taway789aaa6 3y agoAgreed. On Firefox, if I navigate to the main page I can scroll and look at all the items. If I go to a sub-page, then back to the main page, I can no-longer scroll to see all of the "supported" features. :/
- tacone 3y agoI really wish they would do that.
- donmcronald 3y agoFirefox on Android is worse experience than Chrome too, at least for this app. The app is harder to install (no prompt), the icon looks worse, and the icon has a Firefox badge on it. I wonder if that's down to config for the PWA or a Firefox shortcoming. Anyone know?
- amadeuspagel 3y ago> and the icon has a Firefox badge on it This is something enforced by android. If every app was able to pin apps to the homescreen without such a badge, phishing would be too easy ... add something that looks like a bank app to the homescreen, get people to type in their password ... It's not fair, since that's not true for chrome, but there's no obvious solution, other then I guess having some sort of "super trustworthy" status for a few other browsers like firefox.
- FridgeSeal 3y agoIf this site is supposed to be a good demo of what they’re capable of, it’s failing pretty hard for me. - Takes ages to finish loading - huge number of features/functionality I don’t want a website to have over my phone/desktop - navigation is broken: swiping back causes some double-navigation stutter. - history is broken: attempting to navigate back to HN loads the same page again and again with no content change a stack of times, before I can finally escape.
- Lornedon 3y agoI understood this as a showcase of the features that PWAs can use, and I think it does a pretty good job at that. Do I understand your second point correctly? The feature demo is failing at being a feature demo because it demoes some features that you don't like?
- FridgeSeal 3y agoIf you demoed a car, whose feature set included “often opening the glove box into your shins” and “texting inappropriate things to your ex”, you’d be pretty leery of using it. If random people kept going on about how much they love this car, and the ex-texting features were so good, that they hoped to upgrade them into “actively calling your ex” you’d be a bit leery of what they were talking about. Every time someone talks about “how great PWA’s are” and how much better they’ll be after just some more features, I just hear “more stuff for advertisers to abuse”, “more things for half-assed devs to drain my battery and network with” and “more ways to have shittier experiences, slower” the less I’m interested in them. More concretely, it’s a feature demo that doesn’t work (see navigation) for features I consider anti-features.
- Lornedon 3y agoIf there was a car with those features and someone sold it to me without talking about them, I would be pretty angry. I think you're shooting the messenger here.
- benrutter 3y agoThis blows me away! I did a tiny bit of prototyping a year or so ago with an app for react native that required text to speech. Maybe I'm just a little slow with things but alongside janky styling I found it insanely difficult to implement any kind of offline native text to speech (I.e. not just sending sound files over an api call to anither api). Seeing that it (and lots of other things) are now implementable with PWAs fills me with excitement that "write once, run on iOS/android" might be becoming a real option for apps.
- wg0 3y agoJust wondering why mobile platform gate keepers, even Google would allow PWAs which will erode the value of their platform.
- mdhb 3y agoBecause holding customers hostage is a shit strategy? That and the fact that there is a large legal aspect to all of this largely led by the EU that seeks to prevent that kind of anticompetitive behaviour.
- wg0 3y agoI of course was aware of PWAs but didn't know that so much is possible just with the Web APIs now that only but maybe some highly specialized apps would need native apps which are difficult to develop and are subject to an approval process on top. Ironically, Apple os is going in the reverse direction it seems as Safari has not much good PWA story.
- Andrex 3y agoGoogle makes more money from the Web platform than the Android platform.
- magicseth 3y agoWe built hellowonder.ai as a PWA first, and it was almost amazing! But we use voice input, and ios would pop up the microphone permission repeatedly after a few minutes, even if it had been approved recently. I couldn't figure out how to keep the microphone permission! So frustrating to be soooo close, and then need to build an iOS app.
- maxglute 3y agoPretty buggy for me. Wonder if better connectivity will lead to remote streaming apps and skip this mess altogether.
- deathanatos 3y agoIs this satire? I'm not sure what about this is supposed to be a convincing argument for PWA? Even the text seems wrong? The prose seems to indicate it is installable even outside of mobile … but I have no idea. I'd've expected one of those popup "this site wants…" boxes, but nope? I also sort of thought PWAs were supposed to be responsive in their UI, adjusting to more/less real estate, but this is just the same UI at any size?
- hoten 3y agoWhy does the HN crowd love to leave comments of mean criticism as if it was certain the creator of the submitted site wasn't going to see it? You can levy critique without being rude. Not many are doing this, but it doesn't take much. Maybe letting harsher-than-necessary criticism wash over you is necessary for putting any creation out into the world, but it still feels bad to see. This is why people outside this community often dislike their work being shared here, or at least refuse to read the comments.
- doublerabbit 3y agoThe HN crowd are mainly developers who feel that their opinion is strictly correct with no leeway; as per developer culture. If it's not Apple, Go or Rust; or some ten-story sandwich stack of cobbled together libraries, it's deemed trash. Don't you dare mention Java. But what do I know, I'm just a sysadmin after-all. Everything is full-cycle cynicism to me; tomorrow we will be bitching about SPA's again and praising some new reinvented library. Bring back ActiveX and JavaApplets. I'm sure I'll get some "deemed worthy" downvotes for this comment; and I think I need more tequila.
- baranul 3y ago[dead]
- mardifoufs 3y agoEspecially for an article about... PWAs. It's so weird to be this worked up about this, like sure maybe they suck but that's not the point of the article. It's like getting mad at someone for writing a c++ article because it's not a memory safe language... like... okay!
- ryan29 3y agoA lot of the criticism seems to be about the UI and the site is about functionality that's available. It doesn't make sense to criticize the implementation details in my opinion. It's disappointing because this site was one of the rare occasions I emailed the link to myself so I can add it to my list of things I want to look at. Having a concise demo of PWA functionality that exists is very useful.
- pieresqi 3y ago[dead]
- PrayagBhakar 3y agoIsn’t there storage limitations for mobile PWAs?
- gregopet 3y agoI fell for the marketing and built a PWA for an app that needs to receive notifications even with the device in "deep sleep". It kind of worked, but not quite, which was a huge deal breaker. It took me a lot of googling to find an obscure Chromium bug report stating that this doesn't work as reliable as in native apps and is in that nasty "we will never close this ticket but we will never work on it either" state. Complete with many many howls of outrage from people like me who depended on this working right and now have to rewrite their app.