---
title: "Hilt | Skills We Assign For | Azendo"
description: "Hilt for Android dependency injection — compile-time wiring, lifecycle scopes, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/hilt/"
---

[Skills](https://azendo.co/skills/) Mobile platforms and frameworks 

# Hilt.

Hilt is Android's dependency injection framework, built on Dagger with Android-specific conventions. It generates the injection code at compile time and provides predefined scopes tied to application, activity and fragment lifecycles.

## Where Hilt fits on a long engagement.

Hilt exists because Dagger was correct and unapproachable. The compile-time guarantee is the same — a missing binding fails the build rather than crashing at runtime — but the Android-specific scopes and annotations remove most of the setup that made Dagger a specialist skill rather than a team one.

Scope selection is where teams get into trouble. A dependency scoped to the application that should have been scoped to an activity holds a reference past the point it should have been released, which is a memory leak that no test will catch and that only shows up as degradation over a long session.

## What an assigned team does with Hilt.

Injection setup is the kind of infrastructure that is configured once and then inherited by everyone who follows. A scope chosen carelessly in month one is repeated by every subsequent contributor because it is the existing pattern.

Getting those foundations reviewed properly at the start is part of what a standing assignment is for, and how it is agreed is set out in [how the monthly fee is built](https://azendo.co/pricing/).

## What we use Hilt for.

* Wiring checked by the compiler A missing dependency failing the build instead of crashing on a screen in production.
* Test doubles without a parallel graph Dependencies replaced in instrumentation tests through the same mechanism the app uses.
* Scopes matched to lifecycle Objects released when the thing that needed them goes away, rather than held for the process lifetime.

## How Hilt capacity is assigned.

Hilt work sits inside Android capacity under [software development outsourcing](https://azendo.co/services/software-development/).

## Roles we assign Hilt for

* [Android Developer Mobile development](https://azendo.co/services/mobile-development/android-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 mobile platforms and frameworks

* [SwiftUI — skill we assign for](https://azendo.co/skills/swiftui/)
* [UIKit — skill we assign for](https://azendo.co/skills/uikit/)
* [Jetpack Compose — skill we assign for](https://azendo.co/skills/jetpack-compose/)
* [Coroutines — skill we assign for](https://azendo.co/skills/coroutines/)
* [Flutter — skill we assign for](https://azendo.co/skills/flutter/)
* [React Native — skill we assign for](https://azendo.co/skills/react-native/)
* [Expo — skill we assign for](https://azendo.co/skills/expo/)
* [Ionic — skill we assign for](https://azendo.co/skills/ionic/)

## Tell us what your roadmap needs Hilt 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/)