Product news: Gemini apps can move into private Google Sites drafts, adding a handoff point for classroom review

Google announced on October 19, 2026 that interactive apps created in Gemini could be exported to Google Sites as new private drafts. The update is available on web, Android, and iOS for eligible Workspace, Workspace Individual, and personal-account users with Gemini access. Sites must be enabled, and users must have permission to create and edit sites; existing Sites and Drive policies continue to apply. This October 20 report focuses on the handoff into a draft, before a person decides to publish and share it.

For a classroom project, that intermediate state could become an explicit review checkpoint. A student would first describe what the app is intended to help someone explore, which inputs it accepts, and what a correct result should look like. The teacher and peers could then test the prototype against that description. Keeping the learning purpose visible matters because an interactive interface can attract attention even when its underlying explanation is incomplete. This is a proposed teaching use of the export workflow, not evidence from a classroom evaluation of the release.

Consider a student-built simulation comparing water use under different household choices. Before sharing it, students manually calculate a few examples with supplied fictional values and predict the results. They then check units, reset behaviour, and the handling of an unusual input. A classmate tries to explain the simulation's assumptions after using it. If the explanation differs from the authors' intention, the team can revise the labels, instructions, or model. The exercise gives the draft a clear purpose: revealing problems while revision remains part of the assignment.

Review should also examine what the interaction encourages learners to notice. A slider may make change easy to see while hiding why two quantities are related. A student could therefore pair the app with a short explanation of the rule, an example worked without the interface, and a statement of where the model stops being appropriate. Peers could test whether changing one input produces the expected consequence. These activities assess the reasoning represented by the prototype, rather than rewarding complexity, animation, or the number of controls it contains.

Publication introduces a separate audience decision. A teacher could ask students to identify the intended readers, remove unnecessary personal information, and check that the shared page contains the instructions and source acknowledgments needed by someone outside the group. They should open the result using an appropriate test role and device before assuming it is usable. A draft that works for its creator may still be unsuitable for its intended audience. The review is an educational proposal; the announcement does not claim that export automatically checks content quality or accessibility.

The new connection reduces a handoff between creating an interactive app and preparing a site, while preserving a draft stage where people can make deliberate choices. A small pilot could assess whether students can explain the model, identify a failure case, and justify what they choose to share. The evidence should include their reasoning as well as the finished page. Successful export establishes that an artifact reached another product; a publishable learning resource requires a separate judgment about its behaviour, explanation, audience, and instructional purpose.