Custom mobile apps.
Krafter designs and builds custom mobile apps for iOS and Android, in Flutter, from a single codebase. For your field teams, your clients or a product to launch: an app published on the App Store and Google Play, and adopted by its users.
Installed. And used.
The reality
80% of apps are uninstalled within 3 days. The problem is almost never technical.
Most mobile app projects fail before the technology even comes into play. The app doesn’t solve the right problem. The user journeys are confusing. The onboarding makes no sense. The features are too many or too little used. The app was built to tick a box, not to solve a daily problem.
On the other side, many contractors sell mobile development as a technical service: you provide a spec, they deliver screens, good luck with the rest. Nobody asks whether people will actually use what was built.
At Krafter, mobile development always starts with the same question: who will use this app, and why would that person open it rather than anything else?
Use cases
10 field users or 10,000 customers: the right app.
Field team app
#1Job reports, routes, data entry, geolocated photos, back-office sync. Reliable even when the network isn’t.
Let’s talkConsumer app
#2The challenge isn’t just technical: onboarding, retention, the ability to bring people back day after day. Designed for adoption, not just for publication.
Let’s talkMobile companion for your SaaS or ERP
#3Your web platform exists, your users move around. The app connected to your system, real-time sync, critical data in your pocket.
Let’s talkMobile MVP
#4Test a concept on mobile before investing heavily: an MVP publishable on the stores, testable by real users, in 8 to 12 weeks.
Let’s talkWhy Krafter
A studio that operates its own apps, with thousands of users.
Melimelo, our home organization app, is rated 4.7/5 on the App Store (421 ratings) and 4.6/5 on Google Play (306 reviews) as of October 2026. It accounts for most of the 25,000 people who use our products every day. Over 50 versions published. It has kept up with every iOS and Android update, absorbed load spikes, and evolved with hundreds of pieces of user feedback.
Trottr, our field service management software, made the other choice: a progressive web app (PWA), installed on technicians’ phones without going through the stores. Native app or PWA is a scoping decision, and we run both in production.
This isn’t theory, it’s production experience. When we build a client’s app, we know what’s waiting after publication: crashes on older devices, Apple review rules that keep tightening, the first user who finds a flow confusing, the push notification that won’t show on a Samsung. We learned to handle all of it on our own apps before anticipating it on yours.
Conviction
“On mobile, technical debt catches up with you twice as fast. A shaky architecture shows at the first crash in production. That’s why we build every app to the same standards as our own products: if it wouldn’t hold up under Melimelo and its thousands of users, we don’t ship it to a client.”
François Pluchino
Co-founder & CTO, Krafter
How we work
From user need to store publication.
An app for a technician in the rain and an app for a parent on the couch are not designed the same way. The process starts there.
01 / 04
Scoping
1 to 2 weeksPriority use cases, user profiles, context of use: office, field, transit, home.
We identify who will open the app, in what conditions, and what it has to solve day to day, before drawing the first screen.
User journeys
Mockups screen by screen. Every flow, every interaction, every edge case validated before coding.
On mobile, a UX mistake costs more than anywhere else: an unhappy user uninstalls in 3 seconds, and never comes back.
Development and real-world testing
deliveries every 1 to 2 weeksEvery version installs on your devices. You test for real, not on screenshots.
Multi-device testing, offline mode handling, denied permissions, interruptions by incoming calls.
Publication and support
Store listings, submission, Apple review follow-up, publication. The accounts are in your name.
Apple and Google developer account creation if needed, screenshots, descriptions, keywords: you keep ownership of your presence on the stores.
The technical side
Do you need two apps for iOS and Android?
No. Krafter builds with Flutter, a framework created by Google that produces an iOS app and an Android app from a single codebase. It’s not web wrapped in a shell: the code compiles natively, performance matches pure native, and access to the phone’s features is complete. One build, one budget, one test cycle, one codebase to maintain.
- Framework
- Flutter, in production at Krafter since 2024.
- Platforms
- iOS and Android from a single codebase.
- Performance
- Native compilation, identical to pure native.
- Hardware access
- Camera, GPS, Bluetooth, push, biometrics, local storage.
- Offline
- Local storage and deferred sync when the use case requires it.
- Proof
- Melimelo runs on it every day, on iOS and Android.
FAQ
Field app, consumer app, mobile companion for your platform: we start by understanding your users, not by talking tech.
Discuss my mobile projectBefore launching your mobile app.
A mobile MVP runs from €6,000 to €25,000 excl. VAT, store publication included. It starts at €6,000 when you know exactly what you want: processes, business rules and screens already defined. The price goes up if we need to shape the thinking with you, integrate payments or go up to 5 to 8 screens with authentication. A complete application with back office, API sync, push notifications and built-in payment: €25,000 to €60,000 excl. VAT. Maintenance is budgeted separately.
An MVP takes 4 to 8 weeks of development and 8 to 12 weeks to reach the stores. A more complete application takes 3 to 5 months. Apple reviews most submissions in under 24 hours; on Melimelo, a review usually takes 1 to 2 days.
No. We build with Flutter, which produces an iOS app and an Android app from a single codebase, with native performance. You save the double build and the double maintenance budget.
If your use case requires it, yes. We design architectures with local storage and deferred sync when the network comes back. Essential for field apps, but a word of caution: offline often drives the price up, so we scope it from the start.
We do. Developer account creation if needed, store listings, screenshots, submission, Apple review follow-up, publication. The developer accounts are in your name: you keep ownership of your presence on the stores.
Yes. Most of the apps we build are connected to an existing back office or API, with real-time sync and access management from the smartphone.
The entire business layer built for your app is fully yours. It sits on FastEdgy, our open source foundation. You can take the code back, hand it to another provider, or build an internal team.
Let’s build a product people → actually use
A 30-minute call with a founder. Answer within 24/48h. Pitch deck optional.