FAQ

Common questions about the current Gamecoder rollout.

This FAQ is meant to help principals, teachers, pilot users, and public visitors understand the current school-facing posture without needing to parse the codebase.

Is Gamecoder a public student social platform?

No. Gamecoder is being positioned as a school-first learning platform. Student projects begin private, and the current showcase is limited to signed-in school users with access.

Who can use it today?

Students, teachers, admins, guardians, and other adult users can access different parts of the product, but school-facing rollout and approved access are still the main posture.

What do students actually do in class?

Students plan games with AI assistance, build in the browser, edit scenes and code, test their work, and revise based on teacher guidance.

Is publishing open to anonymous visitors?

No. The current showcase is signed-in only. Broader sharing is a later policy and product decision, not a default assumption.

Where should parents start if they receive a school email about Gamecoder?

They should start with the parent overview page, which explains what students can create, who can see work, and how questions or removal requests should be routed.

How are questions or rollout issues handled?

Use the existing request-access and school-rollout flow. The current support page explains how to route questions without assuming a public ticket desk already exists.

Are these the final legal and parent-facing materials?

Not yet. This FAQ is part of the public-post pass. Parent-email-ready materials, additional policy language, and deeper governance documents come later in the rollout.