Hacker News new | past | comments | ask | show | jobs | submit
It’s fairly common for these sorts of things to be iPhone-specific

Having done a bunch of mobile web work recently, I don't think that's actually true -- I hit weird issues on both Safari (on iOS) and Chrome (on Android). (And Firefox for that matter)

Safari does have its weird glitches but it's not inherently glitchier than other browsers.

There are some APIs it doesn't implement, but you don't need real hardware to catch that, MDN / caniuse has all the compatibility data and there are tools like ts-browser-compat for automated checks.

you can’t test on Apple devices without owning one, or paying altogether too much

Right, that's the real problem. But again I don't think it's Apple-specific. If you're a Mac user, in principle you could install Android Studio and test your app there, but a) that's a huge hassle, and b) an emulated phone on a desktop isn't close enough to a real phone to be useful for QA.

You really need to test on both iOS and Android hardware, there's no two ways about it.

I guess it would be good if you could install Safari on Android, and/or real Chrome on iOS. Then you'd only need to buy one phone. And that is on Apple, as they're the one blocking it in each case.