LocalView / Released · iOS + macOS
Developer files.
Without the cloud.
A native document viewer and editor that adapts to Mac, iPhone, and iPad while keeping processing on-device.
The file stays yours.
LocalView is a viewer and editor for developer-oriented text documents on Mac, iPhone, and iPad. It supports Markdown, JSON, property lists, TOML, YAML, NDJSON, XML, ENV, and plain text. Image documents are intentionally outside the product scope.
The goal is to make the file understandable without requiring an account or uploading its contents. Markdown has source and preview views; structured documents have appropriate editing affordances; outlines and search help with longer files.
Adapt the workflow, not just the width.
On Mac, document windows support desktop file actions, explicit Save/Save As, search, local recovery drafts, and structured JSON editing. On iPhone, a compact navigation row and actions menu keep the working surface usable. On iPad, adaptive source/preview controls and an outline sidebar use the extra space.
Mobile documents use native autosave, undo, coordination, and conflict handling. Shared document-format and rendering policies keep the file model consistent, while the surrounding interface follows each platform’s conventions.
Document opening is part of correctness.
The app retains SwiftUI’s standard DocumentGroup launch scene. Its operating documentation explicitly guards against replacing it with a branded launcher before cold document opening from Files is verified. That is a useful example of protecting an important behaviour even when a visual change looks attractive.
Document decoding, format detection, syntax tokenisation, search, preview rendering, and structured editing each have an explicit place in the implementation. Treating those boundaries separately helps the editor stay predictable as more formats and surfaces are supported.
A public native release.
LocalView is available through the App Store for iOS and macOS. Its public support and privacy pages document the local document-processing posture. The repository maintains separate macOS, mobile, project, and release-readiness validation routes.
The strongest part of this project is the continuity between a simple public promise—developer files kept local—and the native document behaviour underneath it.