The STEAM Lab: 142 tools, and how to find the one you need
The 142-tool STEAM Lab: how to find a tool, how to put one in front of students with its own link, what to expect from any of them, and three ways teachers actually use them.
- Best for
- Any teacher
- Typical use
- 8 minutes
Search the guide
Type one or more words to search every chapter.
The STEAM Lab is the largest thing in AlloFlow: 142 interactive tools across thirteen subject areas, from a water-cycle simulation to a titration burette to a disproportionality analyzer. This chapter does not describe all 142 — that list lives in the catalog, which is always current, while a printed list would be wrong within a month. What this chapter teaches is the part that does not change: how to find the right tool, how to put it in front of students, and what to expect from any tool you open.
What is in there
| Area | Roughly |
|---|---|
| Earth and space science | 27 tools |
| Computing, AI, and digital literacy | 19 |
| Ecology, environment, and animals | 14 |
| Math fundamentals | 15 |
| Life science and genetics | 12 |
| Life skills, careers, and economics | 11 |
| Engineering and design · geometry and measurement · learning and behavioral science | 7 each |
| Human body and safety · data and statistics | 5 each |
| Strategy games · sports and movement science | 4 each |
Where the live list is. All 142 live inside the STEAM Lab itself: open it from Learning Tools on the Launch Pad, or from the STEAM Lab entry in the tool list, and search or browse by area there. That is the only always-current list, which is why this chapter does not reproduce it.
Do not confuse this with Find a tool on the AlloFlow website. That page is a finder for the lesson-building tools, the ones that turn source material into glossaries, adaptations and quizzes, and it usefully filters by whether a tool needs a source, needs AI, or runs in Gemini Canvas. It does not list the STEAM Lab's simulations, so searching it for "titration" or "solar system" finds nothing.
Finding a tool: three routes
Search, if you know roughly what you want. Open the STEAM Lab and type in its search box. It matches tool names, descriptions, topics, and hand-written aliases — so "photosynthesis" finds the tree lab even though that word is not in its title.
Browse by area, if you are planning a unit. The lab's own subject groupings are the fastest way to see everything available for a topic you are about to teach.
Ask by voice or the command palette, if your hands are busy: press Ctrl+K and type the tool name, or say it aloud with voice control on.
Putting a tool in front of students
This is the part worth learning once, because it works for every tool.
Every tool has its own web address. A tool called Water Cycle is at /water-cycle, the coaster lab at /coaster-lab, and so on — one address per tool, all 142 of them. Paste that link into Google Classroom, an email, or a QR code and a student lands directly in that one tool, with no menus to navigate and nothing to install. They do not need an account.
A student who arrives this way sees a small note at the bottom of the screen explaining that this is one tool from AlloFlow and offering a way into the full app. It can be dismissed and does not follow them into the activity.
Or share the whole lab by sending the app link and telling students which tool to open. Use the direct link when you want them in one place; use the app link when the activity is "explore three of these."
What to expect from any tool
They run on the device, in the browser. No installation, no account, and nothing uploaded. A Chromebook, an iPad, and a ten-year-old laptop all work; the 3D tools want a reasonably modern browser.
AI is optional and clearly marked. Most tools are simulations and instruments — they compute, they draw, they respond, and none of that needs AI. Some offer AI extras such as hints or coaching. If your school has not connected an AI backend, those extras are simply not shown, and a small "AI extras: off" note appears in the lab header explaining why and how to turn them on. The tool itself works fully either way. This matters for planning: a lesson built on a simulation is not at risk if the AI is unavailable that morning.
They are instruments, not answer keys. The tools show what happens; the interpretation is the lesson. A simulation that produces a surprising result is usually the most valuable moment in the class, not a bug to be fixed.
Fullscreen and accessibility. Most visual tools have a fullscreen control for projecting to a class. Tools are keyboard-operable, and the 3D ones expose camera controls to the keyboard rather than requiring a mouse drag.
Three ways teachers actually use them
As a demonstration. Project one tool, drive it yourself, and narrate. Fastest to plan, and the fullscreen control exists for exactly this.
As a station. Send the direct link for one tool to a group and give them a question to answer with it. Because each tool has its own address, four groups can be in four different tools without anyone getting lost.
As the evidence step in a lesson. Build the lesson in AlloFlow as usual, then send students to a tool to gather the observation the lesson asks them to explain. The tools do not record student work, so decide in advance how you want them to capture what they found — a worksheet, a photo, a shared document.
When something does not work
Almost every problem is one of three: the tool did not finish loading, the browser is too old for a 3D tool, or an AI extra is hidden because no backend is connected. The first is a reload, the second needs a different device, and the third is explained by the note in the lab header. The full recovery sequence is in Troubleshooting.
For leaders planning wider use
Tool links are the easiest way to hand teachers something concrete: pick three tools for a grade band and send the three addresses. There is nothing to license, provision, or roster, so a department can pilot on Monday. The privacy picture is the same as the rest of AlloFlow and is set out in Privacy and responsible AI.