2 ms·
I’d be interested to see how the customers made an informed choice between a non existent native app and a PWA app. Probably they made the choice after listeni
by tinus_hn 5y ago
I’d be interested to see how the customers made an informed choice between a non existent native app and a PWA app.
Probably they made the choice after listening to an opinionated story about ‘sitting around waiting for updates’. Which nobody does, of course, because if you mind that you just turn on automatic background updates.
At least in this story Safari is good enough to have the features that matter. The world is safe.
- zdragnar 5y agoAs for an informed choice, the company (and their clients) that I am thinking of is in a crowded market. Not having to make employees download a new app ended up being a surprisingly (to us) compelling selling point. As for safari, we supported IE11, chrome, Firefox, mobile / android chrome, desktop and mobile safari. Safari easily added about 10% to our development budget, and safari users got a downgraded experience in certain cases. Not ideal, but close enough for me to not feel bad calling it the "new IE" (and yeah, I remember developing sites for IE 5.5 and 6). Edit: speaking of auto updates, I have it turned on myself, and just yesterday had to wait around to update my mobile bank app to virtually deposit a check- log in, get kicked out to update, wait to download and install, then log in again before I could proceed. Not sure why, but auto update isn't a cure-all.
- tinus_hn 5y agoHere’s the magic part: if you are the developer, you get to decide if the backend works with only the newest version or also some earlier ones. And if you just do nothing, the user will be just as logged in in the new version. So, unless they are really unlucky, they’ll never have to wait for an update.