CONSENT CONSOLE/MK-V
DEFAULT

Telemetry consent. Operator-grade.

We capture only the signals we need to keep the site running, understand which content earns reads, and credit referral partners. You decide what stays on. Default is strict opt-in.

Privacy Policy →Terms →
JURISDICTIONOutside regulated jurisdictionsFRAMEWORKNo regional opt-in framework applied

COMPLIANCE FRAMEWORKS RECOGNIZED

GDPREU / EEA
CCPACalifornia
LGPDBrazil
PIPEDACanada
ePrivacyEU Directive
Strategia-X
L
-6dB
C
-1dB
R
-3dB
Technology Trends

The Library Under Your App Went Into Maintenance Mode

Strategia-X EditorialOct 11, 20262 min read345 words
Technology TrendsOP-5900

The Library Under Your App Went Into Maintenance Mode

PUB·2 MIN·345 WORDS

Platform vendors rarely announce the end of a library. They add one sentence to a release page and move their engineers elsewhere. If nobody on your team reads release pages, you find out years later, when the feature you need exists only in the successor.

The Sentence

The release page for Android's Navigation library, the one that moves users between screens in most apps, now opens with this: "This library is in maintenance mode and will only receive critical fixes; new features are not planned." (Android).

That is not a deprecation. The library is supported and current apps keep working. It is a statement about investment, and it should change where new investment goes.

The Successor Works Differently

The replacement, Navigation 3, has been stable since November 2025. It is not an upgrade of the old model. Google describes it this way: "With Navigation 3, you have full control over your back stack, and you navigate between destinations by adding and removing items from a list." (Android). The app owns the navigation state. The library draws it.

Because the model differs, moving is a project. Google's migration guide assumes it happens "in a single, atomic change" (Android), which means it needs a slot on a roadmap and cannot be done on the side.

A Number We Removed

Our article on this topic used to cite a study of 1,200 apps and a crash percentage. We could not find the study. The figure is gone. The engineering argument stood without it, which is usually the sign that a statistic was decoration.

What to Ask Your Team

  • Which of our core libraries are in maintenance mode? Someone should know without looking it up.
  • Are new features being built on the old model? Each one adds to the eventual migration.
  • Is the migration on the roadmap with an owner?
  • Which statistics in our own planning documents have a source?

-Rocky

#TechnologyStrategy #Android #PlatformRisk #EngineeringDreams #StrategiaX

Originally published on ANDROID-ARCHITECT, the Android engineering blog of Strategia-X, with the code for both libraries.

technology strategy Android platform risk software architecture technical debt roadmap planning

/Rocky