Over a decade on from “mobile first” I’m always surprised at how few developers actually test their work on mobile devices.
It’s fairly common for these sorts of things to be iPhone-specific, and you can’t test on Apple devices without owning one, or paying altogether too much.
I’ve found Epiphany (a.k.a. GNU Web), which is based on WebKit, to be decent proxy for testing on Safari—in my last project of this sort, where I was developing on Firefox and could check in Chromium, I was able to reproduce each of the three or four Safari issues that were raised, in Epiphany.
loading story #41454812
> It’s fairly common for these sorts of things to be iPhone-specific, and you can’t test on Apple devices without owning one, or paying altogether too much.
That's correct, but Apple phone users are customers with money used to paying.
loading story #41455219
The issues differ wildly between Android and iOS and often a fix for one device, OS and browser breaks something in another. It's not easy. Also, not everyone has access to an iPhone or a Mac with a simulator, and even the simulator has its own irregularities with how things are behaving that are not consistent with an actual device.
Which is a shame because one of the upsides of building mobile-first is that you generally end up with simpler/easier to reason about results.
(not a comment on this site implementation per se, but a general remark)