Rukky: Planning a Ride as a Conversation
I wanted to explore a simple question: what if planning a motorcycle trip felt more like talking through an idea than filling in a form?
The Rukky film starts with the fiddly version of that experience, then imagines a quieter one. A destination becomes a conversation. A stop can move to the beginning without losing the final destination. The system asks before saving the trip.
The ride in the film is simulated. It is an illustration of the interaction, not footage proving how the app behaves on a real journey.
The small interactions matter
A voice interface still needs to make its state understandable. In the film, lettered choices make it possible to answer briefly. Small actions get a quiet acknowledgement. Larger changes, such as saving a trip, get a confirmation.
Those details interest me because a spoken command can otherwise disappear into the machine. Did it hear me? Did it change the route? Is it waiting for an answer? A useful interface needs to make the next step clear.
Separate planning from riding
The planning conversation happens while parked. That distinction is part of the idea, not an afterthought. A voice interface should reduce the need to handle a phone, and it still needs careful testing before anyone relies on it on the road.
The film also illustrates music controls, checkpoints, and a request to go home. I would treat it as a design walkthrough: look at how each moment is acknowledged, where a choice is offered, and when the person stays in control.
If you are building a voice interface, sketch one of those moments yourself. Start with the request, write the system's answer, and decide what confirms that the right thing happened.