Technologies / Dart
Dart app development: the language behind your Flutter app
Dart app development is, in practice, mostly Flutter development. Dart is the language every Flutter screen, state class and API client is written in, so the quality of your Dart code decides how easy your app is to change in year three. This page is for CTOs and product owners who want to understand the language decision underneath Flutter, and where Dart is useful outside it.
If you are choosing a team to build the app itself, start with our Flutter app development company page. Dart is one of the languages in our mobile app development technologies overview.
- Dart 3 with sound null safety
- Strict analyzer rules in CI
- Shared Dart packages across apps
- Code in your own repository
What Dart is, and why Flutter uses it
Dart is a typed, object-oriented language from Google. It compiles ahead of time to native machine code for release builds, which is why Flutter apps start quickly and run without a JavaScript bridge. During development it runs in a just-in-time mode that powers Flutter’s hot reload, so a developer sees a UI change in about the time it takes to save the file.
For a buyer, three things matter. Dart is easy for Java, Kotlin, Swift, C# and TypeScript developers to pick up, so hiring is not limited to people with years of Dart. It has one official package registry, pub.dev, and one official formatter and analyzer, so codebases from different teams look alike. And it is controlled by the same company that ships Flutter, which keeps the language and the framework moving together.
Sound null safety in Dart 3: what it changes for your app
Google announced Dart 3 on 10 May 2023 as “a 100% sound null safe language”, and Dart has enforced sound null safety ever since. In plain terms, a variable cannot hold null unless its type says it can, and the compiler checks every path. A whole class of crash, the “null check operator used on a null value” kind, moves from production to the developer’s screen.
“Sound” is the important word. In some languages null checks are hints that can be bypassed. In Dart 3 they are guaranteed, which also lets the compiler produce smaller, faster code because it can trust the types.
If your app is older than Dart 3
Flutter apps started before 2023 may still carry pre-null-safety code or packages, and current Flutter and Dart releases will not build it. Upgrading usually means migrating the app’s own code, replacing abandoned packages and fixing the places where a forced null check (the ! operator) was used to silence the compiler rather than handle a real empty value. We treat those forced checks as a review checklist, because each one is a possible crash. This work often sits inside our legacy app modernization engagements.
Dart 3 also added records, pattern matching and sealed classes. They matter less than null safety, but they make state handling clearer: a sealed result type forces every screen to handle loading, success and error, and the compiler complains if one is missing.
When we choose Dart app development, and when we do not
We choose Dart when we choose Flutter: one codebase for iOS and Android, a custom-designed UI that should look identical on both, and a team that wants to move quickly. Our Flutter vs React Native comparison covers that framework decision in detail, and Kotlin Multiplatform vs Flutter covers the newer alternative.
We do not pick Dart for its own sake. If your web team writes TypeScript and you want to share code and people with a React app, React Native usually fits better. If the app depends heavily on platform features such as widgets, watch apps or deep Bluetooth work, native Swift and Kotlin carry less risk. And for a backend that other teams will maintain, Dart is rarely the right default.
Dart fits when
- You are building with Flutter
- iOS and Android launch together on one budget
- The UI is custom and brand-led
- You want shared business logic across several Flutter apps
- Your team is comfortable with typed, object-oriented code
Dart beyond Flutter: where else we use it
Dart is mostly a client language, but a few uses outside the UI layer save real time.
Shared packages across apps
A customer app and a driver or staff app often share models, API clients and validation rules. We put that code in private Dart packages so a pricing rule changes once, not twice.
Command-line and build tools
Small Dart scripts generate code from API schemas, check translation files, bump version numbers and prepare store metadata in CI. The same developers can maintain them, with no extra language.
Lightweight server code
Dart can run on a server, with packages such as Shelf for HTTP. We use it for small internal services or prototypes where sharing models with the app is the main win. For core backends we prefer Node.js or Laravel, which have larger ecosystems.
Web and desktop builds
Dart compiles to JavaScript for the web, which Flutter web relies on. That suits internal tools and companion dashboards more than SEO-driven public websites.
Worried about the state of your Dart code?
Share read access to the repository. Within one business day we reply with a short note on null-safety status, outdated packages and the riskiest parts of the code.
Dart compared with the other mobile languages
How Dart sits next to the languages we use for the same kind of app.
| Dart (Flutter) | TypeScript (React Native) | Swift / Kotlin (native) | |
|---|---|---|---|
| Platforms from one codebase | iOS, Android, web, desktop | iOS, Android; web via React | One platform each; KMP shares Kotlin logic |
| Null safety | Sound, enforced since Dart 3 | Checked in strict mode; can be bypassed | Built into both languages |
| Hiring pool | Smaller, but quick to train into | Large, shared with web teams | Platform specialists |
| Platform API access | Plugins or platform channels | Native modules | Direct |
| Backend use | Possible, small ecosystem | Strong with Node.js | Kotlin strong on the server; Swift niche |
Hiring and maintaining a Dart codebase
Fewer developers list Dart as their main language than JavaScript or Java, but the learning curve is short for anyone who knows a typed language. What takes longer to learn is Flutter’s architecture: state management, widget rebuilds and platform channels. When you hire Flutter developers, test those, not Dart syntax. Our guide on how to hire Flutter developers includes interview questions.
Maintenance follows Flutter’s release rhythm. Plan for regular Flutter and Dart upgrades, package updates and the yearly Google Play target API change. Teams that skip upgrades for a year or two usually face a painful jump, because several packages and the framework move at once. Our app maintenance services keep that cadence small and predictable.
Code-quality practices on our Dart projects
What you can check in your own repository.
- Strict analysis_options.yaml with lints enforced in CI; zero analyzer warnings on main
- dart format applied automatically, so reviews focus on logic
- Every ! operator justified in review or replaced with real null handling
- Sealed classes for screen state, so loading, empty and error cases are always handled
- Unit tests for business logic and widget tests for critical screens
- Generated code (JSON models, routes) produced in CI, not edited by hand
- Packages pinned, reviewed for maintenance status and upgraded on a schedule
Dart app development: frequently asked questions
Is Dart only used for Flutter?
Mostly, but not only. Dart can run command-line tools, build scripts and small server applications, and it compiles to JavaScript for the web. In practice almost all commercial Dart code sits inside Flutter apps. We use Dart outside Flutter for shared packages and build tooling, and pick other languages for core backends that other teams will maintain.
What does sound null safety mean in Dart?
It means a variable can only hold null if its type explicitly allows it, and the compiler guarantees this across the whole program. Dart 3, announced in May 2023, made sound null safety mandatory. The practical result is fewer null-related crashes in production, because the compiler catches missing values before the app ships.
Our Flutter app predates Dart 3. Does it need work?
Very likely. Code and packages without null safety will not build on current Dart and Flutter releases, so you cannot ship updates until they are migrated. The work usually covers migrating your own code, replacing abandoned packages and reviewing forced null checks. We audit first and give a written plan with a typical effort estimate in hours.
Is Dart hard to hire for?
Less than it looks. Fewer developers list Dart as their main language, but anyone who knows Kotlin, Swift, Java, C# or TypeScript reads it quickly. The harder skill is Flutter architecture, such as state management and platform channels, so interviews should focus there. You can also hire Flutter developers from us with a two-week trial.
Can we use Dart for our backend?
You can, and sharing models with the app is a real benefit. But Dart’s server ecosystem is small compared with Node.js, Python, Java or PHP, and fewer backend developers know it. We use Dart on the server for small services and prototypes, and recommend a mainstream backend for anything your wider team must run long term.
Should we choose Flutter and Dart or React Native and TypeScript?
Choose Flutter if you want one custom-designed UI that looks the same on iOS and Android and your team has no strong web stack. Choose React Native if you already have React and TypeScript developers and want to share code or people with a web app. Both are production-ready; the better fit depends on your team and roadmap.
Build your Flutter app on clean, current Dart
Book a 30-minute scoping call. We will look at your plans or your existing code and tell you where Dart and Flutter fit, what an upgrade would involve and what to watch in maintenance.