If you're a button, you have one job

	If you're a button, you have one job(unsung.aresluna.org)
	567 points by nozzlegear 1 day ago \| 263 comments
	tl;dr: When rotating a photo, iPhone buffers rapid taps so eight quick taps produce a full 360° round-trip, while Nothing Phone/Android ignores taps during the rotation animation. The author argues this matters because even "casual" interfaces eventually meet power-user scenarios (e.g., rotating dozens of documents), and UIs should never force users to wait for an animation to finish—either buffer inputs or accelerate/interrupt the animation.
	HN Discussion: ↓Buffering rapid clicks can cause problems like accidental double-actions, so debouncing has merit ↓The 'you had one job' framing is wrong because buttons have many responsibilities beyond being clickable ↑Animations should serve function, not block input; UIs shouldn't force waiting for animations ↑Buttons need clear feedback states to communicate whether clicks registered ↓The Android/Nothing Phone criticism may be inaccurate since the behavior can't be reproduced