DevLog #005 — Nothing Left to Build
For months, every day had a clear objective.
Fix a bug. Polish a screen. Improve onboarding. Reduce crashes. Pass Google’s Closed Testing.
Then, two days ago, I submitted the app for production review — and suddenly found myself with nothing left to do.
Not because the project was over, but because, for the first time, it was out of my hands.
Before that, there was always something to do. Check Crashlytics. Reply to a tester. Rebalance the leaderboard. Chase down a billing bug. Now there’s one thing left:
Refresh.
Refresh.
Still “In review.”
I don’t think this is unique to me. It seems to be a common ritual among indie developers — refreshing the Play Console, knowing full well nothing has changed.
I used to think shipping an app meant writing the last line of code. It doesn’t. Shipping means stopping — deciding, on purpose, that this version is good enough, and then not touching it. That turned out to be harder than any bug I fixed this year.
Waiting isn’t the end of development. It’s the beginning of learning whether any of it mattered. Closed Testing was Google checking the app. Production is where the app finally meets people who owe me nothing.
The first real player. The first one-star review. The first piece of feedback that isn’t from someone I recruited. The first dollar. The first player who comes back a second day.
Sudoku Fog is no longer sitting on my computer. It’s somewhere inside Google’s review system. For the first time in months, I can’t improve it with another commit.
The next commit won’t be mine.
It’ll come from player feedback.