Atomic AI for Android with production build lanes, secure mobile auth, and live Atomic Lexy connected to the control room.
The mobile surface is focused on the highest-value actions first: secure sign-in, session restore, live Atomic Lexy continuity, and real access to the Atomic AI system when the operator is away from the main console.
The first mobile release focuses on Android access to the Atomic AI control room with secure session restore, live Atomic Lexy threads, and direct connection to the existing local-first server.
That gives operators a real mobile surface for conversation and system access instead of a stretched browser view.
The app now has Expo and EAS build configuration, Android package settings, release profiles, and environment-driven API routing for preview and production lanes.
That means the mobile project can move into signed Android builds without redesigning the app structure later.
After Atomic Lexy, the next mobile surfaces are Operator OS missions, learning memory, and commercial state so the strongest parts of Atomic AI travel with the operator.
The goal is not feature parity with the desktop surface on day one. The goal is a deliberate mobile command lane.
The Android app is a platform surface. Hat Tracks and Red Hat Radar are commercial knowledge products. Keeping those lanes separate makes pricing clearer, product intent cleaner, and the Atomic storefront easier to understand.
That gives Atomic AI room to treat mobile as a companion surface first, then later decide whether it becomes free access, premium inclusion, or a dedicated mobile access tier.
It should support operators who need continuity, clarity, and access on the move without dumping the entire desktop system into a phone-sized viewport.