The DIST model lets us tackle a project in a structured and organized way, but with room for spontaneity.
Itamar Galad, ex-senior product owner at Microsoft & Google, whipped up the DIST model.
How does it work?
Think of it as a GPS system: we set the destination and budget, but the journey? That’s an adventure packed with real-time updates. The goals stay put, that’s a given. But the ideas, steps, and tasks we undertake along the way? They’re always in flux. We’re always adjusting, recalibrating, and optimizing. That’s how we roll!
What (business) goal or goals do we aim to achieve with the app?
Ideas are the bets we place to reach the goal or goals.
Small or big projects we need to carry out to fulfill an idea.
All tasks needed to complete a step (project).
We validate and optimize EVERY idea with our certainty score. Only the true game-changers get our focus. Period.
How does it work?
We first determine the current certainty score for each idea using the info we already have. Then, we can do additional research to boost the certainty of success.
A no-brainer way to validate quickly and substantively!
We only build native apps. No faux-native apps, but the real deal. Without the double costs usually slapped on you.
So, no hybrid, cross-platform, or no/low code apps like ReactNative, Xamarin, Flutter, Ionic, NativeScript, or OutSystems.
True native apps are built solely in Apple’s 🍏 and Android’s 🤖 own development environment. That means lifelong and guaranteed support, a promise you won’t get with the above alternatives.
So, while others are trying to reinvent the wheel, we stick to the basics. It works. It’s proven. And guess what? It’s sustainable.
We make native apps in the birthplace of operating systems: Xcode for iOS and Android Studio for Android. No shortcuts, no half measures.
But here’s our power move: Shared Architecture. An app isn’t a simple one-layer pancake, it’s a multi-layered cake. And those layers can be baked in different kitchens. Our secret recipe?
We share as many layers (the app architecture) in common development environments as possible. We only code the strictly necessary (the top layer) within the OS-specific kitchens.
A chunk of our code can be shared across multiple platforms. This prevents a lot of double work. Simple, efficient, and wickedly effective.
Simultaneous feature development
Developer A (Android) and Developer B (iOS) work on different things at the same time – Feature A and Feature B.
So, if Feature A needs tweaks after customer feedback, we do it once. Developer B only starts on Feature A after it’s approved, then he can implement it in the same way.
Listen up, we’re not in the business of creating 3 or 4-star apps. No, we’re shooting for the full five stars! If we don’t make it? We’ll refund you half. Yes, you heard it right. Why? Because we have total faith in the quality of our team.
We’ve got a system. It’s tight, it’s well-founded, and it’s unbelievably organized. We set our own quality benchmarks, and we ensure stringent checks. We deliver top-notch quality, time and time again.
Each of our teams has a QA specialist. This superhero ensures we stay on track, that we meet our quality targets. They’re keeping their fingers on the pulse, making sure we don’t stray off the path to perfection.
We operate with a system that makes every minute count. Everyone clocks in and out, so we know exactly how much time has been spent on each feature. This way, we can adjust in time to meet our objectives.
We show you exactly how much time we spend on each task. No guesswork, no misunderstandings about costs.
It’s in our DNA. We can precisely see which tasks are time-consuming, or which ones are quicker than anticipated. This helps us to switch gears faster and make smart decisions in every sprint. That’s how we operate here. That’s how we come out on top.