Collecting Player Feedback During Steam Next Fest

Steam Next Fest drops thousands of brand-new players onto your demo in a single week. It is the most concentrated source of honest, unbiased feedback an indie game will ever get, and most developers waste it. They watch the wishlist count tick up and miss the crashes, the confusing tutorials, and the exact moment players quit. The festival lasts seven days and then those exact players are gone forever, so the difference between a wasted Next Fest and a transformative one is entirely about what you set up beforehand. Here is how to instrument your demo so the spike becomes data you can act on long after the event ends.

The spike is one-time, so capture everything automatically

Next Fest players are not your community. They have no patience, no loyalty yet, and no reason to file a thoughtful bug report. If your demo crashes, they uninstall and move on. You will not get a second chance with them, which means manual feedback channels will catch almost nothing.

Automatic capture is the answer. An in-demo report button, automatic crash capture, and lightweight funnel tracking run silently and collect data from players who would never otherwise tell you anything. Set this up before the festival, not during it.

Capture crashes before players vanish

A crash during Next Fest is a wishlist you will never get. Automatic crash capture records the stack trace, build version, and device info the moment the game dies, and uploads it on the next launch or immediately if you can. Even players who quit forever leave you a crash report that tells you what drove them away.

Group crashes by frequency and you will quickly see which one or two issues are costing you the most players. Fixing the top crash mid-festival, if you can ship a demo update, can measurably change your conversion for the rest of the week.

Track where players drop off

Wishlists tell you how many players liked the demo. They do not tell you where the other players quit. Add simple funnel events at key moments: demo launched, tutorial completed, first objective done, demo finished. The gaps between those numbers are your problems.

If half your players never finish the tutorial, your tutorial is the bug. Funnel data turns a vague sense that the demo could be better into a ranked list of exactly where you are losing people, which is the single most valuable thing Next Fest can give you.

Make the report button irresistibly easy

Add a Send Feedback button to your demo menu and your demo-complete screen. Capture a screenshot and device info automatically so the player only types a sentence. The demo-complete screen is gold: players who just finished are in the perfect mood to tell you what they thought.

Keep it to one text box. Ask one question, like What is the one thing you would change. Specific, low-effort prompts get ten times the responses of a blank box labeled feedback.

Setting up with Bugnet

Drop the Bugnet SDK into your demo build, wire the feedback button to capture a screenshot and device info, and enable automatic crash capture. Everything lands in one dashboard so you can triage the firehose in real time instead of scattering across spreadsheets and Discord.

Because the free tier covers a meaningful volume of reports per month, a one-week demo spike fits comfortably without a paid plan. Set it up once, watch the data come in, and carry the same instrumentation straight into Early Access afterward.

Turn the festival data into your next build

The week after Next Fest is when the value compounds, if you have the data. Sort your crashes by frequency and your funnel drop-offs by size, and you have a ranked, evidence-based to-do list for the next version of the demo or the full game. This beats arguing about priorities from memory or from the few opinions that happened to be loudest in your Discord.

Pair the quantitative funnel with the qualitative feedback from your report button and you can see not just where players quit but why. If the data shows half your players abandon during a specific boss and the feedback says that fight feels unfair, you have both the location and the reason. That is the kind of clear, defensible insight that justifies real changes, and it only exists if you instrumented the demo before the spike instead of after. Save the raw numbers somewhere durable, too, because comparing the funnel from this festival against your next one is how you prove the changes you made actually moved the needle rather than just feeling better.

Next Fest is a week-long firehose of strangers. Point a bucket at it.