Re: Integrating MLKit library into chromium android caused APK Size increase

[Reilly Grant]

Note that this increase only applies to the open-source Chromium build. Chrome is unaffected.

Reilly Grant | Software Engineer | rei...@chromium.org | Google Chrome

On Fri, Feb 13, 2026 at 6:50 PM Fei Chen <fe...@microsoft.com> wrote:

Hi team,

This is Fei from Microsoft Edge team. Recently I'm working on enabling on-device web APIs (e.g., Summarizer)  on Android based on google MLKit library. MLKit provides the developer-facing public APIs that talks to AICore which is the system-level AI runtime that actually runs and updates on-device models. I think both Microsoft and Google have got the alignment that open-source Chromium can use MLKit integrating with AICore to benefit from on-device AI capabilities. We have made some progress including adding the library and auto-rolled it, adding and refactoring some interfaces, and now we are approaching the step that really adds MKLit dependency to chromium android in this CL:

7557052: Implement Android on-device AI backend interfaces - Part 1 | https://chromium-review.googlesource.com/c/chromium/src/+/7557052.

Here we encountered the issue - Dry-Run CI reported android-binary-size failure that MKLit library deps caused 349.9KB binary size increase. Can you suggest whether the binary size increase is acceptable or are there any actions we can take to optimize the size.

Thanks,

Fei

[Andrew Grieve]

Triggered android-internal-binary-size, and it confirms not size change, so binary size isn't a concern here.