DigiFX does not currently ship a native iOS or Android application. Mobile access is delivered through the browser, with one separately built mobile web interface for operations. This page is about how that decision is implemented, and what it costs.
01Responsive web, not a native shell
The Media Console is one web application served to every device. Its page shell declares the standard viewport meta tag and the Apple web-app meta tags — web-app capable, status bar style, and application title — so that adding it to an iOS home screen produces a full-screen launch rather than a browser chrome window.
Layout adaptation happens in CSS. Breakpoints live in the component stylesheets alongside the components they affect, rather than in a central responsive layer, which keeps a component's small-screen behavior in the same file as its markup.
The absence is as informative as the presence: there is no Capacitor, Ionic, Cordova, or React Native dependency anywhere in the project, and no ios/ or android/ native project directory. Nothing in the build produces an app bundle. Anything the console does on a phone, it does through the browser.
02A purpose-built mobile interface for the Master Controller
The one exception is the Master Controller's mobile command interface, which is its own application rather than a responsive view of the desktop one. It is built with React, Vite, TypeScript, and Tailwind, and its tab structure mirrors the desktop panels: a system overview plus one tab per operational panel, each with its own accent color matched to the desktop tokens.
It exists as a separate codebase because the information design is genuinely different. The desktop layout is a multi-panel wall of simultaneous state; the mobile layout is a sequence of single-focus tabs. Shrinking the former does not produce the latter. Its checks are lightweight — a type-only lint pass and a standard bundler build.
03What this trade-off buys and costs
Staying on the web removes an entire release train. There is no app store review queue between a fix and its users, no separate versioning scheme, no divergence between what desktop and mobile users are running, and one deploy pipeline instead of three.
The cost is that capability is bounded by what each mobile browser exposes. Device integrations, background execution, and storage behavior all vary by platform and browser version, and the heavier media tooling in the console is built for a pointer, a keyboard, and a large canvas. The honest position is that the console is usable on a phone for review and light work, and built for a desktop for production work — but the exact per-feature line has not been documented and should be before this page is published.