181–190 of 318 posts
Earlier quoted context omitted.
Those could all run in a browser. A PWA isn't cloud software, it's just software that runs on your browser. But they would indeed ask for all kinds of permissions. And K9 and the network scanner would get a really scary-looking permission dialog.
Mozilla would cry bloody murder if Google proposed a raw sockets API for the web, for the same reason why they oppose WebUSB & friends.
Earlier quoted context omitted.
I guess that's why no one uses The Internet or Web Browsers. Pack it in, fellas, the web is a passing fad.
That's not what I said, I live half my life within browsers. But big chunk of the population that you are probably not thinking about is not like that. My mother in law is using browser to read on her computer, and will never do that on her phone - the screen is too small and the whole experience not something that fits someone at her age. On the other hand, my children use apps since they are two years old, and at t…
There’s also a breaking change coming up in SDK 34 around exact alarms.
Google seems hell bent on making the platform more and more restrictive as time goes on because they started with no restrictions.
Apple started off more restrictive and then loosened restrictions as they put actual thought into APIs.
I don’t think there’s been a breaking change since iOS 8 or so.
Earlier quoted context omitted.
On Android you have to pop open a menu and find the install option. That's not inherently discoverable as you need to know it's even possible, and most people don't. It would be trivial to present the user with a more proactive notification that a site can be installed as an app, or even include such a notice in their search results on Google, but they choose not to do so.
Actually nowadays it's not that bad anymore. Android browser itself offers installable PWA and there is an event called beforeinstallprompt event ( https://developer.mozilla.org/en-US/docs/Web/API/Window/befo... ), which can be used to perform PWA installation on user interaction. Of course it's not supported in every browser. iOS is more difficult since user needs to understand that "saving to home screen" is same a…
It literally took a two second Google search
Earlier quoted context omitted.
Actually nowadays it's not that bad anymore. Android browser itself offers installable PWA and there is an event called beforeinstallprompt event ( https://developer.mozilla.org/en-US/docs/Web/API/Window/befo... ), which can be used to perform PWA installation on user interaction. Of course it's not supported in every browser. iOS is more difficult since user needs to understand that "saving to home screen" is same a…
In iOS it’s also buried deep in the “share” menu which makes absolutely no sense as you are not sharing the website with anybody.
I also got this email, but professionally and personally. Personally, I voluntarily built and run open source apps for 16 different cities for their transit system. This gave me two weeks to update 16 apps, for no benefit of anyone. My app is a PWA, and the Android version just uses cordova + a few plugins to add a few native options. Unfortunately, updating cordova to support the new target android api broke some of…
I have compassion with you, some of my private apps were also affected. But we were being told this deadline for many months now. It was clear that at some point they would show it more in your face. I also disliked the way it was formulated, also, even if everything was fine in production, it complained when testing versions didn't comply (doesn't make sense). Also, it was always only about pushing new updates (it's…
Earlier quoted context omitted.
I just have no desire to have an app. The attempt to download one when I visit a website is unwelcome.
That's what's pretty great about PWAs: 1. For people like you that don't want to install them, they're just a normal website. 2. For people that do want to install them for the added functionality (things like notifications), then it is easy to install, and furthermore cheaper for developers to build and maintain (one codebase instead of multiple). You say "you have no desire to have an app", but I think for most peo…
Earlier quoted context omitted.
> it's just that most users really have separated in their minds (not surprising due to history) that apps come from app stores, and the browser is used for websites. Right, because for a very long time (and maybe still) PWAs have been much closer to terrible websites than good apps. They generally don't have the same UX properties as real apps. Remember when the iPhone first came out and web apps were the only optio…
But nowadays you can't really see the difference between good webapps and native apps. We also migrated our native apps to full SPA apps. And really it makes development so much easier. The apps we have are relatively simple without fancy stuff. But the css render engine is fast. Even on Android. And we reduced some of our apps from 30mbs of java code to 150kb of java/typescript. Plus as a bonus we can have a website…
So two of the three parts that are native are there to make it a worse user experience?
Earlier quoted context omitted.
Play has raised it's tarter API requirements several years now and repeatedly warns a full year ahead of next change. If you never heard of it you've been deliberately playing dumb.
In my case, I was hired to work on an update to a legacy app ~8 months ago. So this is my first round of bs. Been writing software for 20 years and I’ve never seen this before… I wouldn’t consider it playing dumb, I’ve just never had cause to care or receive an email like this.