Install & Build

Install Fanta 1.0.0 Public Alpha

The first public distribution targets Apple Silicon Macs. Use the official download page for current availability, the immutable installer, checksum and macOS versions actually tested for that package. The public label is Public Alpha, the app version is 1.0.0, and the internal release channel is stable.

The final Build45 package is Developer ID signed, Apple-notarized and stapled. Distribution and tested installation checks have passed. The Public Alpha is available through the official download page. The launch overview and three workflows have been reviewed on this signed app.

The accepted package is bound to source 57d86330289153ead8a3bdbd114e1fa530a74e03. Its Fanta-aarch64.dmg SHA-256 is:

5e6b68605bbb601e70778acb2b8fcf72186d1b9a368b7947554f316ab96b87b8

On 12 October 2026, an authenticated Chrome draft download retained quarantine and passed Gatekeeper as Notarized Developer ID. Native edit, Save, normal Quit and reopen passed. Finder replacement with the same signed build preserved the saved change after reopening, and the installed bundle matched the accepted signed bundle. After publication, an anonymous public Chrome download matched the accepted DMG checksum. These checks do not establish clean-account installation or migration from an older version.

1. When the download page reports availability, download Fanta-aarch64.dmg and SHA256SUMS.txt from its linked GitHub prerelease.

2. Verify the checksum in the folder containing both files:

   shasum -a 256 -c SHA256SUMS.txt

   Continue only when the installer reports OK.

3. Open the disk image, drag Fanta into Applications, and eject the image.

4. Open Fanta from Applications. macOS may ask you to confirm opening an app downloaded from the internet.

5. Follow the ten-minute exercise.

The accepted package has passed signature, notarization, stapling and Gatekeeper checks. If Gatekeeper refuses the public installer, stop and report the dialog to support@fantaisa.net. Do not remove quarantine or bypass Gatekeeper. Earlier ad-hoc-signed internal QA packages retain their original identities and are separate artifacts.

Requirements

The signed Build45 package was tested on an Apple Silicon Mac running macOS 27.0 (26A428). A minimum supported macOS version has not been established. Check the download page for the tested versions of each package. Intel and universal installers are outside this release.

Manual updates

Automatic updates are disabled in this alpha. Save work, close Fanta and back up the complete project folder before replacing the app. Download the newer public installer, verify its checksum and drag its Fanta app into Applications. Choose Replace, keeping your project and application data folders. Reopen the sample, make an edit, save and reopen it before continuing important work.

Limits and support

Start with a copy of a small project. Imported Figma structures and rendering can differ. Code edits supported FNX and managed JSON, while Saved Code in Dev mode is read-only. Source drafts can lock conflicting canvas edits, and saving several source buffers is sequential rather than an atomic rollback operation. Review project trust prompts and keep manifests, identity sidecars and assets with the source. Current capabilities and limitations.

In a 12 October 2026 signed Build45 recording, Code showed Could not refresh saved source: oneshot canceled after a canvas Save. The saved FNX retained the edit and reopening that project restored the source view. Verify the saved change and resolve any unsaved drafts before closing, then reopen before editing source. Report a persistent warning or a saved-source/canvas mismatch. See source refresh troubleshooting.

Use the verified community and issue-reporting links on the download page for reproducible bugs. Include app version, macOS, steps and expected versus observed behavior. Send account and billing reports privately to support@fantaisa.net.

A separate Mac App Store feature build exists in source. It is a different packaging route and does not establish public Store availability. The installer and external-agent guidance on this page describe the direct-download build.

Build from source

Clone the fanta-edit repository, install its Rust and macOS build dependencies, and run from the repository root:

cargo run

The Cargo package and its binary are both named fanta. Use cargo build --release -p fanta for a release binary. The repository uses ./script/clippy for linting. The release verifier's --stage lint checks twelve editor and engine crates with all features, then separately checks fanta-format, fig_viewer, and fs with default features.

Maintainers can enable build diagnostics on a manual macOS release workflow run. This opt-in setting records bounded CPU, memory, disk, and swap progress during the Cargo build and retains Cargo timing reports when produced. It is disabled by default and requires GitHub Actions CI. Diagnostic output helps investigate a build; it does not establish signing, notarization, installation, or release readiness.

Mac App Store build differences

A build compiled with mac_app_store is sandboxed. It does not ship the CLI helper or bundled Git runtime and does not automatically initialize Git repositories. It cannot launch command-backed MCP servers, external agent processes, terminal tasks, or external formatters from inside the app, and remote project connections are disabled. Remote HTTP MCP servers remain available.

All new AI credit and subscription purchases use web Billing. The current public non-Store DMG supports web checkout. Native Store web-billing controls are a source change for the next app release; the backend already prevents the retired Apple purchase, restore, offer-code, and trial paths from granting AI credits. Public accounts receive no signup, referral, or trial credits. Existing founder exceptions are restricted on the backend. Previously purchased Apple subscriptions must still be canceled in the Apple Account.

The in-app live canvas MCP server is a separate setting, but an external client's bridge to a packaged Store build still needs validation. File access follows macOS user-selected Open and Save permissions. See Settings and build differences.

Next choose File → New Design… or File → Open… to import a .fig file. See Your First Project.