← Writing GameKal

Two products, one calendar

GameKal’s first commit and its first playable build landed on the same day: version 0.1.0, with a home screen, a month view, an Up Next list, settings, reminders and a sample shelf, exported to the web and deployed on Vercel. None of the layout or data came from anywhere else. The idea did, and it came from two products that solve different halves of the same problem.

By the end of this post you’ll have a way to borrow from existing products without copying them: write down what you take, write down what you leave, and let both lists shape the first build.

This post covers the two products, what I took from each, and what I left out on purpose.

The problem

Game releases are scattered across stores. Steam, PlayStation, Xbox, Nintendo and the PC launchers each keep their own lists, and none of them answers the question I actually ask: what is coming out that I care about, and when? A store wants to sell you the next thing. A calendar just needs to tell you the date.

Steam Labs, Experiment 16

Steam once ran an experiment called Personal Calendar: a store calendar of recent and upcoming games, filtered toward what it thought you’d play. The announcement and the discussion threads around it are still up, and the threads are the useful part. People said exactly what they wanted, and what annoyed them.

What I took:

  • A visual calendar of upcoming releases. Dates first, not a ranked feed.
  • A clear “today.” The day you open the app is the anchor.
  • A way to look back. What already came out is part of the story.
  • Filters that belong to the person. The list should be yours, not the store’s.

What I left out:

  • A calendar that only shows weekdays. Games release on weekends too. The month shows all seven days.
  • Recommendations built from playtime on someone else’s servers. Nothing about what you play needs to leave your device to make a calendar useful.
  • A feature you can’t turn off. Anything personalized has to be optional.

Goodreads

The other model is Goodreads. A reader keeps a shelf: what they want to read, what they’re reading, and what they finished, each with a private rating and a note.

That maps cleanly onto games. A tracked game is upcoming, playing, completed or dropped. The rating is private. It’s there to make your own list better, not to become a public review or a playtime profile.

The first build

Read together, the two lists described the first build:

Piece Where it came from
Home, anchored on today Steam Labs: a clear “today”
The month, all seven days Steam Labs, minus the weekday-only view
Up Next Steam Labs: a list that belongs to you
Reminders the question the stores don’t answer: when
A sample shelf a way to see the app working before you’ve added anything

The sample shelf matters more than it looks. An empty calendar explains nothing. A calendar with a handful of real-looking games on it explains itself in a second, so the first build shipped with one you could load and remove.

What I learned

Looking back, three lessons stand out.

Read the complaints, not the announcement. The Steam Labs post describes the feature. The discussion thread describes the product people wanted. Most of my “left out” list came from there.

Write the “left out” list first. It’s shorter, and it’s where the opinions are. “No weekday-only calendar” and “nothing personalized you can’t turn off” decided more of the layout than any sketch did.

Borrow the idea, not the screen. Neither product’s layout, copy or data is in GameKal. What carried over was the shape: a calendar from one, a shelf from the other.

What’s next?

The shelf half of that idea needed its own screen: a journal for what you started, finished or dropped, kept apart from the release dates.

Two products, one calendar, and a short list of things it would never do.

I'm listening if you're talking

A bug, a new build, a data question, a site that needs to be faster or a full rebuild. Tell me what's going on.

Let's see how to collaborate.