this post was submitted on 27 Jun 2024
1142 points (97.2% liked)

> Greentext

7548 readers
1 users here now

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 5 months ago* (last edited 5 months ago)

As a mobile developer, tiny unhittable buttons drive me batshit. I used to get handed app design documents all the time that had these little buttons, along with image files for these buttons that were just large enough (width and height) for them. I would always do a trivial amount of extra work to make the actual tappable regions larger than the images to improve their usability, but when I mentioned this to the designers they would go apeshit and demand that I restore the original tiny tappable regions, usually with the bullshit rationale of that being what end-users expected and they didn't want to verify that what I'd done to my best judgement was OK. Management would go along with the designers, on the grounds that enlarging the tappable regions required more time and effort - even though I'd already done it and undoing it would require even more time and effort.

It eventually occurred to me to just do it without telling anyone and I had no further problems.

A fun little fact about iOS: the operating system includes a private method (which is something developers supposedly can't use without getting their app rejected) named _warpPoint. This hack was put in when they started supporting landscape, because the top toolbar and its tiny buttons became even tinier and virtually unusable in that mode. _warpPoint intercepts touches near the toolbar and changes the coordinates to the middle of the nearest button - basically doing the same thing I was doing by enlarging the tappable regions, just doing it at the global level. The irony is that they still don't really work very well, despite the very existence of this method proving that Apple knows it's a general problem.