I've only been a dev for about a year but I keep coming across FE issues in iOS that make no sense. Animations that require a minus 3 second delay so that they don't end oddly abruptly. Safar browser handling transparency as a shade of black rather than true opacity. Janky stuff.
There are other employers. There are other fields. It takes work to get out but the reward is being respected as a person, being paid fairly for your work, and work-life balance. Compared to the cost of unpaid labour (in cash, time and dignity) it's a no-brainer.
I was the only person who refused to do it.
My colleagues felt this was unfair. And it was. But that wasn't my responsibility. I wasn't the entity exploiting them.
Fixed up my accelerometer demos:
π΅ Dot Demo: Lay your phone flat. Tilt to roll the marble across the surface.
βοΈ Tilt Demo: Hold your phone upright. Tilt to move the block.
π±β¨Mobile, cross-OS, cross-browser
https://t.co/Ak9wYdK8nY
Messy demo of tilt controls in mobile browsers. Should work on mobile devices with accelerometers running Android or iOS, in Chrome, Safari, Edge & Firefox. iOS users will need to click the permissions button before it'll work:
https://t.co/9HrODeZAdJ
Now, after hours of work, I can finally implement the tilt controls in iOS that took me ~15min to build in Android - although it'll have to be in a deployed repo rather than a succinct codepen π«
Today I've been learning about iOS restrictions on browser access to mobile accelerometer data, eg. for tilt controls in browser-based games. Android works out of the box; iOS has a few tricksy hoops! πβ¨