story
Many of the patients are older folks. They tend to press long and hard on the big buttons.
A sensible app developer traps tap and long-touch, and sends them both to the same handler. This developer only catches the tap event, and ignores long-touch. The attendant was getting grumpy, because she had to keep telling patients "tap 'gently'."
It's just me, I know, but I get salty, when I see this kind of careless UI design (it was the app's fault -not the iPad's). I know that the medical group paid big bucks for the app.
I think it tends to be the more well-off schools with the iPads, the chromebooks are definitely a lot cheaper over the long run for the district.
I'd need to seem some evidence for that - cheap chromebooks break very easily. Talk to any school IT person who handles device repair/replacement and you will hear nightmares of 50+% loss rates...
Things like the keyboard caps were a constant pain point, but they were durable little devices and 30 minutes as all it took to fix the worst of issues.
We would just hang on to the Chromebooks whenever they had a fault that made them inoperable, and when a new one came in with a problem, like missing keyboard caps or a broken webcam, we'd just part out one of the Chromebooks from the graveyard.
I imagine that would be significantly more difficult with an iPad, even just opening them up is much harder, and there's not a whole lot you can do to fix them.
Your district is liable to be unpleasantly surprised. Like ours, they will likely find middle school-ers are worse at caring for Chromebooks. The rate of broken Chromebooks for us was staggeringly high.
