# busy.dev > busy.dev is an AI-driven app studio that takes an app idea end to end: it researches, designs, builds, tests and releases native Android and iOS apps with an AI pipeline and a farm of real phones, then keeps them running after launch. It is run by EFIRITY PTE. LTD. (Singapore). There are no public prices: every project starts with a message, and busy.dev replies by email with what it would take and the next steps. ## What busy.dev does - Native apps on both stores: a real Android app (Kotlin, Jetpack Compose) and a real iOS app (SwiftUI), not a web page in a wrapper. - Five languages from day one: English, Spanish, Brazilian Portuguese, Hindi and Russian. - Built in from the first screen: Sign in with Apple and Google, in-app account deletion, store or web payments, Play Integrity and App Attest device checks, TLS pinning, push notifications with an in-app inbox, and accessibility (large touch targets, text up to 200%, screen-reader labels). - Clients follow every stage live in the busy.dev app and at https://portal.busy.dev. ## How an app is built (9 stages) 1. Idea: you describe the app in a few sentences, who it is for and what it should do. 2. Research: rival apps in each store, their 1–2★ complaints, feature requests and who pays, ending in a go or no-go. 3. Name: candidates checked against Google Play, the App Store and domains. 4. Design: AI mockups of every screen in light and dark, a design system and a UX check. 5. Build: Kotlin and Jetpack Compose on Android, SwiftUI on iOS, sign-in, payments and security from the first build. 6. Test: installed from the store on a farm of real Android phones and iPhones, including real in-app purchases. 7. Store: listing, screenshots and graphics in five languages, plus public privacy, terms, support and account-deletion pages. 8. Release: Google Play internal testing then production; TestFlight then App Review. 9. Live: crashes, ratings and reviews watched, reviews answered and updates shipped. - [How we build](https://busy.dev/process): the whole line, scene by scene ## Apps busy.dev shipped (live on Google Play) - [Contito](https://play.google.com/store/apps/details?id=dev.busy.contito): tally counter with home-screen widgets; no ads, no internet, no data collected - [Turnimo](https://play.google.com/store/apps/details?id=dev.busy.turnimo): shift-work calendar with rotating patterns, hours, pay and partner sharing - [Rodalo](https://play.google.com/store/apps/details?id=dev.busy.rodalo): fuel log and car expense tracker with cost per kilometre and service reminders - [Fonomo](https://play.google.com/store/apps/details?id=dev.busy.fonomo): decibel meter in dB(A) and dB(C) with Leq, peak, octave spectrum, noise dose and reports - [Nilbite](https://play.google.com/store/apps/details?id=dev.busy.nilbite): intermittent fasting timer with a widget and a journal - [Faltino](https://play.google.com/store/apps/details?id=dev.busy.faltino): days-until and days-since widgets made from your own photos - [Metrino](https://play.google.com/store/apps/details?id=dev.busy.metrino): ruler, bubble level, protractor, compass, light and sound meter in one app - [Velisto](https://play.google.com/store/apps/details?id=dev.busy.velisto): GPS speedometer with a windshield head-up display mode - [Work](https://busy.dev/work): all apps with screenshots ## busy.dev MCP server - [MCP server](https://busy.dev/mcp): connect Claude, ChatGPT or any MCP client to a busy.dev workspace - Server URL: https://mcp.busy.dev/mcp (Streamable HTTP, OAuth 2.1 sign-in with a busy.dev portal account, dynamic client registration) - Status: rolling out now. Available to busy.dev customers with a portal account; accounts are created by the busy.dev team ([contact](https://busy.dev/contact)), there is no self-service signup. - Tools: apps and each app's stage, store status (Google Play, App Store, TestFlight), what needs attention, ideas and research status, similar ideas, submit an idea or save a draft, add notes, file improvement requests for an app, read the inbox. You can also review your approvals (preview, then confirm). - Every write asks for confirmation; access is scoped to the user's own workspace. Busymate, the AI chat on busy.dev, uses the same tools. - Claude Code: `claude mcp add --transport http busydev https://mcp.busy.dev/mcp` ## Contact - [Contact form](https://busy.dev/contact): describe the app you want to build; busy.dev replies by email - Email: hi@busy.dev - [Support](https://busy.dev/support): help for people using busy.dev apps ## Optional - [Full text for AI assistants](https://busy.dev/llms-full.txt) - App help and policies follow one pattern: https://busy.dev/apps//support, /privacy, /terms (and /delete-account for apps with accounts) - [Privacy policy](https://busy.dev/legal/privacy) - [Terms of use](https://busy.dev/legal/terms)