131–140 of 238 posts
Earlier quoted context omitted.
I'm saying that yes, webrtc is part of the HTML 5 web and so should be a basic human right. I'm not saying that it is though.
Except when WebRTC actually isnt a part of HTML5 (yet), it's only a draft specification.
/sarcasm
If every browser just focused on 'the specs' where would the innovation come from. In fact i'd strongly argue that Apple / iOS is the reason we have such a standard web based eco system at the moment. I mean who remembers the dark days of Java Applets, ActiveX components and browser specific plugins? Apples firm stance on the lack of plugin support was a major factor in their demise and the birth of the amazing rich JS & HTML5 world that many here seem to take for granted.
In short it strikes me as the wines of a spoilt child complaining about their parents forgetting that they are the one's who taught them how to tie their shoes.
Earlier quoted context omitted.
You probably never used "add to homescreen" before. PS. 50% of these group of apps are web applications - https://postimg.org/image/59r83pe5f/ Why shouldn't i be an ordinary user? All of these web apps are money related ;)
What feature does AliExpress on Android have that isnt supported by Safari? Is that DHL site using Web Push Notifications for either Android or Apple platforms?
Earlier quoted context omitted.
Definitely a PR stunt, but even so, being sued because you are so behind on standards that it's hurting other businesses certainly puts the spotlight on you.
"So behind on standards". Remind me which browser engine has 100% es6 support? Now remind me which half-baked web api exposes local network information to the JavaScript environment. Oh right. It's HN so apple is the work of the devil and Google is basically Jesus returned.
Many of the HTML5 technologies Apple is steering clear from make the Web more App like meaning they become a threat to their dominance with the App Store on their own platform. The longer they take to adopt them the longer they can benefit from the exclusiveness and control over iOS app ecosystem. I don't think sueing them will get them anywhere but it might be a push to get them understand that users are aware of th…
When I see someone suing a company for not innovating fast enough and opening with sexist terminology[0] I just close the tab and move on. [0] - "Anyone running html5test ( http://html5test.com/ ) on his iPhone"
One of my friends routinely says things like "a woman has rights to his body" when speaking in English because in French possessives agree with the object not the subject, and the French word for body, "corps", is masculine.
In this case, since iPhone starts with a vowel, in French you'd say "son iPhone", so "his iPhone", perhaps.
Alternatively, in French you also always tend to the masculine form in the general case, so maybe that's it? It just strikes me as extremely unlikely that anyone would think, consciously or otherwise, that women don't have iPhones.
It's really hard to believe that Apple is holding back the 'mobile web' when it's shown time and time again that they have the best performing web platform in the market. It was true when iPhone was introduced in 2008, it was true in 2015[0] and it is still true now[1]. "In a nutshell, the fastest known Android device available today -- and there are millions of Android devices much slower than that out there -- perf…
Don't use speed as an argument.
Earlier quoted context omitted.
Isn't it obvious? If they supported things like PWAs and other mobile web initiatives, people could build applications that run seamlessly on their phone, look like native apps etc, and they wouldn't go through their highly lucrative app store. As phones get more and more powerful and things come along and mature like webgl etc, the reliance on native apps drops more and more. As does Apple's control. Maybe I should…
For Apple, the App Store is not 'highly lucrative'.
I realise they also make a lot on hardware, but it seems like that's a revenue stream they wouldn't want to lose.
someone should also sue Apple (and Google?) for worse performance in the webview. something that run smoothly on native Safari was laggy in webview. haven't checked in a while though, not sure if this is still the case.
Earlier quoted context omitted.
It's obvious you are not a web developer using HTML5/CSS3/ES6. iOS has became the new Internet Explorer hands down, and now it's the first platform I test on to check for compatibility issues (as it's the one that normally gives those issues).
Nope. (Front end) web developer by trade. What I say I say from experience - I've never had a client ask for a feature that Safari doesn't support. However, clients do ask for things like a carousel, which Chrome doesn't support natively. iOS is a significantly easier support target compared to Android due to how much of a stable target it is. Android is a bit of a 'which Android?' when it comes to browser support.