Look past the creation button
Astrocade’s official homepage places published games alongside a creation entry point. Our observation is simple: for this kind of product, the destination of the finished game is part of what a creator is choosing.
That does not establish whether a platform will deliver an audience. It identifies another part of the workflow worth investigating.
Questions about distribution
Can a creator share a direct link? Does the recipient need an account? Can the game be published elsewhere? What happens to a published project if the creator stops paying? Those questions should be checked against current documentation and an actual publishing test.
Counters need context
Discovery feeds often display activity signals. A count is only meaningful with its definition: unique players, page visits, launches, or something else, over a known time window.
AI GameScope will not combine platform counters into a global popularity ranking. Until definitions are comparable, editorial observation and clearly attributed platform signals should remain separate.
Follow the whole path to a player
Creation, publication, discovery, and repeat play are different events. A public URL establishes a destination; it does not show that the feed exposed it, that someone started it, or that they returned.
| Event | What to record | What not to infer |
|---|---|---|
| Project published | URL, date, visibility setting, moderation status | The game has an audience |
| Listing shown | Platform definition and observation window | A unique person saw it |
| Game opened | Whether this means a page load or actual runtime start | A player completed the game |
| Meaningful play | An explicitly defined interaction or checkpoint | Retention without a later observation |
| Return visit | The platform’s definition and measurement limits | A comparable rate across unrelated platforms |
This is a measurement framework, not data we have collected from Astrocade. If a platform supplies only an undefined counter, preserve that wording rather than relabeling it as “players.”
Publishing inside a platform changes the trade-off
An integrated gallery may reduce the work required to make a project visible. It also introduces questions about discovery rules, moderation, attribution, remix behavior, and access to the audience. Check whether a creator can edit a published version, keep a stable link, and explain which version a player is opening.
For your own site, separate the page that introduces the game from the game runtime. Confirm that a public description, meaningful title, creator attribution, and a direct link exist before assuming search engines can understand the project. A gallery’s existence alone is not evidence that its individual games are discoverable through search.
What we would test next
A useful follow-up would take a small project through publication, open it as a new visitor on multiple devices, and record the complete access path. That would establish more than a launch announcement can tell us. This article does not report that such a test has already happened.