How To: Gaming
THE HOW TO CO. — EDITION 10
Two phone families, built by people who disagreed about almost everything. The part of that argument which reaches your thumb is far smaller than either side would like.
Both of them are just a lit thing on the end of a string. The frame is the argument. The light is the game.
iOS takes games from one channel. Android will let you say yes to others, once you switch that on. The real question underneath it is who gets to make the mistake.
iOS runs on a short list of devices from one designer. Android runs on nearly everything ever built — which is why “it runs fine on Android” is a sentence about somebody else’s phone.
Both cut short work left running behind another app, by different rules, and on Android those rules shift again by maker. Never assume a long download finished while you were elsewhere.
Studios build one game and hand it to both. Content, balance and the shop belong to the people who made it, not to the phone. Where the two differ it is release order, and it closes.
Every phone turns a demanding game into warmth, then quietly slows itself to survive it. No family is exempt, no setting switches it off, and it arrives long before the battery does.
Anything that asked you to sign in keeps your progress with that sign-in; anything that did not keeps it on the handset. The line falls in the same place on both.
Neither of the two lines above decides whether a game is good on your phone. These two do, they are identical on both families, and they are why people quit games they were enjoying.
The install is a down payment. A live game keeps arriving long after you installed it and never shrinks back, so the day you got it is the lightest it will ever be. Decide now what you are willing to delete; the phone will ask at the worst moment.
The empty battery is not the interesting half. The phone warms first and slows itself on purpose to stay safe, so a long session gets worse before it ends. Charging while you play pushes both the same way at once.
The screen is the controller and also the thing you are trying to see. That costs both families exactly the same.
Two fingers cover the lower corners of the screen you are reading. Anything urgent that lives under them gets lost in a fight, never in a menu.
A game built for a thumb has fewer things to press than a game moved onto one. Ported controls announce themselves as a ring of small circles.
Both take one, and the moment you attach it most of the argument above stops mattering. Buy the stand first: holding the two together is the actual problem.
The question was never whether a phone can run it; phones run more than people expect. It is whether the game survives being interrupted. Anything that punishes you for stopping sits badly on a device whose other job is being a telephone, and the tell is always the same: you notice you have started refusing to answer things.
“Pick the one you actually like holding. It predicts how much you will play far better than anything either side prints on a page.”
