---
title: "Dart | Skills We Assign For | Azendo"
description: "Dart as the language behind Flutter — null safety, the two compilation modes, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/dart/"
---

[Skills](https://azendo.co/skills/) Languages and runtimes 

# Dart.

Dart is the language Flutter is written in: statically typed with sound null safety, compiled ahead of time to native code for release builds and just in time during development, which is what makes hot reload possible.

## Where Dart fits on a long engagement.

Dart is deliberately unremarkable, and that is a feature. Anyone comfortable in Java, C# or TypeScript reads it immediately, which keeps the cost of adopting Flutter concentrated in the framework rather than split between framework and language.

The detail worth knowing is the two compilation modes. Development uses a JIT, which is what gives sub-second hot reload; release builds compile ahead of time to native code. Performance differences between the two are normal and routinely mistaken for regressions when someone profiles a debug build.

## What an assigned team does with Dart.

Sound null safety means the guarantee holds at runtime rather than being advisory, but only across a fully migrated codebase. A package that has not migrated weakens the guarantee for everything depending on it, which makes dependency hygiene part of the language story rather than separate from it.

Keeping dependencies current is continuous work that no single ticket ever justifies, which is what a standing assignment is for. What that commitment covers is set out in [how the monthly fee is built](https://azendo.co/pricing/).

## What we use Dart for.

* Shared logic across app and tooling The same language for the application and the scripts around it, so utilities are not a second ecosystem.
* Null safety enforced across the tree Dependencies kept migrated, so the runtime guarantee is real rather than partial.
* Profiling against release builds Performance measured where users experience it, not in a JIT-compiled debug build.

## How Dart capacity is assigned.

Dart capacity is assigned as part of Flutter work inside mobile development rather than as a standalone language specialism.

## Roles we assign Dart for

* [Flutter Developer Mobile development](https://azendo.co/services/mobile-development/flutter-developer/)

## Service lines it sits in

* [Mobile development](https://azendo.co/services/mobile-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in languages and runtimes

* [Python — skill we assign for](https://azendo.co/skills/python/)
* [Java — skill we assign for](https://azendo.co/skills/java/)
* [TypeScript — skill we assign for](https://azendo.co/skills/typescript/)
* [Node.js — skill we assign for](https://azendo.co/skills/nodejs/)
* [React — skill we assign for](https://azendo.co/skills/react/)
* [Next.js — skill we assign for](https://azendo.co/skills/nextjs/)
* [R — skill we assign for](https://azendo.co/skills/r/)
* [.NET — skill we assign for](https://azendo.co/skills/dotnet/)

## Tell us what your roadmap needs Dart for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)