Reading Enemy Fire: How to Actually Get Good at a Space Shooter
How to read enemy fire instead of reacting to it, when to spend each ability, and what separates a fair bullet pattern from a cheap one.
36 articles
Every article we have published on Action & Arcade — how these apps work, the decisions behind them, and where their limits are.
Short sessions are the point of these games, so most of the articles are practical: reading enemy fire in a shooter, countering armoured and flying waves in tower defence, what bots change in an io arena, and what "offline" really means for an Android game.
A few step back to definitions — what makes a roguelike, how bullet hell differs from a classic shoot-em-up — because the genre labels on a store page rarely explain themselves.
Covering 5 apps in this category.
The articles in this category that other articles link to most often.
How to read enemy fire instead of reacting to it, when to spend each ability, and what separates a fair bullet pattern from a cheap one.
Why bosses are memory tests rather than reflex tests, how to learn a rotation efficiently, and why players die at the same phase repeatedly.
Why the upgrade you skip matters as much as the one you take, how auto-fire makes movement the whole skill, and how to push a run deeper.
Most io-style arenas are populated by AI, not people. What that changes about how a run starts, how rivals behave, and how to read the field tactically.
A boss with destructible modules is several targets, not one. Why the order you destroy them in decides how much damage you take, with the arithmetic.
Build Pads add tower slots on valid terrain away from paths, towers, auras and the castle. Where a new position earns its cost, and when to skip it.
Grinding an endless run feels productive and often is not. What motor-learning research on practice schedules suggests about choosing a mode when you are stuck.
Reaching the top of a live io leaderboard inverts your incentives: rank can no longer improve, only fall. How to play the lead instead of playing for it.
In a momentum steering model you set a heading, not a position. Turning radius, interception geometry and the arcs that keep you alive in a snake-style arena.
Two same-studio space shooters with near-identical names and genuinely different designs. A structured comparison of modes, ships, bosses and upgrades.
Pinch, pan, saved presets and follow mode are strategy tools. How to work a tower defence camera so you can actually see what is beating you.
Late waves mix armoured, flying and elite units before a world boss. Why the fix is usually rearranging the layout you have rather than adding to it.
Support towers that buff neighbours turn layout into a real decision. How aura stacking works, and why we capped it the way we did.
Mixed waves punish a single-answer defence. How armour, flight and elite modifiers change what damage gets through, and how to plan for all three.
Mid-size is the dangerous size: big enough to be hunted, too small to hunt back. Route choice, cut-off angles and when to feed quietly.
Most io games need a server. The ones that work offline replace players with AI, and that changes the pacing in ways worth knowing about first.
What separates a tower defence game that works offline from one that only pretends to, and the trade-offs that come with playing without a connection.
Damage feels good and rarely helps first. Why survivability and cooldown upgrades usually outperform raw firepower in the early sectors.
Difficulty modes usually change more than enemy health. What each tier alters, and how we decided where the line between them should sit.
Good tower defence is a geometry problem before it is a damage problem. How to read a path, find the long lanes, and spend where time is longest.
Arrow, cannon, frost, flame, lightning, siege and chaos towers do different jobs. What each is good against and where each one is wasted.
Vertical scrolling shooters live or die on pattern readability and control feel. What to check before committing to one on a phone.
The io label came from a domain suffix, not a genre. What the games usually have in common, and what the name tells you about how they play.
TD is short for tower defence, but the abbreviation collides with several others. What it means in a game title and how the genre is defined.
Why touchscreens are bad at some inputs and good at others, what auto-fire actually solves, and how control design decides which skill a game tests.
Why games drain batteries, what thermal throttling actually does to frame rate, and the settings that make the largest difference on a phone.
Why some arcade games stall the moment you lose signal, what the Play listing does and does not tell you, and how to test any game yourself.
Why bosses are memory tests rather than reflex tests, how to learn a rotation efficiently, and why players die at the same phase repeatedly.
How arcade games escalate, why the classic curve was shaped by coin-operated economics, and what a difficulty curve has to do to stay fair while getting harder.
From a 1962 lab experiment to danmaku, how the shoot 'em up changed across five decades and why its central question never moved.
Two escalation structures that look similar and play differently: continuous pressure with mid-run builds versus discrete waves with pattern learning.
Why a good upgrade offer is a decision rather than a reward, how synergies create build identity, and what makes an upgrade choice genuinely interesting.
How scoring systems change optimal play, why risk becomes a resource, and the specific habits that separate a survival player from a scoring player.
How wave survival games build tension: escalation curves, spawn placement, the pause between waves, and why more enemies is the weakest lever.
Rogue, the Berlin Interpretation and the roguelite split: what the word means, why the definition is contested, and a test that settles it.
How free apps are funded, what the different ad formats cost you in attention and data, and what Google Play's policies require of developers.
Bullet hell and classic shoot 'em ups look alike and reward opposite instincts. Hitboxes, bullet speed, and why density is not difficulty.
How to read enemy fire instead of reacting to it, when to spend each ability, and what separates a fair bullet pattern from a cheap one.
Why the upgrade you skip matters as much as the one you take, how auto-fire makes movement the whole skill, and how to push a run deeper.