A page that computes, not one that describes
Change a value and it recalculates on the spot, so the picture and the numbers move together. Nothing here is a prepared screen being flipped.
Say what you want them to discover and TutorFlow plans the model it will compute. Approve the plan and you get a page they explore by changing its values.
Explain a principle in words and learners write it down. Let them change the numbers themselves and they work it out. That used to mean somebody had to build a simulation, which usually meant nobody did. TutorFlow takes one line about what you want to teach and builds a web page that really runs the calculation. Nothing to install, and a single link opens it on a classroom tablet.
Change a value and it recalculates on the spot, so the picture and the numbers move together. Nothing here is a prepared screen being flipped.
TutorFlow moves every control from one end of its range to the other and checks the picture really changes. A version whose sliders move and whose drawing does not is rebuilt.
Write "widen the rate slider to 20%" and the simulation is rebuilt. Every version is kept, so you can always go back.
Each started from one sentence a teacher wrote. Change the values here, exactly as a learner would.
Change the mass and the spring constant and watch what happens to the period. The measured period is shown alongside.
Move the principal, the rate and the term, and see exactly where the two curves start to part.
Grow the array and count for yourself how the number of comparisons grows with it.
None of this was hand-coded. TutorFlow planned the model, wrote the maths, ran it, and published it.
Three things separate a page that merely looks plausible from one you can teach with.
Before anything is built, TutorFlow writes the plan. Which quantities it tracks and how they relate takes a minute to read, and anything that does not suit your class can be fixed right there.
A simulation whose numbers change while the drawing stays still is worse than none. So on every build TutorFlow moves each control from one end of its range to the other and checks the screen actually changes.
Every simulation carries questions a learner can only answer by moving the controls. Copying a number off the screen will not do it.
Say what you would like learners to work out. One principle they can find by changing values is enough.
Read what it will compute and what can be changed, fix anything that does not suit your class, then build. It takes a few minutes.
Send learners the link and it opens in their browser. Mouse and touch both work.
For teachers tired of describing in words how an algorithm behaves as the data grows.
For subjects like compounding or break-even, where the feel for it only comes from moving the numbers.
For L&D teams who want people to try a decision and see where it leads.
For teachers who would rather show where a formula comes from before anyone memorises it.
Each feature pairs with the others. Pick another feature to see how it fits into your teaching workflow.
One line is enough. Build a page they explore by changing its values.