Dashboard

Preview control

Watch it test your app

Swarmz opens your live app in a real browser and uses it like a customer: clicking, typing and checking out on desktop, tablet and phone. You watch every move in your preview, and it fixes what breaks.

Meet Kernel 1

A real browser

Not a screenshot. It opens your app and actually uses it.

Every screen size

Desktop, tablet and phone: the sizes your visitors use.

Checked before it's done

Style, types, preview and runtime errors, fixed if anything fails.

Hands on

Clicks, types and scrolls like a person

Ask it to test your checkout and it picks a size, adds to cart, fills in the form and moves through each page. Every step shows up in your chat, in plain words.

  • Clicks, types, fills in forms and scrolls
  • Moves between pages like a visitor
  • Every step listed as it happens

Captures

It checks the exact section you mean

Ask about the product grid, the pricing table or the footer. Swarmz scrolls there, frames that section and captures it, so its answer is based on what's really on the page.

  • Frames one section, not just the top of the page
  • The capture lands right in your chat

Final checks

Checked before it says done

When a change is finished, Swarmz checks the code style, the types, your live preview and any runtime errors. If something fails, it fixes it and checks again, up to twice, then tells you plainly how it went.

  • Style, types, preview and runtime errors
  • Fixes what fails, then checks again
  • A plain-English report at the end
How Kernel 1 works

Every screen

Tested at the sizes people use

It switches its browser between desktop, tablet and phone and checks each one, so the menu opens on a phone and the checkout fits on a tablet.

Questions, answered

What does preview control do?
It lets Swarmz use your app the way a visitor would. It opens your live preview in a real browser, then clicks, types, scrolls and moves between pages to test what it built, or to check something you asked about.
Do I need to switch it on?
No. Swarmz reaches for it when testing helps, and you can always ask directly: “test the sign-up form on a phone” or “check the menu opens”.
Which screen sizes does it test?
Desktop at 1280 × 800, tablet at 834 × 1112 and phone at 390 × 844. It can switch between them in the same run.
What will I see while it tests?
Its cursor moves through your own preview, and the button or field it's using is outlined in orange. The chat card says what it's doing right now. It never submits a form a second time in your tab.
What are final checks?
The last step of every change. Swarmz reads its changes, checks code style and types, loads your preview and watches for runtime errors. If a check fails it fixes it, up to twice, and tells you honestly if anything is still wrong.

Let it test the next one

Describe your app. Swarmz builds it, clicks through it and fixes what breaks.

See pricing