Back to home

Games, news and stories

Machine translated · For reference only

We spent half a year polishing the demo, but players never showed up: How should indie game developers balance playtests, demos, and game festivals?

Russell · 文化与观点

steam.png

How much time should you spend polishing a game demo?

Based on my own experience in game development,The sooner we release a demo that can be used to validate the game's core gameplay, the better. ...but at the time, we didn't realize this and spent a great deal of time polishing the details. While this did improve the game's quality to some extent, in hindsight, it wasn't worth it compared to the far more valuable marketing and promotion efforts.

Looking back on this experience now, I realize that the problem wasn’t simply that “the marketing campaign started too late.” Much earlier on, the team should have determined whether the current version was intended to validate the gameplay mechanics or was already capable of attracting players.

Steam offers several different options: Playtest, Demo, and Early Access (EA). While they all seem to give players early access to games, they serve different purposes. If you don’t understand these distinctions, you might mistake a test build for promotional material, a demo for a scaled-down version of the full game, or even include gameplay features that haven’t been finalized yet in a paid Early Access release.

In my view, independent teams do not necessarily lack the patience to continue refining their games,What is more often lacking is the ability to assess the stage : Which issues should be handed over to players for testing as early as possible, which aspects of the experience must be finalized before launch, and when is the right time to take advantage of opportunities for concentrated exposure, such as the New Product Festival.

They’re all ways to let players try the game early—so what’s the difference between a playtest, a demo, and an early access release?

If we consider them solely in terms of completion, Playtest, Demo, and EA can easily be arranged along a development timeline: first, a rough test version; then, a polished demo; and finally, an Early Access version with more content.

This understanding is not entirely accurate. A playtest can certainly be very polished, and a demo isn’t necessarily smaller than an early access release. In my opinion, a more useful way to distinguish between them is to consider why players are playing this version and what the developers expect players to do.

The focus of playtesting is to help developers identify issues.

Steam Playtest is a free testing tool that uses App IDs linked to the main game but independent of it. The standard sign-up portal is located on the main game’s store page, and developers can control the number of participants and the test’s availability; it does not have a separate store page, nor does it provide user reviews. [1]

This approach is ideal for verifying whether the combat feels right, whether the game’s economic loop is understandable, and where first-time players might get stuck. At this stage, it’s not necessary to polish every resource to its final quality, but players should be able to experience the parts that truly need testing.

Developers are familiar with their own games; they know the sequence of tasks and understand why certain features are temporarily unavailable. New players, however, lack this background knowledge. A process that runs smoothly during internal testing may not go just as smoothly when external players try it.

Therefore, I place greater value on specific behavioral feedback rather than mere comments like “It’s pretty fun.” Information such as where players stopped for the first time, why they repeatedly opened the same menu, and why they didn’t continue playing is often more helpful in guiding revisions.

The purpose of a demo is different. Players download demos not to help the team complete development, but rather toDecide whether this game is worth checking out . Steam officials have also explicitly stated that players use demos to decide whether to purchase a game, so demos should be of sufficient quality and accurately represent the actual gameplay experience.[2]

This is also why I do not agree with directly referring to a “version that currently runs” as a demo. If the task cannot be completed halfway through, if core operations still require explanation from the developer, and if the interface is littered with inoperative entries, then even if such a version contains a substantial amount of content, it is better suited for further testing.

The demo may lack future maps, characters, and systems, but the portion that is currently available should be complete. Players need to truly experience the game's appeal, rather than guessing what's to come based on menus that aren't yet available.

As for EA, the difference is even more obvious: the game is already on sale.

Steam classifies EA as a publisher that sells games that are still in development,The current version should be playable and worth its current price. . Officials also emphasized that an EA is not a pre-order and should not be viewed as merely a way to raise funds for development;Players should make purchases based on their current experience, rather than betting on future promises. .[3]

In my view, “Early Access” should not be used as an excuse to lower delivery standards. Just because players are willing to accept that the content isn’t yet complete doesn’t mean they should pay to help the team figure out what makes the game fun. If the core gameplay hasn’t been validated yet and the existing content isn’t sufficient to justify the price, these issues should be addressed first.

EA isn’t necessarily a required step for indie games either. If a game is essentially complete and only requires final bug testing, Steam recommends continuing testing rather than releasing it as an Early Access title.[3] Whether early sales are appropriate also depends on whether the game is designed for long-term expansion or is a one-time experience reliant on a complete storyline.

How detailed should a demo be? Having a little less content isn't necessarily a bad thing.

The most common dilemma when releasing a public demo is thinking, “It’s not good enough yet.” The visuals can still be improved, the video can be re-edited, more features can be added, and there’s always room to fine-tune a particular part of the experience.

Thanks to my previous experience developing a full-fledged game, I’ve gained a more concrete understanding of this mindset. Nearly half a year of refinement wasn’t entirely in vain, but if improvements are primarily focused on issues already identified by the team and people familiar with the game, we may still overlook the experience of new players—and we won’t be able to determine whether the market is truly interested in the game.

Therefore, I do not believe that a demo for a first game necessarily requires several months of development, nor do I agree with the blanket statement that “spending half a year polishing it is definitely not worth it.” Project scale, gameplay structure, and the feedback received vary from case to case.What is even more cause for concern is setting the conditions for disclosure as a standard of “sufficient perfection” that will never be met. ..

To determine whether the demo is ready,First, we need to see if players can complete the experience on their own. ..

A simple way to test this is to invite people who haven’t been exposed to the project to try it out, while the developers try to give as few hints as possible. If you find yourself constantly having to explain, “Tap here first,” “This feature isn’t implemented yet,” or “You should go over there next,” it means the version hasn’t yet conveyed the necessary information to the player.

Second,The demo should showcase the full scope of the core gameplay. . In a management game, it’s not enough to simply teach players how to navigate the menus without letting them experience the outcomes of their management decisions; in an action game, it’s not enough to merely showcase movement and environments without featuring representative combat; and in a game that emphasizes character relationships, the demo shouldn’t be limited entirely to basic controls.

In my opinion,The most important thing about a demo is to make this experience truly work, rather than just cramming in as much content as possible. . Leaving out a single system might not affect players' understanding of the game; however, including a system that isn't fully implemented could ruin the entire demo.

Stability also requires setting clear standards. A public release doesn’t have to be “bug-free,” but issues such as failure to launch, frequent crashes, tasks freezing, corrupted save files, and unreadable text should be addressed as a priority. Basic features like volume, resolution, and input methods should not be overlooked simply because “it’s just a demo.”

Passing Steam review does not mean that quality testing is complete. Officials have explicitly stated that package review is not a comprehensive QA process and will not check for or identify most bugs. [4]

Another issue worth noting is that developers sometimes reserve the most distinctive content entirely for the full release. While it’s certainly reasonable to avoid spoilers, if the demo ends before players have had a chance to experience the game’s key features, it’s hard to expect them to imagine on their own just how good the full version will be.

In my opinion, a demo should help players understand why it’s worth continuing to play, while also leaving some content to be discovered later, rather than simply showcasing the easiest early-game sections to complete.

The duration should also align with this goal. There are no uniform requirements for demo length during the New Releases Festival. [4] For some games, a concise experience is sufficient; for others, more time is needed to showcase system mechanics. Adding repetitive content just to meet a certain duration will not make the demo more compelling.

The ending should clearly inform players that the demo has ended and provide a link to the main game's store page. Steam provides instructions on how to open the main game's store page from within the demo. [2] Compared to an abrupt ending, this approach is more effective at converting interest in the demo into continued engagement.

There's only one chance to participate in the New Product Festival—should I save it for right before the release?

The Steam New Releases Sale is typically held in February, June, and October each year; specific dates and end times are subject to the official page for each event. [4]

The most important rule to remember about it is:You may enter a game only once. This restriction applies to the game itself, not to each demo version. Changing the package, creating a new demo, or renaming it to a different version will not grant you a new chance to participate. [4]

Registration is based on the main game,A publicly playable demo must be available before the event begins; playtesting cannot substitute for a demo. .[4] If you conduct a playtest or release a demo early, you will not lose your eligibility, and Steam does not require that the demo be released on the first day of the New Releases Sale.[4]

You should also pay special attention to EA's schedule. The New Releases Festival features games that haven't been released yet,Entering the EA before or during the event will also result in disqualification. . Projects scheduled to enter Early Access in the future are eligible to participate, but projects that have already entered Early Access are not. [4]

Therefore, teams planning to use the New Product Festival to build anticipation for an EA launch should schedule their events before the EA, rather than waiting until the official release to plan them.

As for which version to choose, I still lean toward a relatively conservative recommendation: for small teams whose primary goal is sales and whose resources are limited,Prioritize the edition that is closest to release, provided the demo is already mature and the release plans are relatively clear. ..

The reason isn't complicated. The attention generated by the event needs to be followed up on. If players become interested after trying the game but there's no new news about the project for a long time, the team will have to invest more effort into maintaining that anticipation. Participating closer to the release date makes it easier to coordinate post-event promotion and sales efforts.

It is worth noting that,Never cram your entire development schedule into the period leading up to the event just because the registration deadline for a particular session is approaching. . New energy-saving features attract more players to try out the game, but they won’t fix the onboarding process for the team, nor will they automatically make a gameplay mechanic that hasn’t been fully developed yet interesting.

If a large number of players get stuck at the same point, the focus during the event will shift from showcasing the game to addressing issues that could have been identified in advance, causing a flood of problems to surface and resulting in the New Product Festival having the exact opposite effect. For small teams with only one chance to succeed, this kind of arrangement warrants particular caution.

Preparations for the New Product Festival shouldn't wait until the opening day

In my view, the safest approach would be to first let a group of external players try out the game, identify any issues that affect the experience, and then decide whether to include this version in the New Product Festival.The first external test should not coincide with the opening of the event.

This doesn’t mean that all teams must follow a set process in the order of playtest, demo, and new product showcase. Targeted testing can also be helpful. The important thing is that, before the main launch, teams have already received genuine feedback and have had time to make adjustments based on it.

When planning the schedule, it’s important not to focus solely on the opening date. Registration, store materials, package reviews, and media previews all have their own deadlines. Currently, the schedule provided in the New Product Festival’s general documentation is as follows:If you want your demo to be ready in time for the media preview, you should submit the app package for review five weeks before the event; if you only plan to have it ready by the start of the event, you should submit it three weeks before the event. Specific details are subject to the schedule for the current application cycle, and applicants should allow for some leeway in case they need to resubmit their application. [4]

A media preview is not a private release. If you want the media to try out the game at this stage, you’ll need to make the demo publicly available in advance so that regular players can play it as well. Steam does not guarantee that the media will play or cover a particular project. [4]

During the event, the organizers do not recommend running the Playtest simultaneously, as this would scatter the players; instead, they recommend concentrating participants in the Demo.[4]

In my view, when evaluating the effectiveness of a campaign, in addition to wish lists and download numbers, we should also focus on whether players successfully launched the game, whether they were exposed to the key selling points, and where they exited the game. Only by understanding why their interest did not translate into continued play can we identify the direction for future improvements.

It’s worth launching a standalone demo page, but it’s not a “surefire moneymaker.”

Whether a demo needs its own page is also a trade-off that small teams often have to make.

Steam allows demos to have their own store pages, and also allows the demo to be accessible only through the main game page. A separate page can provide an overview of the demo’s content and allow demo users to leave reviews; regardless of whether a separate page is set up, demos do not have their own community hub. [2]

I tend to create a separate demo page whenever possible, especially for projects where the scope of the demo is clearly defined and the team is looking to gather public feedback. It’s usually more straightforward to explicitly outline what the demo includes than to have players sift through the full-version description on their own.

However, this also means that additional content and descriptions will need to be maintained.The features, languages, and modes listed on the page should correspond to the demo, rather than listing all the content planned for the official release. .[2] If the team’s resources are limited, it’s more important to refine the main game page and the demo experience than to force the creation of another page with inaccurate information.

A standalone demo page will provide a prominent link to the full game, helping players add it to their wish lists or purchase it. [2] However, demo downloads and wish list growth for the full game are different metrics and should not be directly conflated.

The page and the game itself do not have to be released at the same time. Steam allows developers to first publish a “Coming Soon” page for a demo, and then release the playable version later. [2] In my view, what needs to be synchronized is not the release timing of the two buttons, but rather the promotional promises and the actual content players will receive:If the promotion says a demo is available now, the game should be playable when you click the link; if it’s just a teaser, the release date should be specified. ..

Another feature that needs to be arranged in advance is the demo wishlist notification. After the demo is first made available to play, developers can manually trigger a notification once within two weeks to remind players who have added the main game to their wishlist to try out the demo.This opportunity can only be used once. It will not be reset if it is closed and then reopened, and you will not receive another chance even if you participate in the New Product Festival. [2][4]

Therefore, the demo launch, announcements, new product festival, and product release should not be scheduled independently. Even if the team does not have a complex marketing plan, it is still worth clarifying in advance how these milestones will be coordinated.

Conclusion: When to release it is a more worthwhile discussion than how long to keep refining it.

To sum up: A playtest is used to identify issues, a demo is used to showcase an experience worth looking forward to, and an EA (Early Access) release means the current version is now open to evaluation by paying players. The tools themselves aren’t complicated; the challenge lies in determining which stage the project is currently in.

Regarding the New Product Festival, my suggestion isThe demo should first be tested by real players, and then the appropriate version should be selected based on the release goals. . A release date approaching usually makes it easier to generate buzz, but this is only true if the demo is already capable of fulfilling that role.

For teams developing a game for the first time, continuing to refine the game is often easier than openly accepting feedback from strangers. The former provides tangible progress every day, while the latter may yield unexpected feedback. However, it is precisely this feedback that helps developers decide whether they should continue adding content next month or first address the issues players have already encountered.


The platform features and eligibility criteria mentioned in this article are based on the following official Steam documentation; the author’s opinions regarding development pace, demo quality, and the timing of participation are the author’s own and do not constitute mandatory platform requirements. Specific event dates and submission deadlines are subject to the official page for the current edition.

Sources

[1] https://partner.steamgames.com/doc/features/playtest [2] https://partner.steamgames.com/doc/store/application/demos [3] https://partner.steamgames.com/doc/store/earlyaccess [4] https://partner.steamgames.com/doc/marketing/upcoming_events/nextfest

Sign in to save

评论

0 / 5000 个字符

    暂无评论