Steam Next Fest is over, or close enough to over that the tabs start closing themselves. The demos you meant to try are gone from your evening. The wishlist has a few new names on it. Maybe a few dozen. Somewhere in there is a game you genuinely cared about for twelve minutes, and unless you wrote down why, there is a decent chance it will blur into the next showcase, the next sale, the next tidy grid of capsule art.
That is the part of showcase season I keep thinking about. Not the trailers. Not the lists. The aftertaste.
Steam's own Next Fest page describes the event plainly: a week of free demos, developer livestreams, and chats for upcoming games. That is useful. It is generous, even. The June 2026 round has also been loud enough to fill YouTube with recommendations, from Noclip's wishlist picks to Best Indie Games trying to wrangle one hundred demos into a watchable shape. The signal is there. The problem is what happens after the signal hits you.
A wishlist remembers that you clicked. It does not remember what you felt.
The wishlist is good at buying, not remembering
I do not mean that as an insult. A wishlist has a job. It catches games before they vanish from view, reminds you when they release, and gets involved when the price drops. For a store, that is exactly the right shape. It is practical. It is clean. It helps the platform connect interest to purchase.
But a player's interest is usually messier than that.
During Next Fest, you might play a demo because the art looks strange. You might stop after ten minutes because the combat feels stiff, then keep thinking about the music all night. You might wishlist something you are not sure you even want, because a friend would probably love it. You might bounce off a demo now and know, with annoying certainty, that a different version of you would have adored it five years ago.
None of that fits neatly into the button.
The store remembers the transaction-shaped part of the moment. It knows that the game moved from unknown to saved. It does not know whether you wanted to support a tiny studio, whether you liked the premise but hated the camera, whether you only added it because you were afraid of forgetting the name. It definitely does not know that you played the demo late on a Sunday when you were tired and a little impatient, which is sometimes the worst possible way to meet a slow game.
That missing context matters because games take time. A movie you half-remember can be recovered in an evening. A game you half-remember might ask for thirty hours, a controller, a desk, and some emotional availability. The more games we save for later, the more useful it becomes to remember why we saved them at all.
Next Fest turns curiosity into a queue
The June 2026 research was funny in a familiar way. The official framing is open and celebratory: try demos, watch developers, discover upcoming games. The creator layer immediately turns that abundance into survival guides. There are videos for essential wishlists, cozy demos, strategy demos, FPS demos, weird demos, RPG Maker demos, and all the rest. That is not a criticism. I watch those videos too. They are useful because nobody can play everything.
Still, the pattern says something. Discovery has become its own chore. We need people to filter the filters.
This is where the backlog starts to feel less like a shelf and more like a receipt. A demo catches your attention, so you wishlist it. A video tells you not to miss another one, so you wishlist that too. A friend mentions a third. A sale adds pressure. The list grows, but the feeling that started the whole thing gets thinner each time you add one more item without a note attached.
I think this is why so many players ask for some version of "Letterboxd for games." They are not only asking for another database. We have databases everywhere. They are asking for a place where play can be logged in human terms: what I tried, what I finished, what I quit, what I still think about, what I want to come back to when the mood is right.
That phrase gets thrown around because Letterboxd made movie watching feel recordable without making it feel corporate. Games need their own version of that idea, but they cannot copy it exactly. Games have platforms, saves, patches, achievements, multiplayer seasons, early access builds, demos, backlogs, abandoned runs, and the weird category of "I loved this but will never finish it." A game journal has to make room for all of that without turning into project management software.
The trick is not to make players more productive. I do not want an app that scolds me into clearing a queue. I want one that helps me keep the thread.
A game journal should keep the small reasons
The best notes are often embarrassingly small.
"Loved the door sound."
"Too tired for this today. Try again later."
"Feels like something Sam would like."
"Combat is not for me, but the town is perfect."
Those notes will never look impressive in a year-end graphic. They are not reviews, exactly. They are not recommendations either. They are breadcrumbs. When you come back months later, they explain your own taste to you in a way a star rating cannot.
A star rating is still useful. A proper review is useful too. I like reading why someone gave a game five stars, and I like reading why someone gave it two. But a lot of our relationship with games happens before the rating and after the credits. It happens in the soft middle, when a game is a possibility, a habit, a stalled promise, or a private little obsession.
This is the part most tracking systems flatten. They ask whether the game is completed, playing, dropped, or planned. Those labels help, but they are only the spine. The living thing is the note beside the label.
That is especially true for demos. A demo is not a finished judgment. It is a first meeting. Sometimes it tells you everything. Sometimes it tells you almost nothing except that something is there. If you only wishlist it, you preserve the name. If you write down what caught you, you preserve the reason.
There is a difference.
Where Perthro fits
Perthro is built around that quieter record. It is an iPhone-first social gaming journal, currently in TestFlight beta, for tracking the games you are playing, have played, plan to play, or shelved. You can rate games on a five-star scale, write reviews of any length, keep a backlog and wishlist with reordering and a next up view, and make custom lists for whatever shape your taste takes.
That matters after something like Next Fest because a simple list fills up fast. A better list lets you sort the noise into something you can actually return to. Maybe one demo goes into the wishlist because you want it on release day. Another goes into a custom list called "strange little Steam demos." Another gets shelved, not because it was bad, but because it needs a mood you do not have this month.
Perthro also has friends and a feed, which is the part I care about more than I expected. The best game recommendations rarely arrive as content. They arrive as one person saying, "This made me think of you." Seeing what friends are playing, rating, reviewing, reacting to, or quietly saving for later can carry more weight than another ranked roundup. Not because roundups are bad. Because taste is personal, and the best filters usually have names.
That is the useful version of social. Not a scoreboard. Not a performance. Just enough presence to make the record feel alive.
The point is not to finish more games
Backlog talk gets grim when it borrows the language of work. Clear the backlog. Beat the queue. Optimize your play. I understand why that happens. There are too many good games, too many subscriptions, too many sales, too many unfinished saves sitting there with quiet judgment in their eyes.
But the healthier question is not "How do I finish everything?" You will not. Nobody will. The better question is "How do I remember what mattered enough to come back to?"
That question changes the tool you need. A release calendar can tell you what is coming. A storefront can tell you what you saved. A platform library can tell you what you own, at least on that platform. A game journal can tell you what was happening between you and the game.
It can remind you that you added a tiny detective game because the writing made you laugh. It can remind you that you stopped playing a strategy demo because the tutorial was heavy, not because the idea was weak. It can remind you that your favorite thing at Next Fest was not the most polished trailer, but the one with the ugly menu and the perfect little fishing minigame.
That kind of memory is not important in the grand sense. It will not fix discovery or save the industry or solve the flood of releases. It just makes your own play feel less disposable.
That is enough.
Keep the reason, not just the title
If you came out of Steam Next Fest with a swollen wishlist, leave it alone for a night. Then go back and ask a smaller question for each game you still recognize: why did I care?
If the answer is clear, write it down somewhere. If the answer is gone, maybe the game can go too. That is not failure. That is taste doing its job.
The internet is very good at helping us find more games. It is less good at helping us keep a gentle, honest record of why any of them mattered. A wishlist catches the title. A journal catches the thread.
When the next showcase arrives, and it will arrive soon, you will be glad you kept the thread.