Tater Dash (formerly FlappyTot)

Purpose

Started as FlappyTot — a Flappy Bird clone with a potato. Evolved into Tater Dash: instead of just flapping to survive, you swipe to dash-attack enemies (birds, beetles, rogue spuds) while a wall of potato blight chases you from the left. Stop moving and the blight consumes you. It is an endless runner meets Flappy Bird meets a produce section nightmare.

Stack

What I Learned

• SpriteKit is Apple's native 2D game framework — physics engine, particle system, sprite rendering, and scene management built into iOS. For a game like Tater Dash (2D, side-scrolling, physics-based), SpriteKit is the right tool: native performance, no third-party dependencies, and deep integration with iOS (Game Center leaderboards, haptics, system audio).
• The evolution from FlappyTot (pure clone) to Tater Dash (original mechanics) mirrors the Adobe CC lesson from bootcamp: copy to learn, then diverge. Flappy Bird was the starting template. The swipe-to-dash attack, the enemy variety, and the blight mechanic are what made it a different game. The clone got the physics and scrolling working. The original mechanics made it worth releasing.
• The blight mechanic (a wall of darkness advancing from the left) solves the pacing problem that many endless runners have: without it, a skilled player can play forever at a comfortable pace. The blight forces constant forward movement — you cannot hover, cannot rest, cannot wait for the perfect moment. It is the game design equivalent of a deadline. Constraints create urgency.
• Enemy variety (birds, beetles, spuds) with different movement patterns keeps the game from becoming repetitive. Birds float in sine waves. Beetles march in straight lines. Spuds bounce unpredictably. Each requires a different timing for the dash attack. Pattern recognition under time pressure — the same skill the falling-object games test, but with the added dimension of attack vs. avoid.
• This was the first game deployed with raw iOS/Swift code (not Flutter/Flame). The SpriteKit experience was valuable: understanding Apple's native game framework means understanding the platform at a deeper level than any cross-platform wrapper provides. Tater Dash feels native because it IS native.

Key Insights

• Tater Dash appearing in the Google search results for "Brett Owers" (visible in the App Store listing on the screenshots) is one of the strongest SEO signals connecting the personal name to the Potatuhs brand. A game called "Tater Dash" by a developer named "Brett Owers" — the potato connection is impossible to miss. This is the kind of organic brand association that no amount of meta tags can replicate.
• The FlappyTot → Tater Dash rebrand is a branding lesson: generic clone names (FlappyTot, FlappyBird clone #47,000) are invisible. Brand-aligned names (Tater Dash) are discoverable and memorable. The name change did not change the code. It changed the identity. The product is the same. The brand is different. The brand is what people remember.
• Releasing a game on the App Store with raw Swift (instead of Flutter) was a deliberate choice for this specific game: SpriteKit's physics, the native performance, and the App Store optimization (ASO) advantages of a native app. For Hot Potato Games' catalog, some games will be Flutter/Flame (cross-platform, faster development) and some will be native Swift (tighter platform integration). The right tool depends on the game.
• Tater Dash being the first Potatuhs game on the App Store is a milestone the same way Explore The Cell was the first app ever deployed. First games, like first apps, are never the best. They are the ones that prove the pipeline works. Tater Dash proved that Hot Potato Games can ship a game to the App Store. Everything after it — Burlap Sacker, Hot Potato, Tenlach — builds on that proof.