Modaal: plan-led native iOS and Android development from a Mac workspace

Modaal describes a workflow in which an agent writes a product document and feature specifications for approval before coding. It produces local SwiftUI and Jetpack Compose projects and checks shared behavior through build fixtures.

Modaal is advertised as a Mac application for building native iOS and Android apps with an AI agent. Its workflow centers on approving a plan before generating code, then developing features and flows until the projects are ready for release.

How does Modaal approve a feature before coding?

The site describes an initial turn in which the agent reads an idea, product-requirements document, screenshots, or Figma link. It writes PRD.md at the project root and prepares a feature specification covering user scenarios, technical approach, implementation steps, affected files, risks, and testing.

The user reviews and approves that specification before coding begins. Keeping the documents in the project is intended to give later features the same reference as the first, rather than repeatedly recreating the design intent.

Modaal also offers Production, Duet, and Quick prototype architecture choices. The public page presents these as structures the agent follows; it does not supply evidence that every generated application is production-ready merely because that option was selected.

How does Modaal share behavior across native apps?

The described dual-platform approach uses a shared behavioral core with separate views: SwiftUI on iPhone and Jetpack Compose on Android. The page says both apps replay the same fixtures and a mismatch fails the build.

That is a stated parity check for the covered behavior, not a guarantee that all device features or edge cases behave identically. Users can start with one platform or both and add Android later. The Duet framework is described as open source.

The projects remain real Xcode and Android Studio projects in Git on the user's disk. Local native simulators support running them, while GitHub integration supports pushes, pull-request review, and team workflows.

What model access and release accounts does Modaal need?

Modaal says users can bring an existing Claude, ChatGPT/Codex, Gemini, Copilot, or other subscription instead of paying token-based API prices through that workflow. This is the vendor's integration claim, not proof of an official partnership or a guarantee that every account's plan grants every advertised use.

The page advertises a free plan without a credit card but does not state complete limits or paid pricing in the captured material. TestFlight and App Store distribution use the user's own Apple account.

The appeal is a visible approval process alongside local, editable native projects. Generated code, platform permissions, fixtures, and release settings still need review. The public description explains the intended workflow; Franklin has not built or submitted an app with it to establish its success rate.

Before you try it

Frequently asked questions

Does Modaal write code before a feature specification is approved?

The described workflow has the agent prepare a feature specification for the user to read, correct and approve. Coding begins after approval, with the specification kept in the project.

Official source
Does Modaal use the same interface code for iOS and Android?

The publisher describes shared behavior with platform-specific views: SwiftUI on iPhone and Jetpack Compose on Android. That design does not itself guarantee identical behavior for every device feature.

Official source
Whose Apple account is used to distribute a Modaal app?

The site says TestFlight and App Store distribution run under the user's own Apple account. Generated projects, platform permissions and release settings still require review before submission.

Official source