04 / iPhone & iPad · Native app
One screen for the whole game
A native iPhone and iPad app that puts the live game, the fan conversation, highlights and news on one screen.
- Status
- In testing
- My contribution
- Product direction and build, with Hermes, my AI agent

Can one screen replace the five apps I had open?
Design mockups, not screenshots. The teams, logos, players, handles and scores are made up.
Five apps for one game
Following a game used to mean five apps and a lot of switching. A scores app for the score. Reddit for the game thread. A browser for the fan blogs and the news. YouTube for the goal I just missed. By the time I got back to the conversation, it was a step behind, or it had already spoiled the next thing.
I wanted one place for all the info instead of multiple apps. That is the whole idea.
What is on the screen
Crowd Noise is a native iPhone and iPad app, built in SwiftUI. One screen holds the live score and plays, the fan conversation from Reddit game threads, fan blogs, YouTube highlights, and the news. There is also "Feel the room", a quick read of the crowd's mood drawn from Reddit and Mastodon.
Two features are for the games I miss. The spoiler shield hides the score until I ask for it. Catch me up gives me the short version before I open the thread.
What is mine, and what is not
I direct the product and build it with Hermes, my AI agent. The scores, threads, posts, videos, and articles belong to the people and services that publish them. The app only brings them together.
There is no backend server behind it, no paid APIs, and no scraping. It costs nothing to run, which matters for something I make for fun.
The decision that matters
"One place" sounds like a reason to add things. It turned out to be mostly about saying no. Every source could have its own tab and its own corner of the screen. If I let them all in, I have rebuilt the five apps inside one, and I am switching again.
So the question for each idea is whether I would look at it during a game. Deciding what not to show has been harder than building what is there.
Before something gets a place on the screen
The questions I ask before a feature goes in.
Would I look at this during a game?
If I would only want it afterward, it does not belong on the live screen.
Does it replace an app, or add one more thing to check?
The point is less switching. A feature that sends me somewhere else to finish the job works against that.
Could it spoil a game I have not watched?
Anything that shows a score or a result has to respect the spoiler shield.
Can it run without a server or a bill?
No backend and no paid APIs are limits I chose. If an idea needs either one, it waits.
Where this stands
Crowd Noise is in testing on TestFlight with friends and family. I built it to use it myself, and that is still the main test: do I open it when the game is on?
The images above are design mockups, not screenshots. The teams, players, and handles in them are made up.