Why We Built a Mobile Game With No Login Required

When you open Eat a Mile for the first time, here's what happens: the game starts. There's no account screen, no "sign in with Apple," no email field, no password to invent and then forget. You tap the icon and the coin is already rolling. I've had a few people tell me they assumed something was broken because the login screen never showed up. It wasn't broken. There just isn't one, and there never will be.

I want to explain why, because skipping the login wasn't a corner I cut to ship faster. It's one of the first decisions I made, and almost every other choice in the app follows from it. Once you decide a game shouldn't have accounts, a lot of the usual mobile-game machinery simply has nowhere to live.

What a login screen is actually for

Most games don't ask you to log in because you need to. They ask because they need to. An account is the hook that ties everything you do back to a row in a database. Once there's a row with your name on it, the studio can sync your progress to a server, sure — but it can also build a profile, attach your purchases to an identity, email you when you stop playing, and match you to the same person across their other apps. The login screen is sold as a convenience. Mostly it's a collection point.

Think about how many free games ask for an email or a social sign-in before you've even seen the gameplay. You haven't decided you like it yet, and you're already handing over a way to be contacted and tracked. That trade gets normalized so early that most of us stop noticing it. I noticed it, mostly because building the alternative made it obvious how little the account was doing for the player and how much it was doing for everyone else.

You can't lose what you don't ask for

A game with no accounts can't leak your account, because there isn't one. There's no user table to breach, no password to reuse badly, no email list for someone to walk out the door with. When a studio gets hacked and millions of player records spill out, that only happens because the records existed in the first place. Eat a Mile keeps your scores, your earned characters, and your settings in your phone's local storage. Not my servers — I don't have a player database. Just your device.

This is the part people find slightly hard to believe, so I'll be plain about it: I genuinely do not know who plays this game. I can't tell you how many accounts exist because none do. That feels strange to say as a developer, and it took some getting used to. But it's the honest version of "privacy-first." You can't promise not to misuse data you never collected.

The safest place to store someone's data is on their own phone, where I can't see it, can't sell it, and can't lose it on their behalf.

No login means it works on a plane

There's a practical payoff too. Because nothing about the game depends on an account, nothing depends on a network connection either. Eat a Mile runs fully offline. On a plane, on the subway, in a dead zone, on a kid's hand-me-down phone with no SIM card — it plays exactly the same. No "you must be online to continue," no spinner waiting on an auth token, no session that quietly expires while you're mid-run.

I think we've collectively forgotten that a game can just be a thing on your device. So many "mobile" games are really thin clients pointed at a server, and the moment that server has a bad day, your game does too. A single-player arcade game has no business needing a round trip to a data center every time you want to dodge a pothole. So mine doesn't.

The engagement traps go with it

Here's the part I didn't fully appreciate until later. When you have accounts, you get the ability to nudge. Daily login bonuses, streaks you'll lose if you skip a day, push notifications timed to drag you back, limited-time events that punish you for having a life. All of that needs to know who you are and when you last played. Strip out the account and those levers stop working, because the game has no memory of you between sessions beyond what's sitting on your own phone.

I'm fine with that. I don't want to build a slot machine that's stressed about its retention numbers. I don't even have retention numbers — no analytics, remember. Eat a Mile doesn't beg you to come back. If you put it down for a month and pick it up again, it's the same calm game it was, waiting where you left it, with no guilt-trip notification in between. That's the version of mobile gaming I actually want to use.

The one honest tradeoff

I won't pretend there's no cost. The real downside of no accounts is that your progress lives on one device. Get a new phone and your high scores don't automatically follow you. I think that's a fair price, and I'd rather solve it later with something like an exportable backup file you control than by standing up a server that quietly becomes a profile of you. A login screen would "fix" the new-phone problem, but it would do it by reintroducing every single thing I built this game to avoid.

So when the game opens straight into play and you wonder where the sign-up went — that empty space is the whole point. It's a road, a coin, and a head that wants to bounce. You don't need an account for that, and I'm never going to ask you for one.