Boss Bounce
Hold to charge a giant pixel soldier, release to launch him through goblin lines; every bounce spawns more troops until the swarm buries the king.
Hold to build charge; release sends a giant ricocheting through goblins, each hit multiplying troop count.
Hold to charge, release to fire.
Swarm-rally auto-battler with bounce physics.
itch.io page advertises 'auto-battler' and 'incremental' tags with a one-button control scheme; comments asking for skill trees suggest strong engagement.
Swarm+ricochet mashup is a reasonable hook, but the source proof-of-concept is a 1-day-old itch demo with only 9 ratings and 4.2 stars — no proven audience yet.Swarm The Throne v0.0.1 page — 9 ratings, freshly published, idle/auto-battler not a hold-charge bouncer. ↗
Bounce moments are inherently shareable, but the source trend has near-zero social traction (no TikTok/stream hits, single dev, no chart presence) and the mobile idle/auto-battler space is dominated by Survivor.io/Idle Slayer class hits.Hypercasual scale benchmarks show virality requires a breakout hook — this combo has none yet. ↗
Genuinely one-button hold-and-release, pixel art, single scene — comparable one-button hypercasual prototypes ship in days on itch.io.itch.io one-button hypercasual tag shows dozens of similarly tiny-scope prototypes, indicating the build is trivial. ↗
Idle/incremental mobile monetization (rewarded ads for x2 prestige, skip timers) is proven, but a bounce-ricochet loop with troop multiplication has no demonstrated ad-format fit and no comparable revenue benchmark.AppMagic Q4 2024 trends indicate rewarded video + interstitial dominate, but this specific bounce-swarm combo isn't in any reported top performer. ↗
The hold-to-charge ricochet x swarm multiplier angle is a fresh mashup, yet one-button bounce games and idle auto-battlers are individually crowded segments — moderate whitespace at best.Existing 'One Button Bounce Game' shows the bounce-side is saturated, capping whitespace for that primitive. ↗Swarm/auto-battler itch space is busy with similar tiny prototypes, suggesting limited whitespace even before mobile port. ↗