Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I switched to Android after 7 years of iOS

joreteg.com

Post reply on HN
Print view View original

41–50 of 524 posts

Re: I switched to Android after 7 years of iOS

#41

Post by kec »

untog wrote: post #28
ryao wrote: post #19

> WebBluetooth (yup, talking to bluetooth devices from JS on a webpage) This sounds like a great new attack vector for the black hats of tommorrow. There are just some things that a web browser should not do. Exposing things that previously required escape from sandbox attacks is one of them.

> There are just some things that a web browser should not do. Exposing things that previously required escape from sandbox attacks is one of them. Why is it any different from an app doing it, though? There will be the same permission prompts etc.

I visit far more websites in a day than I use strange new apps. Apps also don't suffer from XSS.

Re: I switched to Android after 7 years of iOS

#42

Post by Ezhik »

Jerry2 wrote: post #5

>So, instead of opening my text editor I placed an order for a Nexus 6P Nexus 6P is notorious for atrocious build quality. It bends easier than a bar of chocolate. [0] Google should do a recall on these things. It bends a lot easier than an old iPhone 6 plus. [0] https://www.youtube.com/watch?v=r3cWVdLqXCg Edit: I see Google fanboys decided to downvote this comment instead of engaging in a debate. This is not in the…

How is that relevant to webapps?

Re: I switched to Android after 7 years of iOS

#43

Post by untog »

toomuchtodo wrote: post #33
untog wrote: post #25

Earlier quoted context omitted.

The article itself cites things like the lack of support for WebRTC and Service Workers.

I can't find a single iOS app I use that needs either of these.

I'm not sure if you're trolling or sincere here. Of course iOS apps don't need them, they are native. We are talking about the capabilities of the iOS Safari browser.

Re: I switched to Android after 7 years of iOS

#46

Post by untog »

rhinoceraptor wrote: post #35
untog wrote: post #15

Earlier quoted context omitted.

> If you aren't worried about provided a first class experience to your iOS customers, then build for Chrome + Android. Although, that sounds a little like "build for IE6 + Windows" 15 years ago. Except that Android is the open one that is implementing agreed upon standards, and Apple is the laggard left behind.

> implementing agreed upon standards Yeah, except most of your users' devices are still running 2+ year old software versions.

But unlike in iOS, the browser is a Play Store app which is updatable outside of major OS releases. So a two year old phone can run the latest version of Chrome.

Why Apple still doesn't do this mystifies me.

Re: I switched to Android after 7 years of iOS

#47

Post by criddell »

rhinoceraptor wrote: post #35
untog wrote: post #15

Earlier quoted context omitted.

> If you aren't worried about provided a first class experience to your iOS customers, then build for Chrome + Android. Although, that sounds a little like "build for IE6 + Windows" 15 years ago. Except that Android is the open one that is implementing agreed upon standards, and Apple is the laggard left behind.

> implementing agreed upon standards Yeah, except most of your users' devices are still running 2+ year old software versions.

That's a really good point.

Do all Android handsets and tablets ship with Chrome now? I'm guessing lots of cheap tablets don't.

And I know Samsung used to have their own browser. Do they ship with Chrome now?

Re: I switched to Android after 7 years of iOS

#48

Post by ryao »

frobware wrote: post #3

Sadly, the web is an accessibility nightmare. If that changes, then sure, I could move too. But there's a lot that modern versions of iOS get right regarding accessibility, stuff that I wish google/android would do too.

I am not a professional web developer, but I used LAMP to make a decent size website using standards conformant XHTML/CSS without table hacks with PHP and MySQL for forms when I was in high school. I wrote the markup by hand, so I made certain to place content first so that 56k modems would load it quickly and web browsers for the the blind would not read navigation bars before the actual content. At the time, I assumed that JavaScript was not always available because people eithet either turned it off to eliminate the Javascript engine as an an exploit vector or were using browsers that did not support it because they were blind.

Consequently, I considered requiring JavaScript for a webpage to load properly to be bad practice. Even if I assume JavaScript is everywhere, I have yet to hear of how one would make things dependent on it accessible to the blind. I know that people will make webpages that require it regardless of whether the blind can view them or not, but I still feel that is bad practice.

Re: I switched to Android after 7 years of iOS

#49

Post by chromakode »

ryao wrote: post #19

> WebBluetooth (yup, talking to bluetooth devices from JS on a webpage) This sounds like a great new attack vector for the black hats of tommorrow. There are just some things that a web browser should not do. Exposing things that previously required escape from sandbox attacks is one of them.

The user experience is similar to webcam/microphone access: nothing works without a prompt and browser-mediated pairing process, and only on secure origins (e.g. https). The spec goes into detail about security/privacy considerations, and includes a blacklist of problematic targets. https://webbluetoothcg.github.io/web-bluetooth/#security-and...

Access through web browsers could expose issues in the user's kernel bluetooth stack, but that risk exists with any binding. There should be time to explore this possibility while the feature is still behind a flag.

Re: I switched to Android after 7 years of iOS

#50

Post by Guvante »

kec wrote: post #41
untog wrote: post #28

Earlier quoted context omitted.

> There are just some things that a web browser should not do. Exposing things that previously required escape from sandbox attacks is one of them. Why is it any different from an app doing it, though? There will be the same permission prompts etc.

I visit far more websites in a day than I use strange new apps. Apps also don't suffer from XSS.

> I visit far more websites in a day than I use strange new apps.

From the article you have to "install" the web application for any of these features to be available.

> Apps also don't suffer from XSS.

From websites sure, but they do from other apps.

Post reply on HN