KeyedService and KeyedServiceFactory together support building a dependency tree of services that are all keyed off the same object (typically, content::BrowserContext or web::BrowserState), and whose teardown order is managed according to the expressed dependency order.

KeyedService is a layered component to enable it to be shared cleanly on iOS.

This component has the following structure:

• core/: shared code that does not depend on src/content/ or src/ios/
• content/: Code based on the content layer.
• ios/: Code based on src/ios.

On Android, C++ keyed services often have a corresponding Java object. In such cases, the C++ part should own the Java one. You can find more details in docs/android_jni_ownership_best_practices.md.