A desktop visual editor for responsive websites and native app interfaces. Create layouts, reusable components and structured content in a local project. Export HTML/CSS for the web, SwiftUI for iOS and Jetpack Compose for Android. Native builds need Xcode or Android tools. Store workflows are experimental.

Modo is for designers, freelancers, students and small creative teams making websites and apps. Use it for a client project, a portfolio or a product of your own. The visual editor gives you direct control over the details, with code you can take into your next workflow.

Yes. Modo exports HTML/CSS for websites, SwiftUI for iOS and Jetpack Compose for Android. Each platform has its own behavior, so portability guidance shows what maps directly, adapts or needs attention. Building native apps requires the Apple or Android toolchain.

No. You can design with the visual editor on its own. If you want help, connect a compatible AI agent through MCP to read and change the same project. You can review and undo changes. Your AI provider may charge separately; your provider’s usage charges still apply.

Your project saves locally on your computer. Export a website to a local folder or ZIP, or publish through GitHub Pages, Vercel, Cloudflare Pages or Netlify using your own account. Keep your readable project and source files in your own Git workflow. Remote publishing is experimental and needs provider configuration and account-level validation. Provider charges are separate from Modo.

Modo includes native publishing workflows for iOS and Android: prepare builds and release plans, review prerequisites, and approve uploads to your developer accounts. iOS uses SwiftUI, with TestFlight and App Store review workflows; Android uses Jetpack Compose, with testing and release workflows. These remain experimental integrations requiring configuration and validation with your accounts. Store materials are exported for manual console upload; preparing a listing is not automatic store submission. You need the relevant build tools and developer accounts. Store listings, fees, testing requirements and approval remain part of the Apple or Google process.

Local projects work on your computer after initial online activation. Shared reviews and live editing require a separately configured team service and an internet connection. The shared canvas is a separate authoritative copy; download a .modo copy to bring it back locally. It is not continuous synchronization of your original project. See Learn MODO for setup and limitations.

MODO is free to download and use. No payment details required. We’re building toward collaborative open source: community ideas and contributions, reviewed by Gianluca Boccia. The code and contribution process are not public yet. For now, join the beta, try real projects, share ideas and report bugs. The manifesto explains the direction; a licence and contribution guidelines will accompany a future code release.

Enter your name, email and operating system. macOS and Linux requests share a maximum of 1,000 beta places; repeating the same email does not take another. Mac Apple Silicon (M1 or newer, macOS 13 Ventura or later; Intel Macs are not supported) is available: after signup, open the personal access link in your email, confirm your website access, and download the verified DMG. Install it and sign in inside MODO with the same email. Confirm the magic link to access MODO; no manual approval is needed. Linux is available for Debian 13 with X11, on x64 and ARM64. After you confirm email ownership, your private downloads area lets you choose the architecture and .deb or AppImage; run uname -m if unsure. Other distributions and Wayland have not been verified. Windows is a separate updates list: it takes no beta place, grants no app access, and sends a confirmation followed by an availability email when ready. Existing members can request a fresh download link from the downloads area without taking another beta place. Check Spam or Junk if an email is missing. See Downloads & beta status for current requirements.

Use MODO on a real idea, expect bugs, and help us find and report them. Use Help → Report an issue, review an optional screenshot, and send when connected. You can also contact bug@inmodo.app. Keep backups of important projects while testing.

You do. Your Modo project lives in local, readable files, and the exported source code is yours to use and take into another workflow. You can keep your project in Git and choose where to go next.

We store your first and last name, email, operating system, optional country or region and the relevant consent: the beta bug-reporting rule or Windows availability updates. These manage your request and its communications. There is no automatic newsletter sign-up. Your first name and country (if supplied) appear in the participant carousel only if you opt in. Emails and surnames are never published. Windows registrations record consent to Windows availability emails instead of the beta bug-reporting pact. They do not enter the public beta participant stream. For privacy or deletion requests, contact info@inmodo.app.

Yes. In alpha.4, create a dedicated Design System project, organize variables and components, and save an immutable local version. Share a .modo-library file or link it to another project. Each project keeps a complete offline snapshot, even without the source folder. Review and apply new versions explicitly; instance overrides are preserved and the update can be undone. Linked masters are protected, or you can detach an independent copy. Collections use project-wide modes. Nested library dependencies and automatic breaking-change migrations are not included. Follow the Design System guide in Learn MODO.

Use MODO Design Bridge to export selected frames or an entire file as .modo-figma.json. Alpha.4 imports into Playgrounds, including from Welcome; it does not force three responsive breakpoints. Supported components and color, number, text and boolean variables are included. Review the conversion report, fonts and assets. Native .fig files must first be opened in Figma and exported through the bridge. This is not a perfect or lossless round trip.

From alpha.4, use Help → Check for updates, or allow the optional check when MODO opens. Control this in App & profile. MODO never downloads or installs an update automatically; offline work continues. The check sends no project content, account identity or activation token. Alpha.3 users receive their first update by email, not an in-app alert. Release emails link to verified downloads and let you stop these notices without losing beta access or magic links. Save a .modo backup before installing: newer variables and Design System metadata may not be editable in older versions.