INDEPENDENT INDIE INTELLIGENCE

Steam Discovery
5,197catalog apps
60digested stories
2026-09-28source check

THE PC MARKET READING ROOM

Postmortem: The journey of Inkbound through Early Access

64 article notes: 11 HTMAG posts + 47 analyst, practitioner and developer readings. 30 are in the original June–September research window. Sorted by source publication date; verification dates and access limits are shown separately.

← All research notes

Game Developer — First-hand Postmortems

Postmortem: The journey of Inkbound through Early Access

Mark Cooke · Outside original priority window · Checked

First-person studio postmortem; historical internal observations

Historical account by Shiny Shoe's CEO: integrated feedback and technical testing helped iteration, but free testers did not anticipate paying customers' objections to cosmetic monetization. Supporting solo and co-op created conflicting design demands. English-only Early Access simplified iteration while leaving a significant localization problem.

NUMBERS, WITH THEIR DEFINITIONS
  • Early Access began in May 2023; a few hundred people tested before release.
  • Approximately 60% of runs were solo and 40% co-op; these are runs, not players.
  • Cooke reports missing Chinese support as the leading Early Access refund reason; no count or rate is provided.

Use it forChoose the supported play mode deliberately and collect contextual feedback; free playtests cannot validate willingness to pay.

Do not concludeNo sales lift, refund denominator, or lost-localization revenue is quantified. This established studio's online infrastructure is not evidence of 15-day feasibility.

Apply in a small-team experiment · 2 steps

Our proposed experiment—not a result measured by this article.

  1. on day 1, select one primary demo play mode and write its acceptance criteria; exclude a second mode, matchmaking hub, and live-service monetization unless they are essential to the tested hook.
  2. by day 6, add a simple feedback link with an optional build ID and consented reproduction details; have the PM separate repeated gameplay issues, language requests, and price expectations rather than merging them into one approval score.

References & how we used them

2 source references. “Used for” identifies where this page relies on each source; it does not mean the author endorses our interpretation. Historical access notes are not fresh verification.

  1. Postmortem: The journey of Inkbound through Early Access

    Used for: Original article summarized in this research note; hard-data statements retain the source scope

    Evidence scope: Developer postmortem on Early Access changes and play patterns. Solo/co-op percentages refer to runs, not unique players.

    Title and source access checked in this update. Public article text reviewed; linked paid datasets and external announcements not independently audited. Check date: 2026-09-08.

    https://www.gamedeveloper.com/production/postmortem-inkbound-s-journey-in-early-access
  2. Steam store page — Inkbound

    Used for: Supporting context; our application steps are separate proposals

    Data-page label, not an article title.

    https://store.steampowered.com/app/1062810/Inkbound/

Full public article read; no login or payment required during this check.