See It Run

Boot Crosswake once. See web, iOS simulator, and Android emulator connect to the same backend — advisorily, without claiming device support. Works from Docker with no local Elixir toolchain.

bin/see-it-run.sh

The banner prints your next steps.

See examples/QUICK_START.md for the full proof command reference.

What You'll See

Advisory native collateral. A successful simulator or emulator run confirms the dev wiring reaches the local backend, but does not prove physical-device support. This is emulator evidence per the support-truth label legend.

One shared backend, starting at the showcase hub:

<img src="https://raw.githubusercontent.com/szTheory/crosswake/main/brandbook/collateral/see-it-run/web-home.png" alt="Crosswake showcase hub at localhost:4700 — the SaaS/Admin, Field Service, and Learning/Training lanes with route-owner and support-truth labels" width="900" />

Then watch bin/see-it-run.sh boot the shared backend and open the browser:

<img src="https://raw.githubusercontent.com/szTheory/crosswake/main/brandbook/collateral/see-it-run/see-it-run.gif" alt="Screen recording: bin/see-it-run.sh boots the shared backend, prints the banner, and opens the browser at localhost:4700" width="900" />

The web runtime is proven; iOS Simulator and Android Emulator connect to the same backend as advisory emulator evidence — compared side by side in the Compare All Three Runtimes table below.

Showcase screenshots explain the product surface; route-tour assertions prove route-owner semantics before screenshots are written.

Run It Now (Zero Toolchain)

JTBD-A: See the web app running in under a minute — no Elixir, no Node, no SQLite toolchain required.

Boot the shared backend with one command:

bin/see-it-run.sh

Or start the Docker backend directly:

cd examples/phoenix_host
docker compose up

Open http://localhost:4700/ in your browser. This is the showcase hub: a product-shaped first screen for the SaaS/Admin, Field Service, and Learning/Training lanes, with route-owner and support labels visible before you inspect proof routes.

If you have Elixir installed locally, mix crosswake.demo does the same thing.

For the full first-run walkthrough including offline replay proof, see examples/QUICK_START.md — Option A: One Command (Docker).

To visibly rehearse the checked-in offline study route in iPhone Simulator, run:

bin/crosswake-ios-rehearsal

It is advisory Simulator evidence only. The real-phone handoff and its one-command promotion flow are documented in Physical iPhone handoff.

Browse the Route Owners

Visit these routes while the backend is running at http://localhost:4700:

Proof routes stay one click deeper and are secondary to the showcase-first path. Use them after the hub explains the product shape.

Support-truth labels stay literal here: Available today, Proof-backed example, Demo pressure, and Future gap distinguish shipped proof from native-control pressure.

http://localhost:4700/
http://localhost:4700/offline
http://localhost:4700/bridge-proof

For the Playwright offline replay proof and script commands, see examples/QUICK_START.md — See The Route Owners.

Compare All Three Runtimes (Web, iOS, Android)

Advisory native collateral. The iOS Simulator and Android Emulator runs confirm the dev wiring reaches the shared backend. They are emulator evidence — advisory platform evidence, not physical-device support.

The three runtimes connect to the same shared backend started by bin/see-it-run.sh. "Web" is proven; native is advisory emulator evidence per the support-truth label legend.

Wire a Native Runtime to the Local Backend

Advisory native collateral. The dev wiring commands load Crosswake routes from the local backend.

The checked-in native shell hosts at examples/ios_shell_host and examples/android_shell_host are checked-in public-coordinate proof in published-coordinate mode. The dev-wiring step connects the simulator or emulator to the Phoenix host you already booted with bin/see-it-run.sh.

A successful simulator or emulator run confirms the dev wiring reaches the local backend, but does not prove physical-device support. This is emulator evidence per the support-truth label legend.

For the exact xcodebuild and gradlew dev-wiring commands, see examples/QUICK_START.md — Run Against the Local Backend (Dev Wiring).

What This Proves (And What It Doesn't)

What bin/see-it-run.sh proves:

• The Phoenix-owned web routes (/, /offline, /bridge-proof) are live and serving correctly at http://localhost:4700. This is proven.
• The Docker backend starts cleanly and accepts connections. This is proven.
• The iOS Simulator and Android Emulator reach the shared backend via dev wiring. This is emulator evidence — advisory, not a proven native build.

What it does not prove:

• Physical-device support. The iOS and Android runs are emulator evidence only; they confirm the dev wiring path, not broad device support.
• Offline replay correctness. The offline proof requires the Playwright spec in examples/QUICK_START.md.
• Any claim of simulator or emulator support beyond the advisory label.

"Proven" is reserved for the web path. Native is always labeled emulator evidence.

Go Deeper

• Full proof command reference: examples/QUICK_START.md
• Installing the library in your own Phoenix app: install.md
• Route ownership and the policy model: route_policy.md
• Choosing the right runtime for your audience: adopter_profiles.md