Platforms & roadmap

Windows first. Android, iOS and Mac as honest, phased research.

One platform is the focus today: Windows. The others are plans with real technical questions still open — most of them about audio. We would rather tell you what is UNKNOWN than promise a date we cannot keep.

Windows — first platform, installer pending

The platform the app is built on. WASAPI loopback from your headset.

Android — planned

Companion first: preparation and practise. Live assist feasibility still being tested — Android has no WASAPI loopback.

iOS — planned

Companion first. Whether other-app audio can be captured at all is UNKNOWN until tested on device.

Mac — planned

Dedicated native app, not a port. Audio candidate: ScreenCaptureKit — permissions and behaviour still to be tested.

Windows — first platform

Windows 10 / 11, 64-bit

The platform the app is built on. The desktop app captures the interviewer’s audio from your headset via WASAPI loopback — the Windows audio path this product was built on. Preparation, live assist, Coach Mode, reports, and the 10-language support all live here.

The signed installer is not published yet — see Download.

Planning — Phase 3

Android — companion first

Android is planned as a companion first: preparation and practise on the go, with the same question bank and the same honest report. Whether full live assist is possible on Android is still being tested — Android cannot use WASAPI loopback, and Android’s audio-capture API (AudioPlaybackCaptureConfiguration, Android 10+) only works for allowed usages (media, game) under the other app’s capture policy. Third-party voice-communication audio is often excluded. That is not equivalent to Windows loopback, and we will not promise live assist on Android until real devices prove it.

No date. No APK. No waitlist yet — the real waitlist will name its processor and privacy policy at launch.

Feasibility UNKNOWN — Phase 4

iOS — planning

iOS is a separate, independent research phase after Android. Whether other-app audio can be captured at all on iOS, and how the app behaves in the background, is UNKNOWN until tested on device. The default scope is the same as Android: a companion for preparation and practise. No date, no TestFlight promise, no store listing.

Feasibility UNKNOWN — Phase 4

Mac — dedicated native app, planning

A dedicated native Mac app is planned — not a port, a native shell. The audio candidate is ScreenCaptureKit, but permissions, hardware behaviour, notarization, and distribution are all still to be tested on device. Until that is done, Mac live assist is UNKNOWN and the scope is a native preparation app with manual question fallback.

Roadmap — five gated phases

The plan, with gates — not dates

Each phase has pass/fail exit criteria and pause criteria. A phase does not start until the one before it has evidence. No phase carries a calendar promise.

  1. Phase 1 — Documentation v2. The planning package behind this site: 71 documents, an audit, and a website checklist. Done
  2. Phase 2 — Website and Windows commercial launch. This site, the signed Windows installer, live Paddle checkout tested end to end, and final legal and support pages. In progress
  3. Phase 3 — Android companion and audio feasibility. Research artifacts and tests on 10+ devices/apps. Kill criterion: if real meeting-audio capture is not stable, permitted, and approved, the live-assist promise for Android is dropped. Planned
  4. Phase 4 — iOS and native Mac feasibility. Independent sign-off for each: a SwiftUI companion prototype and OS-level audio tests for iOS; a Swift-native Mac shell concept with ScreenCaptureKit tested on device. Planned
  5. Phase 5 — Growth, support, and product quality. Support, quality, and growth work on top of a launched, tested product. Planned

Full detail lives in the planning docs in the project repository — including the pause/kill criteria for each phase.

Next step: How your data is handled — what is recorded, what is never recorded.

Privacy & ethics →