Hacker News new | comments | show | ask | jobs | submit login

I wonder what the workflow is in the Apple teams that allows them to catch stuff like this. Is this the work of a single, smart programmer, or a good QA team?

It's most likely from a strong culture of interaction design and usability testing. During the design process, you usually do usability tests with would-be users and they can help illuminate issues with your design. In this case, it may have even been during testing that a person said, "well that's not what I meant by tomorrow."

Pretty much every time I do a usability test or study, random users catch small things like this that help make a product much better. When you design without feedback, you have your own mental model of how everything is supposed to work. But you're the designer and the expert, and users are not. They often find different ways to use your product than you intended.

But it's even more impressive because you could do usability testing all day long (during work hours) and never catch this issue. It's when someone's _really_ using it where something like this comes up.

I'd imagine someone was dogfooding and had an 'ah hah!' moment when they hit a similar issue. Often the best way to spot anything missing.

Like talking into a prototype iPhone at 00:35 while drunk in a bar? :D

Considering it is Siri, it is not a good QA team. Probably a programmer who set an alarm shortly after midnight one time and had an unexpected result.

It's possible this wasn't actually an Apple designer - Siri was fairly well featured when they acquired it.

This has to be internal user testing feedback.

One of those delicate edge cases that you find once you start using a product.

It's called user experience design.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact