Explore features and challenges

The Explore tab is where Code Lab becomes more than a block editor.

It is meant for guided curiosity, not for replacing your first successful run.

When to use Explore

Use Explore after you can already do at least one of these:

If you open Explore too early, it can feel like extra complexity instead of help.

When no advanced feature is active, the Explore area behaves like a discovery prompt.

From there you can enable optional tools instead of being forced into them by default.

That is a good design choice for beginners: the advanced surfaces stay available without taking over the first learning experience.

This feature turns the current block program into:

Use it when you want to answer: “What is this program doing, in plain language?”

This feature lets you adjust supported values and preview what would likely happen without changing the actual code.

Use it when you want to:

This makes it a safe place for experimentation.

This feature loads intentionally broken logic so learners can practice fixing it.

It includes:

Use it when you are ready to move from “I can run examples” to “I can diagnose logic problems.”

This feature shows how the current blocks translate into text code.

It helps you:

Use it when you want to build a stronger bridge between visual programming and text-based programming.

If you want a useful progression:

That order keeps the learning curve sensible.

Do not enable every Explore feature just because it looks interesting.

A better strategy is:

That keeps Explore educational instead of distracting.