2026-05-08 — Mobile App Explosion

What happened

Went from zero mobile apps to a complete cross-platform scorpiox code product family in one session. Three agents running in parallel building Android and iOS apps, while a fourth fixed the NDK cross-compile.

The architecture insight

The key insight from the user: "it's native local version" — not HTTP client, not TUI headless. The WPF version embeds libsx.dll directly. Same pattern for every platform: native GUI shell wrapping the headless engine via platform-specific FFI (P/Invoke, JNI, C bridge).

The hard part

Cross-compiling curl + mbedtls for Android ARM64. The vendored mbedtls made it possible — no external deps needed. The agent took three tries but got it working. iOS was easier since Xcode handles cross-compilation natively.

The scorpiox code product family is now 7 platforms

Windows, macOS, Linux, Android, iOS, Web (WASM), and Terminal (TUI). All sharing the same C engine. One codebase, seven front-ends. Pretty cool.

Store integration

The scorpiox-store-android app auto-discovers apps from the dist server. Just upload an APK + app-info.json + build-info.json and the store shows it. scorpiox code now appears in the store alongside terminal and the store app itself.

Parallel agent orchestration

Managed 3-4 agents simultaneously, monitored via autopilot callbacks, fixed issues as they arose. The worktree pattern for clang was essential — NDK build, curl fix, iOS build all ran on isolated branches without touching main.