Hilt.

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.

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.