8 ms·
I don't really understand this. If you want to make something local, make an app and distribute through the app store, that's what it is for. A web app on the
by mulmen 7y ago
I don't really understand this. If you want to make something local, make an app and distribute through the app store, that's what it is for. A web app on the other hand is connected by definition, no?
Apple forcing local apps to distribute through the app store is a feature.
- ianlevesque 7y agoPeople keep wishing for a loophole. There isn’t one they won’t close sooner or later.
- swsieber 7y agoA feature for who? Not for users - now there's one less avenue for developers to get them something they want. Not for developers - now they have to jump through additional hoops to make something that works cross platform. Who exactly does this benefit?
- snazz 7y agoUsers want to be able to log in and see their data from any device. If the whole idea is that there is no server that the data is stored on, then you can't have a sync function, can you? Do any of you have an example of a good offline-only PWA that will be affected by this?
- swsieber 7y agoThe whole point is that you don't need to download a big payload just because you haven't used it recently. There are two ideas that go together well: * The app can work offline * The app doesn't need a server to function Neither of those prevent a sync function from existing. Right now, apps can do both of those. Why don' we want PWA's to be able to do the same? Why do I have to go through Apple's walled garden in order to so? Especially when said alternative is in a sandbox?
- woodson 7y agoIt means you constantly have to re-login on a PWA (e.g. Twitters web client PWA).
- falcolas 7y agoConstantly being weekly at most frequent in this case.
- vxNsr 7y agoI roll my eyes every time robinhood makes me login again after an app update... though it hasn't happened in a while, so maybe they fixed that bug, but it was annoying when it's an unexpected hurdle that doesn't follow what other apps are doing.
- dktp 7y agoGames with your personal high scores. Is the one that would affect me Plus a local note-taking app I created a while ago
- eslaught 7y agoThe whole point is that those PWAs probably never got built in the first place because the foundations were always shaky at best. It's a chilling effect. But if you look at native apps, especially ones I use on desktop OSes, they're dominated (at least in my usage) by offline-first or offline-only apps---and for me, this is a feature, not a bug. This doesn't have to mean they don't have sync, by the way, it just means that's separate from the main functionality of the app. A perfect example of this is Dropbox: it syncs to your local disk by default. It's easy to forget how valuable this is until you go camping (or similar) and suddenly you realize you forgot to star that one directory you care about. Now your mobile phone is useless, but your laptop works no problem. And due to this being factored out into a separate app, all my files now work regardless of file type (I don't need separate offline support in every app I use, since that's the default).
- veeti 7y agoIt's no less of an issue for an online-based PWA. Where do you store login credentials or session tokens? In local storage. What happens to them when Apple decides to arbitrarily throw it away? The user has to log in again and again. This sounds like a seriously poorly thought out idea. Want to clear tracking data from random websites I've been to? That's great. But you don't mess with the data stored by apps I have specifically _chosen_ to install on _my_ device.
- bengale 7y agoBut only if they don’t interact with it for a week. I wouldn’t be surprised if a web app I hadn’t used for a week required me to login.
- veeti 7y agoThere are many apps on my phone that I only use every once in a while, yet every single one of them remembers me. No matter how long I've been gone. Technology is amazing! Where is Apple's famous UX here? What legitimate argument is there for clearing data of an app the user has added to their home screen?
- admax88q 7y agoAnd most native apps crash one a week, we should therefore automatically crash every app once a week. Just because current apps are buggy doesn't mean we should enforce those bugs at a platform level.
- Dylan16807 7y agoI wouldn't be surprised but I would definitely be upset.
- carlosdp 7y agoIt doesn't have to be that way though, that's the point of PWAs. A way to use web technologies for local applications.
- osrec 7y agoSo you can think of absolutely no situation where a user would access a web app, and might want to store state info locally?
- falcolas 7y agoI can personally think of cases (not that PWAs have ever been anything but fragile when it comes to locally stored data), but as a user, the occasional clearing of super cookies is a bigger boon.
- osrec 7y agoI don't disagree that local data for PWAs has always been fragile. I wished browsers were taking steps to make it less fragile, as opposed to more fragile. It would allow certain use cases to become valid for PWAs, thereby circumventing the need to create a 10mb native app for something that can be deployed much more easily and quickly with 30kb of Javascript.
- falcolas 7y agoRespectfully, I haven't visited an online SPA with under 100kb of Javascript in a very long time. Anytime I care to look, they are almost always in the 5mb range. So, an offline app's size, when compared to just browsing the web, isn't a compelling difference (especially since it's downloaded maybe once a month or so).
- brlewis 7y ago> A web app on the other hand is connected by definition, no? No, it just has to run in a browser.
- fastball 7y agoWell it needs to be downloaded from the internet at least the first time, so it's intrinsically going to be less secure than an app that you can guarantee never connects to the internet.
- osrec 7y agoYour app needs to be downloaded the first time too. In fact, a downloaded app can run riot on your filesystem. A web app runs in the "cage" of the browser, and is arguably more secure and explicit about permissions it requests.
- rstupek 7y ago"... can run riot on your filesystem"? Citation needed because an app is as heavily sandboxed as a web page running in a browser. An ios app gets no view into anything you as a user don't choose to give it (no access to photos, etc).
- osrec 7y agoI mean, if you give the app access to your filesystem (which a lot of non-tech users would, almost without thinking), it can potentially access/modify/delete your files and folders. With PWAs, that's not really a possibility.
- LocalH 7y agoStock iOS doesn’t allow apps to directly access data from other apps afaik
- e12e 7y agoHas to come from somewhere. A pwa might have to come via http (I'm not sure) - but html+js+css can come from the (from a) filesystem too. Like an USB-c memory stick. Or from an extracted archive (much like a native app).
- cryptonector 7y agoApple's app store is a walled garden. The web isn't a walled garden. TFA wants to be able to operate outside the walled garden. EDIT: Also, it's probably cheaper to develop one PWA than a PWA + N native apps, even if N=2. Probably lots cheaper. Now, perhaps there's a way to build a native app that is just a wrapper around WebKit/Safari and a PWA, but you'd still be subject to Apple's walled garden. For example, think of Gab or some such website whose apps have been banned by the various app stores...
- untog 7y ago> A web app on the other hand is connected by definition, no? No, not in the era of "progressive web apps", which is really just a little bit of branding around interconnected APIs. The Cache API in particular means that a webapp can be downloaded and made available offline on a permanent basis. Unless it isn't actually permanent at all, which is what Apple are doing here. The web and the App Store are just delivery mechanisms for code with different trade-offs built into them. Apple have added an extra trade-off on the web side in the name of privacy.
- icedchai 7y agoPersonally I would never expect a web app to be available offline on a permanent basis.
- untog 7y agoOkay?
- icedchai 7y agoI basically assume my phone is nearly useless without connectivity. And if I want something to work in that sort of environment, it better be a native app.
- untog 7y agoOkay? ...I guess I don't really see why the current state of things should block any future development. Browsers shouldn't ever implement new features because users today aren't expecting them to exist?
- rezz 7y agoTo an end user there’s an icon on their screen, they tap it, the app opens. It didn’t matter if they downloaded from the AppStore or from a website. This is no longer the case which is why the OP is upset.
- ajford 7y agoNo, it's a grab for money. Releasing an iOS app requires Apple hardware, X-code, and an Apple developer license which is $100/yr. Where as developing a PWA can be done on any hardware, and would be natively cross-platform. An offline PWA does not require an active connection, and in fact is the one of the reasons behind the idea of developing a PWA instead of a general webapp or website. All other browsers allow the use of local storage to optimize and enhance your experience by allowing things like pre-loading data or storing your preferences. This disappears with the decision Apple made to clear storage.
- jfb 7y agoI promise you that Apple does not give a shit about the revenue from the developer program.
- lliamander 7y agoThen why not make it free?
- falcolas 7y agoThat's easy. It adds a hurdle for people who make malicious or fraudulent apps. It's not free, but neither is it MSDN levels of absurdity.
- fomojola 7y agoI'd counter that: make it a one time tax, like the Play Store. Is it reasonable that I need a Dun and Bradstreet number to write an application for my computer?
- judah 7y agoIt's not just about the revenues of $100/year. It's also the revenue from 30% sharing of profits. And most importantly, it's the bigger revenue generated from having apps that work only on iOS, which drives users to buy iPhones and iPads.
- EvanAnderson 7y agoYou should research the original plan for "apps" on the iOS platform. There was no "native app" story originally, and Javascript-based applications were expected to be the only 3rd party platform on the OS.
- npunt 7y agoAs should you. It’s not that an app ecosystem was never planned, it’s that it was not an early priority. Remember they were literally defining everything at the beginning - OS, UX, APIs, core features, hardware, first party apps, market positioning, etc etc. Needs of third party developers weren’t nearly as important as nailing the basics and ensuring a risky project was a success. The html5 app bit was a way to test the waters for developer interest and demand but very much an interim solution.
- EvanAnderson 7y agoHow do you square that against all the reported accounts (including the Isaacson biography) of Steve Jobs saying that he was opposed to third-party native applications on the platform? Yes, they changed direction in 2008. That's just it, though. They changed direction.
- npunt 7y agoJobs’ hot takes aren’t the end-all when it comes to product intent at Apple. He was basically an embodiment of strong opinions weakly held. His superpower was focusing teams on what the right set of features would be to create a product that made sense to the market, and ignoring everything else. The phone / iPod / internet communicator trifecta was example of this - nothing but nailing those three mattered at launch, and any effort elsewhere was wasteful. Without that kind of leadership, eng teams will often dither efforts over many things that don’t matter to success. The history of Apple is filled with examples of this dynamic. iPhone was a group effort among many talented and influential people and I doubt Forstall and others driving software had same opinion on third party apps. They just didn’t pick that battle before it made sense to. Every other computing platform at the time (including Windows Mobile, Palm, and BlackBerry) supported third party apps, it’s not like the use case was novel or difficult to see, and the webs limitations were considerable. Adding apps was a default path temporarily set aside.
- gnicholas 7y ago> If you want to make something local, make an app and distribute through the app store, that's what it is for. Have you ever gone through the app review process? It can be frustratingly capricious, which makes it very expensive. We've had features in our app for years, displayed in plain sight, and then all of a sudden they decide to block an update because of these utterly innocuous features. No rhyme or reason, and now we've got to spend dev time fixing a "problem" that never was a problem before. And we have to delay our entire update because of it. PWAs offer a way around that uncertainty and added cost. There's also the cost of a developer license, and the Apple hardware you have to buy to run XCode (and probably iOS devices too, so you can test IRL).
- jariel 7y ago"Apple forcing local apps to distribute through the app store is a feature." Forcing companies to give Apple 30% is not a feature. If companies feel they can deliver a net experience in webapp that's better than an app, then so be it, it's their choice. App makers are smart enough to know what makes sense for them.
- txcwpalpha 7y agoAt one point, Apple was denying some app store reviews because they said they should be distributed through PWAs instead. If this is supposed to be a "feature", it seems like some product manager has their head up their ass. Also, the entire point of PWAs is that they are supposed to have feature parity with local apps, but delivered via the browser. This change is obviously counter to that goal.