You tap a stone onto tengen. The screen flashes. The phone gives a small buzz. And still, something feels unseated, as if the move has not quite landed. The awkwardness is tiny, but it accumulates. Each turn feels separated from you by a pane of glass. However tense the position becomes, your finger never quite enters the board. Move feedback is the craft of making that half-second — touch, sound, and image — arrive in sync.
A Move Begins With Confirmation
On a phone, Gomoku loses the weight of a stone meeting the board. After you tap, you need a clear answer: this stone is on this intersection, and the turn has passed to the other side. If that confirmation is too faint, you wonder whether you mis-tapped. If it is too heavy, it pulls attention away from the shape of the position.
The familiar case is defending against an opponent’s open three. You find the only blocking point and put your finger down. If the feedback arrives a beat late, your mind first checks, “Did I tap the wrong place?” The hesitation is brief, but it breaks the thread of reading.
Keep the Vibration Short, and Weight It by Event
Haptics are easy to overdo. A long buzz after every move becomes irritating within minutes. In an endgame, when stones are traded quickly, it can make the phone feel as if it is hurrying you. Restrained vibration usually feels better than busy vibration.
The Apple Human Interface Guidelines remind designers that haptics should complement visual and audio feedback, remain consistent, and avoid overuse; short, optional haptics are better suited to frequent actions. Gomoku is exactly that kind of frequent action: dozens of moves in a game, and many more during quick review.
Android’s haptic design principles are just as direct: less is more. They also recommend matching the importance and frequency of an event to the strength of the vibration. An ordinary move can be light. A win or loss can be slightly heavier. An undo or an invalid point can use a different, shorter cue. Without reading instructions, you gradually learn the distinctions.
Feel comes from proportion, not volume.
Sound Should Close the Move, Not Perform It
The sound of a stone is tempting. Wood, slate, a crisp click — each seems to restore something of the real board. But phone audio lives in unruly places: the subway, the office, a bed at night. The same sound can turn from polished to intrusive.
The safer approach is to make the placement sound short, light, and with little tail. It works like a period, telling you the move is complete. Once the sound lingers, your next thought is caught on the previous move’s echo.
Google Design’s material on Sound and Touch describes multisensory design as the meeting of sight, hearing, and touch, and notes that microinteractions feel more satisfying when sound and haptics are sufficiently fine-grained and light. The word that matters here is subtle: audible, but not occupying the room.
Motion Must Follow the Hand
Visual feedback is often underestimated. A stone fading from transparent to solid, growing from small to full size, or settling lightly on an intersection all tell you, “This is the right spot.” The problem is timing. If the animation is even a little slow, the rhythm of reading falls apart.
Gomoku thinking does not happen in one corner at a time. You play in the upper right to defend a four-in-a-row, and your eyes immediately need to return to the lower left to check for a double-three risk. If the stone is still easing into place, your gaze stays trapped, and the next judgment arrives a beat late.
A good placement animation should be so short that you barely notice it. You can feel that it exists, but you do not wait for it to finish. The board stays calm, and the position has room to speak.
Design the Three Feedback Channels Together
Visuals, sound, and haptics can each be tuned correctly in isolation and still feel wrong together. The stone appears, but the sound comes half a beat late. Or the vibration fires first, while the board has not changed. Perception reads these misalignments as lag, even when the software itself is smooth.
Think of a move as a small beat. At the moment of contact, the stone should immediately occupy the point. A very brief haptic confirms it at the same instant. The sound should cling closely to the stone’s arrival. The sequence is not flashy, but it lets your finger, ear, and eye say the same thing.
Different Positions Need Different Weight
Using the same feedback for every move looks clean, but it also flattens the information. An ordinary move, a five-in-a-row, an invalid point, and a timeout loss carry different weight in the game. Their feedback should carry different weight, too.
For example, an ordinary move can get only a light tap and a short sound. When a five-in-a-row is made, the win-loss cue can be a little more apparent, while still staying contained. An invalid point is best served by a crisp, brief response that says you cannot play there. The point is not to manufacture reward. It is to reduce the cost of explanation.
Layering also has to account for frequency. Feedback that happens on every move must be light. Only occasional signals earn the right to be stronger. Android’s principle puts it clearly: the more frequent the event, the more restrained the haptic should be.
Let Players Turn It Off
Haptics and sound both cross private boundaries. Some people like the sound of stones. Some play only in silent mode. Some find a light vibration helpful for confirming the point. Others find vibration breaks their concentration. A refined board should allow those differences to exist.
In settings, sound and haptics should be separated. Do not hide them behind one master switch, and do not let turning feedback off remove game information. Win or loss, whose turn it is, forbidden moves, and invalid points should all remain legible through clear visual states.
When move feedback is done well, you may not praise it. When it is crude, it reveals itself within a few turns. In your next game, watch just one thing: when each stone lands, do you keep reading the board, or do you first check whether the phone understood you?