Thunkable review

Thunkable is a hosted app-building platform, not a library, CLI or self-hosted server. It sits between an app idea and the native mobile app: you describe what to build, then its AI generates screens, layouts and logic inside a project that you can continue editing. The platform brings that generation together with a visual editor, a Code Editor and Version History.

The target output is native iOS and Android apps, with web publishing also listed. You can preview a project on a phone before publishing. The homepage says apps can use more than 25 device features, including camera, barcode scanning, GPS and maps, push notifications, biometrics, NFC and Bluetooth. It also lists email, Google and Apple sign-in, plus connecting a free Supabase account for a cloud database.

In a stack, Thunkable owns the build workflow and publishing path. It is aimed at people who need app screens, logic and device integrations without building the entire mobile project from scratch.

The build workflow is primarily a hosted editor: describe the app, refine it with AI or Discuss Mode, then use the visual editor or Code Editor for changes. Version History lets you roll back changes. Thunkable also describes phone preview, publishing guides and AI checklists as part of testing and launch.

The homepage does not name a REST or other API protocol, SDK, programming language, CLI or plugin system. It does identify integration points at the product level: Supabase for a cloud database, email/Google/Apple sign-in, and native device features such as GPS, camera and Bluetooth. Teams planning custom services or code-level integrations should check Thunkable’s docs and confirm SDK and API support before choosing an architecture.

This is a different workflow from adopting a mobile SDK in an existing codebase. Thunkable’s public materials center on building within its project editor, rather than installing a package into an independently managed app. The homepage links to Docs and Integrations, but specific protocols and language support should be verified there.

The Free plan costs $0 and includes 2,000 AI tokens, three public projects and five screens per project. It allows no private projects and no app publishing, so it is for exploration rather than shipping. Accelerator is $19 per month, or $18 per month with annual billing; it includes 20,000 tokens, one private project and 10 screens per project. The plan also lists Intercom support.

Builder costs $59 monthly or $37 per month with annual billing. It includes 50,000 tokens, 10 private projects, unlimited screens and one live published app. Advanced costs $189 monthly or $99 per month with annual billing, and raises the included token allowance to 100,000 while allowing unlimited private projects and live published apps. Enterprise has custom pricing; Education lists a discount after application.

The pricing page lists no add-ons. It does not publish token overage rates, so ask what happens if a project exceeds its allowance. Costs also step up when you need more private projects or published apps. Annual billing lowers the listed monthly price for Accelerator, Builder and Advanced.

Thunkable is presented as a hosted platform. Its homepage and pricing information do not list an open-source licence or a self-hosting option, so teams should treat it as a vendor-operated service unless Thunkable confirms otherwise. The public materials here also do not establish whether projects can be exported as portable source code or moved to another builder.

That leaves portability as a procurement question, not a safe assumption. Before putting production work into the platform, ask what project data and assets can be exported, in what formats, and whether generated app code can be maintained outside Thunkable. Also confirm what happens to published apps if a subscription ends. If a team needs a fully owned mobile codebase or a self-hosted build system, verify those requirements with the vendor before committing.

Thunkable lists native publishing, phone previews and more than 25 device features, but those capabilities do not answer every production question. Confirm the current app-store publishing requirements, project limits, service reliability, security controls and compliance terms with the vendor before making the platform a critical part of a release pipeline. The published plan limits matter too: Builder includes one live app, while Advanced includes unlimited live published apps.

A Reddit commenter describes Thunkable as taking time to learn and reports problems with a newer layout framework, including absolute positioning and poor results on larger screens. That is an individual account, not a current platform guarantee, but it makes responsive behavior worth checking on target devices. Another Reddit post from a beginner says the tool was complicated and took time to understand.

Test the app’s actual layouts, device integrations and publishing path before relying on them. Ask Thunkable about service-level commitments, backups, security documentation and recovery procedures; the homepage does not make those production details clear.