211–220 of 927 posts
Safari already was lagging behind Chrome, Chrome forks and Firefox in a lot of feature adoption. This will only make it more of a "new Internet Explorer", a browser that sites recommend you NOT to use.
I already have a comment on this subject in a thread here but I believe this should be stressed more explicitly. Apple didn't kill offline web apps. You can always add an interaction to your app which exports the stored data into a file which then can be saved by the user. It can be done entirely on the client side as well. If anything died here, it is the implicit consent by the user for allowing unnoticed storage s…
But that is not the deal, the deal is that they fear that more and more developers are moving to webapps instead of developing native apps that need to pass trough the App Store and thus be approved by Apple, and they don't like that.
I already have a comment on this subject in a thread here but I believe this should be stressed more explicitly. Apple didn't kill offline web apps. You can always add an interaction to your app which exports the stored data into a file which then can be saved by the user. It can be done entirely on the client side as well. If anything died here, it is the implicit consent by the user for allowing unnoticed storage s…
>You can always add an interaction to your app which exports the stored data into a file which then can be saved by the user. But... why? Drag the user through some dialogue to save a file locally / manage / be responsible for that and then deal with that whole deal? That seems like very... old / unnecessary. The fact that applications store some random things locally to me is neither surprising nor a hassle. Browser…
Here is a fun idea that just came to me (trying to find middle ground here):
- Allow localStorage writes automatically, persist forever (choose your favorite definition for "forever").
- Allow localStorage reads automatically for 7 old.
- Prompt permission dialog if last read from localStorage is at least 7 days long.
I really appreciate this link. I would have never seen this otherwise. It's kind of a disappointment for us on the enterprise side. Our main offering is an offline app where people are disconnected from the internet for weeks and we use localStorage to validate who they are. It's a bit vague about how this affects apps that don't use safari. Nevertheless, we might have to start to really think about the user experien…
I hope they come up with some good options as this news settles. It's hard to see this as anything but even just a accidental push ('well you should always have written an app for the app store') to force folks to write a native app / participate in the app store.
Earlier quoted context omitted.
User not coming to website 7 days can't be invalid use-case. Losing important data simply because someone went on vacation is unacceptable.
Not allowing important data to be downloaded for cold storage is unacceptable.
Earlier quoted context omitted.
I don’t even play games but I wouldn’t expect a web game to store all of its metadata in my local storage. I would expect it to store data on their own severs and only store active gameplay information locally. My browser storage is not a game developers long term storage, its a cache.
Why? Are you paying for it? To you, it's trivial amount of data that you can wipe if you somehow desperately need the 1mb, to them it quickly adds up to significant costs. I find this position absurd, just like the suggestion that everyone should start programming complicated user hostile save flows.
I already have a comment on this subject in a thread here but I believe this should be stressed more explicitly. Apple didn't kill offline web apps. You can always add an interaction to your app which exports the stored data into a file which then can be saved by the user. It can be done entirely on the client side as well. If anything died here, it is the implicit consent by the user for allowing unnoticed storage s…
Earlier quoted context omitted.
Apple disallows third-party web rendering engines. Google Chrome on iOS uses own networking stack. It is still a significant restriction, but it is rather understandable. Without it it could be just Blink everywhere at this point.
So it's not about what's best for the user but what's best for Apple? I wouldn't call that "understandable". All this is doing is contributing to webkit monoculture.