Made with Nano Banana 2 Lite · CC0 · 8 Oct 2026

Flat colour

Generated from: a scene from a small video game about: Build a polished playable prototype of a mobile game called Table Tap. The priority is the gameplay prototype first. Do not build menus, settings, accounts, matchmaking, progression, cosmetics, shops, or other systems yet. I want to play the core game immediately and judge whether it is fun. Core concept Table Tap is a fast reaction game based on the physical table-tapping game where players sit around a table with their hands alternating around the table. Translate that physical experience into a mobile touchscreen game. The game should feel like looking down at a wooden poker table from directly above. Players have two hands/thumbs positioned around the edge of the table. For the first prototype, create a simulated multiplayer table with several opponents controlled by AI. The player's two thumbs/hands should be represented at the bottom of the table in natural positions for a player holding a phone with both hands. Core gameplay The table contains an ordered sequence of active hands. A tap travels around the table in one direction. When it is a hand's turn, that hand must tap. After a normal single tap, play continues to the next active hand in the current direction. A double tap reverses the direction immediately. The next tap must therefore come from the hand in the opposite direction. This is the central mechanic. The player must react to the changing sequence without panic-tapping. Losing a hand A hand is eliminated if: It taps when it is not that hand's turn. It fails to tap before the allowed reaction time expires. Remove the eliminated hand visually from the table. The player can therefore lose one hand while their other hand remains alive. The game ends when only one hand remains. The player wins if one of their hands is the final surviving hand. Timing The timing should be central to the game. Do not make the game depend on complicated mechanics. Start with a comfortable reaction window. As the game continues, gradually reduce the reaction window when the table is not producing enough mistakes. The purpose is to increase pressure naturally. The game should feel like: calm → faster → tense → chaotic → mistake. Do not make the acceleration so aggressive that it feels random or unfair. There should always be enough time for a skilled player to react. Double taps A double tap should be deliberate and readable. A single tap passes the sequence. A second tap from the same active hand within a short double-tap window reverses the direction. Make the reversal visually obvious for a brief moment so the player immediately understands that the direction has changed. Do not add special buttons for reversing direction. The double tap itself is the mechanic. AI opponents Use simple AI opponents rather than complicated strategy. The AI should behave like human players with different reaction speeds and occasional mistakes. AI difficulty should affect: reaction time consistency chance of making an incorrect tap willingness to trigger double taps ability to react correctly after a reversal The AI should not feel perfectly predictable. Importantly, AI mistakes should look believable rather than random. Some opponents should occasionally panic and tap early. Some should be slightly slow. Some should be very reliable. Difficulty Include only three difficulty levels for now: Easy slower timing forgiving reaction window more AI mistakes Normal balanced timing moderate AI skill Hard faster timing smaller reaction window more competent AI more frequent rapid reversals Keep the rules identical across difficulties. Only change the pressure and opponent skill. Visual direction Make the prototype feel like a real game from the first build. Use a bird's-eye poker-table composition. Visual style: warm wooden table subtle poker-table/felt influence clean circular or oval playing area hands positioned naturally around the table strong but restrained lighting subtle shadows tactile tap feedback polished mobile-game presentation no clutter The table should occupy most of the screen. The player should immediately understand: where their two hands are which direction play is moving whose hand is currently expected to tap when the direction has reversed which hands are eliminated Use subtle visual indicators rather than large UI overlays. The physical table should remain the visual focus. Touch interaction Design specifically for a phone held with two hands. The player's two tap areas should sit naturally toward the lower left and lower right portions of the screen. Make the touch areas forgiving enough that the player does not need to hit a tiny target. The player should be able to tap naturally with their thumbs. Do not require swipes, dragging, menus, or complicated gestures. The only important interaction is: tap / double tap Feedback Make every tap feel satisfying. Use subtle: tap animation sound vibration/haptic feedback where supported direction-change feedback elimination feedback win/lose feedback A successful tap should feel slightly different from an invalid tap. A double tap/reversal should feel particularly clear and satisfying. Keep the feedback fast. Nothing should interrupt the flow of play. Game pacing Get the player into the action immediately. The prototype should start with a short setup/countdown and then begin. Avoid tutorials during the actual game. The rules should be understandable simply by watching the first few taps. The first round should be short enough that the player immediately wants to try again. Prototype UI For this first build, only include the minimum UI required to play: difficulty indicator subtle reaction-time/tension indicator if useful restart button simple win/lose result Do not build the final main menu yet. Do not build account systems. Do not build online multiplayer yet. Do not build player customization yet. Do not build progression yet. Important design principle Do not overdesign the game. The fun comes from the extremely simple rule becoming increasingly difficult: Tap when it's your turn. Then: Don't panic tap. Then: Don't miss the reversal. The player should gradually get faster and more nervous as the table speeds up. The game should create its own excitement through timing, mistakes and reversals rather than through additional mechanics. Build priority Functional tap sequence Correct turn tracking Double-tap reversal Individual hand elimination Reaction timer AI opponents Increasing speed Win/lose detection Polished table presentation Tap/audio/haptic feedback Make the first playable version quickly. Once the core game is working, polish the presentation rather than adding more features. The finished prototype should feel like a simple, addictive 30-second-to-several-minute reaction game, not a complicated board game. Most importantly: make it fun to play before making it feature-rich., as an in-game screenshot in flat colour 2D shapes with a bright limited palette. Palette: sky blue #8ecae6, grass #3a7d44, player sunflower #ffb703, threat red #d62828, accent white #fdfcdc. Everything is original: never draw or resemble characters, places or logos from existing games, films or brands (no red-capped plumbers, no famous mascots), even when the idea names one. Keep the pictures honest: they promise what a small first version of this game, made in a game engine in a few days, can look like. Simple readable shapes, clear silhouettes, few flat materials, the in-game camera view. Never film stills, photoreal renders, AAA key art, detailed textures, cinematic lighting, or anything that looks like a big-studio game. No text, UI, HUD, logos or editor screens inside any image.