Android 8.0 or later
The cabin features support Android API 26+. The optional Adult assistant requires a 64-bit device plus sufficient free storage and memory for the selected local model.
Setup and readiness guide
Start a cabin with the right expectations.
Choose the right edition, understand every permission, and know exactly what has—and has not—been validated before you travel.
01 · Choose an edition
Adult and Family are intentionally different.
iOS or iPadOS 17+
Core cabin features support version 17 and later. The assistant needs iOS/iPadOS 26+, eligible Apple Intelligence hardware, Apple Intelligence enabled, supported language settings and the downloaded system model.
| Capability | Adult Android | Adult iPhone / iPad | Family Android · 13–17 |
|---|---|---|---|
| Entry | Tower approval | Tower approval | Adult-issued QR only |
| Chat and files | Included | Included | Not included |
| Calling | Direct media when the LAN allows it | Direct media when the LAN allows it | Not included |
| Games | Included | Included | Five allow-listed games |
| Assistant | Optional downloaded on-device model | OS-managed on-device model when supported | Not included |
02 · Adult setup
The Tower makes admission a human decision.
- 1
Choose the Tower
One adult device starts the cabin and stays open while nearby passengers use it.
- 2
Join the same local network
Use the Tower hotspot or the same trusted Wi-Fi. Cabin traffic does not need the public internet.
- 3
Review the chosen name
The Tower sees the passenger’s chosen, unverified name and must explicitly allow or reject the request.
- 4
Keep the Tower available
Closing the Tower ends the cabin. File serving on iPhone and iPad also requires the sender to keep CabinMesh open.
Identity boundary
A displayed passenger name is chosen by that passenger and is not identity verification. Allow only someone you expect on the nearby network.
03 · Family enrollment
A live QR scan opens a games-only space.
Create a deliberate invitation
Assign the young traveller’s roster name, keep both devices on the same private Wi-Fi, and show the short-lived, single-use QR.
Scan automatically with the live camera
Center the QR in the scanner. Enrollment does not require a shutter button or saved photograph. After acceptance, only the allow-listed games are available.
Family has no public discovery, chat, files, calls, ads, purchases or generative AI. The invitation is a technical access control; it does not replace any consent required by local law.
04 · Permissions
The app checks first and explains why.
Required permissions are checked when the app opens. If something is missing, a large gate appears before the cabin. Closing the gate dismisses it only for the current active session; returning to the app checks again. A system-level denial may require Settings.
05 · Safety and privacy
Local-first does not mean invisible limits.
Adult and policy acknowledgement
The Adult app requires all age, Terms, Privacy and Safety acknowledgements before continuing.
Block locally
A passenger can be blocked on the device without publishing an internal identifier in the interface.
Report evidence is opt-in
A report is saved locally first. A content or filename preview is included only after the reporter explicitly enables it.
Server intake is not live yet
Delivery needs internet and an available HTTPS intake. The production intake remains disabled until its backup and operator controls pass their release gates.
06 · Verification record
Automated evidence, with a clear boundary.
On 24 August 2026, the freshly rerun iOS scope contained 137 distinct tests across the app, Safety, Calls and UI suites. The complete documented iOS inventory contains 271 distinct methods; repeating the same 11 UI tests on an iPhone 17 Pro Max simulator and a 13-inch iPad Pro simulator produces 282 recorded executions.
App and integration tests
Safety package tests
Call-engine tests
iPhone UI tests
iPad UI tests
What this proves
Source behavior, package contracts and the tested iPhone/iPad simulator flows passed without a test failure.
What it does not prove
Physical-device permissions, a real multi-device LAN, microphone/camera quality, live peer calls, store approval or public availability.
Adult AndroidClosed testing
No public store link is published on this site.
Family AndroidNew source needs exact-build review
Do not reuse older reviewer evidence for a newer build.
iPhone and iPadBuild 5 is older than local source
The follow-up test and hardening changes require build 6 or later.
These checks include local source changes made after submitted iOS build 1.0.1 (5). A newer uploaded build is required before those changes can reach testers or customers.
Backend migration note: the current iOS source still uses flightnet-policies.avititievsky.chatgpt.site for policies and reports. It must not be described as migrated to policies.cabinmesh.com until the custom domain has working DNS and TLS and the app endpoint is changed and retested.
07 · Troubleshooting
Start with the local connection.
I cannot see or join the cabin.
Confirm both devices are on the same trusted Wi-Fi or Tower hotspot, reopen CabinMesh, and allow the local-network or nearby-device permission.
My request is still waiting.
The Tower must explicitly allow it. Ask the host to review the chosen name shown on the Tower device.
A call connects without usable audio or camera.
Check microphone and camera permission on both devices. A simulator or engine test does not confirm the quality of a real local-network call.
A file stopped downloading.
Keep the sending app open and both devices on the same local network. iPhone and iPad do not serve cabin files while CabinMesh is in the background.
The Family QR does not scan.
Use the live scanner, keep the entire QR inside the frame, improve lighting, and confirm both devices remain on the same private Wi-Fi before creating a fresh invitation.