Native app development · Built with Perry
Native apps from one TypeScript codebase
We build your app once in TypeScript and compile it to a real native binary for every platform you need. No Electron, no embedded browser, no JavaScript engine shipped with your app. And because we wrote the compiler, we are not waiting for anyone else when something has to work.
- iOS
- iPadOS
- Android
- macOS
- Windows
- Linux
- watchOS
- Wear OS
- tvOS
- visionOS
- Web
The usual trade-off, and how we avoid it
Separate native teams
One team for iOS, one for Android, one for desktop. Every feature is built and tested several times, and the versions drift apart.
Wrapped web apps
One codebase, but each app carries a browser or a JavaScript runtime. Large downloads, slow starts and the feeling that something is off.
Compiled TypeScript
One codebase in a language your team already knows, compiled ahead of time to a small native executable per platform. That is what Perry does.
What you get
11 platforms
From phones and tablets to desktop, watch, TV and the web, from the same source code.
Small binaries
A compiled hello-world is about 330 KB. A complete desktop app such as Mango is around 7 MB.
Your team can read it
The code is standard TypeScript. Your web developers can review it, extend it and take it over.
No lock-in
Perry is open source under the MIT licence. The code we write for you belongs to you.
How a project runs
- 1
Scope
A short workshop to pin down what the first version must do, on which platforms, and what can wait.
- 2
Prototype
A working build on real devices early, so you judge the app by using it, not by slides.
- 3
Build
Short iterations with a build you can install after each one. Fixed scope and price where possible.
- 4
Launch and care
Store submissions, monitoring and updates. Most of our clients stay with us for ongoing development.
Is this a fit for you?
A good fit if
- your app should run on several platforms without several teams
- you already have TypeScript code or TypeScript developers
- download size, start-up time and memory use matter to you
- you want a partner who can change the toolchain when needed
Probably not if
- you only ever need one platform and already have a native team for it
- your app depends on a large existing React Native or Flutter codebase you want to keep
In those cases we tell you so, and we also build with Swift and Kotlin where that is the better choice.