Skip to guide
DocumentationUsing Helios
Using Helios

Previews and evidence

See the result and understand what has actually been tested.

Reviewed 6 October 2026 · 2 min read

Import example project ↗Two named conversations, shared files, revisions and a preview.

Different kinds of evidence

A browser preview, native app window and screenshot answer different questions. A screenshot shows appearance at a moment; it does not prove buttons work.

Specialist viewers and native preview additions depend on the installed build and computer.

  1. Start the intended preview/application and identify its location.
  2. Exercise the main flow with realistic input and an error case.
  3. Check narrow layouts, keyboard use and relevant device sizes.
  4. After changes, refresh the actual running version and capture new evidence.

Try this

Example request

Open the current build, test adding and deleting a note, then reopen it to check persistence. Capture desktop and phone-width layouts and include relevant console errors.

Check the result

  • The preview matches current source.
  • The main interaction works.
  • Mocked data or a missing backend is clearly identified.

Blank or stale previews

Check the process, port, log and browser console before redesigning a blank screen.

A local preview URL may not be reachable on a phone without a supported relay or sharing path.

Your screen may differ by platform and version. Check availability or get help.