1. Be a developer and you (or a spouse/child/friend) get motion sickness when looking at the phone while travelling.
2. We’ve known the mechanisms of motion sickness (looking at something static while your inner ear indicates you’re moving) from before smartphones were a thing.
3. We already have a ton of information on the phone to know when we’re in a vehicle, how fast we’re moving, direction, so on.
4. Try adding something to the static screen so it moves in tandem with you and thus reduce the cause of motion sickness.
5. Get the people who get sick to try it out.
If anything, I’m surprised it took a decade and a half to come up with it.
And this is exactly how things in large corporations don't happen. Things in large corporations who pay so well that nobody makes it through the recruitment filters and competition who's more than 2% off from being a pure assessment metrics maximiser. In my mind, chasing an idea like this just does not match the type.
Why it isn't likely to have happened before: trying is only easy for a developer who is not only very familiar with the API for reading those motion sensors but also with the API for system wide overlay. This a strict no for your run of the mill to-do list app. Combine that with the requirement of being affected themselves (or someone close), having the idea, having the time to try and no competing side quests that take up all attention. And the requirement of when the experiment was successful, having the kind of access that actually serves as a conduit for ideas not only on paper to someone in the position to make it a product. That's a lot of stars that need to align. Personally I wouldn't even be surprised if there was an LLM angle: would still need someone in the know to try it, but chances are that knowledge combined with a bit of prompting could be a path to PoC implementation that could clear effort thresholds that would stand in the way of conventional coding.
That has nothing to do with the feature being “ideated, then prototyped, then validated”, which is the crux of the conversation. It having taken so long is but a footnote.
> Personally I wouldn't even be surprised if there was an LLM angle
I would bet money there wasn’t. The feature was introduced in early 2024, meaning it has to be thought about, developed, and tested before that.
This isnt quite right. For one 2) is not required at all! I regularly get sick to the point of vomiting, no screen required. It can even happen while i driving! Looking at a screen with this on helps - looking at a screen can now reduce my motion sickness. neat.
4) - it is not motion but acceleration of all kinds. When the plane takes off, the dots move in reverse. When the train stops (no more motion), the dots continue moving for several seconds. Which is to say, its a little more complicated to get it just right than it would seem!
1. Be a developer and you (or a spouse/child/friend) get motion sickness when looking at the phone while travelling.
2. We’ve known the mechanisms of motion sickness (looking at something static while your inner ear indicates you’re moving) from before smartphones were a thing.
3. We already have a ton of information on the phone to know when we’re in a vehicle, how fast we’re moving, direction, so on.
4. Try adding something to the static screen so it moves in tandem with you and thus reduce the cause of motion sickness.
5. Get the people who get sick to try it out.
If anything, I’m surprised it took a decade and a half to come up with it.