harness.today

What It Is

Deux is an AI developer tool for mobile app migration. Its core goal is to automatically convert existing iOS/Xcode projects into runnable native Android codebases. The website positions it as “Your iOS app, running on Android” and “In hours, not months,” and offers a macOS DMG download. At the moment, it appears to be in Early Access.

Core Capabilities and Technical Boundaries

Based on the captured content, Deux’s workflow is: users download the desktop app, hand an Xcode project to the tool, and the AI reads the project architecture, plans the migration, and generates a native Android codebase. This positioning is very clear, making it suitable for teams that already have an iOS product but lack an Android version. However, the page does not specify its exact support scope for Swift, Objective-C, UIKit, SwiftUI, or whether the Android output uses Kotlin, Java, Jetpack Compose, or XML Views. It also does not explain how complex business logic, third-party SDKs, push notifications, payments, Bluetooth, maps, and other native capabilities are migrated. As a result, it is better treated as a migration draft or evaluation tool rather than a full replacement for human Android development by default.

Pricing, Deployment, and Integrations

The public page does not disclose pricing, licensing, free quotas, or enterprise plans; only Early Access and a macOS download entry are visible. In terms of deployment, it emphasizes running through the Deux desktop app locally against an iOS codebase, but does not clarify whether it is fully offline, whether code is uploaded to the cloud, or whether self-hosting is available. There is also no visible information about API/SDK, CLI, CI/CD, Android Studio, GitHub, or other integrations, and the documentation appears limited.

Pros, Cons, and Who It’s For

The main advantages are its focused use case, simple onboarding path, and goal of generating a native Android codebase, which in theory should be easier to maintain over time than a pure wrapper-based approach. The downside is a lack of transparency: the technical support matrix, migration accuracy, code quality, security and compliance posture, pricing, and support options are not explained in detail. It is a fit for iOS teams, startups, or mobile engineering teams that want to quickly validate the feasibility of an Android version. For large enterprises and highly regulated industries, the source-code handling process and licensing terms should be confirmed first.

China Access and Alternatives

There is not enough information on the page to determine access from mainland China, download speed, or supported payment methods, so these remain unknown for now. If access or compliance becomes a constraint, alternatives include a manual native Android rewrite, Kotlin Multiplatform, Flutter, React Native, Capacitor, or using general-purpose AI coding assistants to support the migration in stages.