Use Gemini's immersive explorations as a visual starting point for an educational walkthrough, then build the explanation from sources you can check. A useful creator brief separates what the scene displays, what the narration claims, and what the viewer should be able to explain afterward.
Imagine Mara, the fictional host of Small Atlas, planning a short video about how an interactive scene changes as someone opens its labels. She wants to explain how to explore the experience without turning a convincing visualization into evidence for every statement on screen.
| Walkthrough decision | Filled fictional brief | Review before recording |
|---|---|---|
| Viewer task | Open one available exploration and follow two related labels | Confirm those controls exist in Mara's account |
| Opening shot | Mara points from the whole scene to a selected detail | Keep the original context visible |
| Spoken claim | This label opens a closer view of the selected topic | Check the actual interaction |
| Factual explanation | Explain one relationship introduced by that view | Attach a separate checked source |
| Missing evidence | The visual alone does not establish scale or completeness | Say when a view is illustrative |
| Final handoff | Three-shot plan, approved narration, source notes, and captions | Mara approves the exported file |
Mara and her channel are invented. This is a proposed editorial exercise, not a product test or a report of improved learning.
Google's October 28 announcement introduces a library of interactive explorations in the Gemini student hub. Direct access from chat and audio narration are described as coming soon. A walkthrough made today should show the controls actually available, with that distinction intact.
Begin with the viewer's next action
Mara's first sentence is a practical instruction: choose an available scene, look at its overview, then open one label. It gives the viewer something specific to follow. A broad promise to “understand the universe” would need a different lesson and far more evidence.
Write the action before assembling screenshots. Decide where it ends. For this video, the viewer needs to understand how Mara moves from an overview into one detail and back. They do not need a tour of every available topic.
Record a fallback plan too. If the selected exploration is missing from the account, choose another visible example and revise the brief. A launch announcement is evidence of an announcement; it is not footage of your account working.
Keep the screen and the explanation in separate columns
Create two short lists while exploring: visible observations and factual statements. “A label opens another view” belongs in the first. A statement about the object being depicted belongs in the second and needs its own basis.
For each factual line in the draft, attach a source passage and explain what it supports. If the source only establishes a general relationship, do not add a precise number because the visual appears measurable. Avoid estimating distances or sizes from an illustrative scene.
Mara can prepare her capture sequence without approving every explanatory line. Mark unresolved narration clearly and leave it out of the recording script until checked. That keeps the attractive scene from deciding the lesson's claims.
Plan three shots with one job each
The opening establishes orientation: show the whole interface long enough to locate the selected label. The second shot follows the interaction. The third returns to the overview and restates the narrow relationship the approved narration explains.
This is our suggested production method, not a prescribed Gemini feature. Use a simple shot list with the selected view, cursor or tap action, spoken line, and required caption. Avoid camera moves or decorative edits that hide the control the viewer needs.
Keep a clean version of the recording before adding callouts. If an arrow points to the wrong label after a revision, correct the arrow rather than asking narration to compensate. Review the final crop on the kind of screen your audience uses.
Describe availability without borrowing tomorrow's controls
Google names English, Indonesian, Hindi, Brazilian Portuguese, French, and simplified Chinese for the feature, with an English-only experience for other languages at announcement. Check the language and entry point you actually use before describing either in a tutorial.
Do not record an invented audio button because narration is promised later. If you add your own voiceover, identify it as your narration. Similarly, a walkthrough through the student hub should not imply that the forthcoming chat entry point has already arrived.
Put a checked-on date in your production notes. When the interface changes, update the affected instruction and recording together. A small correction is clearer than leaving an old click path beside a newly rewritten paragraph.
Give the reviewer a claim they can challenge
Ask a reviewer to locate the two labels using the draft alone. Then ask them to distinguish the scene's presentation from the explanation you added. If they cannot tell which is which, revise the narration and captions before adding more detail.
Google's Gemini Apps help guide says responses can be mistaken and should be checked. Treat that as a reason to inspect the actual statements, not as a caption that automatically makes an unchecked lesson reliable.
For this exercise, a useful correction note is concrete: “The narration states a scale that neither the source nor the captured view establishes; remove it.” Keep the revised line beside the rejected version so the editor understands the decision.
Finish one explanation and preserve its boundaries
Save the selected scene name, checked-on date, capture sequence, source passages, approved narration, and exported filename together. The next person should be able to tell what was observed, what was sourced, and what remains outside the lesson.
For a Growit planning handoff, review the o1 guides, current specifications, and o1 AI workspace. The physical o1 device remains in development. This example establishes no Gemini integration, scene import, screen recording, or automatic lesson verification through o1.
Choose one available exploration and write its first three shots today. Approve one sourced explanation before expanding the tour.
