01Native iOS apps
Swift and SwiftUI apps built for iPhone and iPad, designed to Apple’s standards and shipped through the App Store.
02 / appssource → compile → run
Serious code for serious products.
Behind every good interface is engineering nobody sees: data models, APIs, real-time pipelines, security, releases. It’s the part we enjoy most — and the part that decides whether a product lasts.
↓ scroll — the source compiles as you read
01source
What we engineer
Websites are where many projects start. These are the systems behind them, and the products that stand on their own.
02Android & cross-platform
Kotlin for native Android, or Flutter and React Native when one codebase for both stores makes more sense.
03Desktop applications
Cross-platform macOS and Windows apps in Electron and TypeScript — signed, notarised and self-updating.
04Web platforms & SaaS
Multi-user products with accounts, roles, subscriptions and billing, built to grow from ten users to ten thousand.
05APIs & integrations
REST and GraphQL APIs, webhooks, and connections to the services you rely on — Stripe, TWINT, bexio, CRMs and more.
06Real-time systems
WebSocket feeds, streaming data and worker-thread pipelines that stay fast when thousands of updates arrive every second.
07Databases & data modelling
MySQL, PostgreSQL and NoSQL, designed properly from the start, with migrations, backups and room to scale.
08Cloud & serverless
AWS, Google Cloud, Azure, Firebase and Cloudflare Workers — lean infrastructure with nothing running that doesn’t need to.
09Web3 & fintech
Non-custodial wallets, on-chain settlement and trading tools, engineered for security first — see our Desk case study.
10Data pipelines & automation
Collecting, cleaning and moving data between systems on a schedule, with monitoring when something breaks.
11Security & compliance
Authentication, encryption, secure key handling and code signing, built for the Swiss FADP and the GDPR.
12Releases & DevOps
Automated builds, App Store and Play Store submissions, notarisation, over-the-air updates and error tracking.
02compile
Our stack — and how we choose it
We pick the right tool for the job, not the one that’s trending. That’s why our projects last.
- Mobile. Swift and SwiftUI for iOS; Kotlin for Android; Flutter or React Native when cross-platform is the smarter call.
- Web. HTML, CSS and JavaScript, TypeScript, React, Next.js, Astro, Flask and Python, and WordPress where a CMS fits best.
- Desktop. Electron with TypeScript and esbuild, split into isolated processes, with worker threads for heavy lifting.
- Data. MySQL, PostgreSQL and NoSQL stores, chosen for the shape of the data and how it will be queried.
- Infrastructure. AWS, Google Cloud, Azure, Firebase and Cloudflare Workers, KV and R2 — serverless wherever it keeps things simpler.
- Quality. Code review, automated tests, real-time error tracking and performance monitoring on everything we ship.
03run
Shipped, signed and maintained
Code that isn’t running in front of real users isn’t finished. We take it all the way, then stay involved.
- 01 — Release. App Store and Play Store submissions, notarised and signed installers, automatic updates — the unglamorous steps done properly.
- 02 — Observe. Error tracking, performance monitoring and alerts, so we hear about problems before your users do.
- 03 — Maintain. Operating systems update, frameworks change: patches, upgrades and new features — or a clean handover if you outgrow us.
See it in practice: how we built Desk, a real-time trading terminal →
Questions we hear a lot
Native or cross-platform?
Native (Swift, Kotlin) when performance, polish or deep device features matter most; Flutter or React Native when one team and one codebase for both stores gives you more for your budget. We’ll recommend one and explain why.
How long does an app take?
A focused first version usually takes six to twelve weeks. We ship the core first and build on it, rather than disappearing for six months.
Can you take over an existing codebase?
Yes. We start with a review of the code, infrastructure and risks, then either improve what’s there or plan a careful migration.
Who owns the code?
You do. The source code, accounts and infrastructure are yours, documented so any competent developer could pick them up.
Do you publish to the App Store and Google Play?
Yes — developer accounts, store listings, review guidelines, submissions and updates are all part of the job.