poppivoPoppivo is planned as an immediately playable feed of portrait games. A game should be ready to interact with when it comes into view. Tap and horizontal game inputs belong to that game; a fresh vertical browsing gesture belongs to the feed, including while an attempt is underway.
That creates a specific design problem. At the instant a finger touches the screen, the interface may not yet know whether the person intends to tap, drag within the game, or swipe to another game. The first moment of contact cannot safely commit to all three.
Keep vertical browsing available
A fresh vertical swipe must continue to mean browsing throughout the collection. Starting a game should not take that gesture away from the feed. The player should be able to move on without finding a separate exit screen or passing through a required play button.
This gives game controls a useful constraint. Their tap and horizontal actions need to fit around vertical navigation. A game that requires a fresh upward drag for its main action would create a conflict with the collection’s browsing rule. That conflict needs to be resolved in the control design before the game joins the feed.
The distinction also needs to hold during rapid play. A vertical swipe after a series of taps is still a browsing gesture. The game should not assume that every new touch belongs to it because the previous touches did.
Recognize the gesture before committing an action
A finger rarely follows a perfectly straight path. The initial contact can include a small amount of motion before the person’s intent becomes clear. The interface needs enough room to distinguish a tap from deliberate horizontal or vertical movement.
Until that classification is clear, the game must not fire a shot, spend a resource, or commit another irreversible move. An early touch response can acknowledge contact if it is reversible, but it cannot quietly decide that an unresolved touch is already a gameplay action.
A fresh vertical gesture should produce navigation without a stray shot or move underneath it. A classified tap or horizontal game gesture can then produce the intended game response. The touch used to bring a game into view must not leak into that game as its first action.
Once a gesture has a clear owner, its remaining events need consistent handling until it ends or is canceled. The next fresh touch gets its own classification. This avoids changing ownership casually halfway through a movement or carrying the previous gesture’s decision into a new one.
Treat cancellation as its own outcome
A canceled touch is different from a completed tap. Someone might interrupt the motion, an operating-system gesture might take over, or the phone might interrupt the app. None of those cases should accidentally trigger an action that was waiting for a normal release.
Any temporary response to an unresolved touch needs to be cleared when it is canceled. If browsing interrupts an attempt, returning to that game should make any pause or reset understandable. The player should not have to guess which part of the earlier interaction survived.
Screen edges deserve a separate review because the phone also uses gestures there. Important game actions should avoid competing with the operating system’s navigation. Testing only in the middle of the screen would miss that part of the experience.
Explain the input without adding a gate
A short instruction can tell the player which tap or horizontal action the visible game accepts. It can sit alongside an immediately playable game, so understanding the control does not require a separate entry step.
Browsing also needs a discoverable alternative for someone who cannot comfortably swipe. A visible navigation control can supplement the gesture while leaving the game ready to play. It should stay clear of the area used for repeated game inputs.
For a feed like this, I would review these cases deliberately:
- Start a fresh vertical swipe during an active attempt and check that no game move is committed.
- Begin with a slight diagonal motion, then continue vertically.
- Tap after browsing and check that only the new tap reaches the visible game.
- Cancel an unresolved touch before lifting normally.
- Finish a horizontal game gesture, then begin a new vertical swipe.
- Try the same actions near system-navigation edges.
- Use the visible browsing control without a swipe.
The intended result is simple to describe: the game in view is ready for play, and a fresh vertical swipe is always a way to browse. The input handling has to preserve both parts of that experience.