Why Glydra uses relative-drag control
The control scheme is the whole game. Here's why we threw out the obvious option and built Glydra around your finger instead.
When you're making a one-touch arcade game, there's a temptation to treat the controls as a solved problem. Tap, swipe, drag. Pick one and get on to the fun stuff. We learned the slow way that for Glydra, the controls were the fun stuff. Get them wrong and nothing else matters; the orbs, the biomes and the combos all sit on top of how the ship feels under your thumb.
So before building anything else, we spent an embarrassing number of evenings on a single question: how should the ship move?
The obvious option that didn't work
The first thing we tried was absolute touch, your finger is the ship. Wherever you press, that's where it goes. It sounds intuitive, and for about ten seconds it is. Then two problems show up. Your thumb covers the exact slice of screen you're trying to read, and every time you re-place your finger the ship teleports across the screen. In a game about threading narrow gaps at speed, a teleport is a death you never asked for.
Following the finger instead of chasing it
What shipped is relative drag. The ship doesn't jump to your finger; it follows how far you slide from wherever you first touched. Lift and re-press anywhere and nothing snaps, you just keep steering from the new spot. It's the difference between pointing at where you want something and nudging it there. The ship glides, it never jumps, and your thumb can sit in a corner well clear of the action.
The trade-off is honest: there's a five-second learning moment. On your first run you'll probably overshoot a gap or two while your hand calibrates. By the third run you've stopped thinking about it, which is exactly where a one-touch game wants you.
Tuning the feel
Most of the work was invisible. How much ship movement per millimetre of slide? Too sensitive and it twitches; too slow and tight gaps feel unfair. We added a little smoothing so a shaky thumb doesn't read as a shaky ship, but not so much that steering feels like wading through syrup. There's no "correct" number here. It's a feel you chase by playing the same thirty seconds a few hundred times until it stops annoying you.
Why it makes the rest of the game work
Precise control is what lets the other systems be demanding. Chaining orbs for a combo up to 4x only feels fair because you can actually steer onto each one. Skimming a wall for a slow-mo near-miss is a thrill instead of a frustration because you trust the ship to go exactly where you put it. Even the power-ups, a Shield that eats one hit, a Magnet that pulls orbs in, assume you're in control enough to use them on purpose.
A one-touch game lives or dies on a single verb. For Glydra that verb is "glide", and glide only works if the ship never betrays you.
If we'd kept the teleporting controls, we'd have had to make the world more forgiving to compensate, and a forgiving arcade game is a boring one. Building around relative drag let us keep the gaps tight and the speed honest.
It's the least glamorous decision in the whole project and the one we're most glad we got right. Next time something feels good in the hand, it's worth asking what boring problem someone quietly solved to get there.