Add guidance on using proprietary components
PiperOrigin-RevId: 357201112
Change-Id: Ic3085e8f25e57ff7c53fa0cb8dd976bf88da0653
diff --git a/docs/principles.md b/docs/principles.md
index 6dba721..c498b10 100644
--- a/docs/principles.md
+++ b/docs/principles.md
@@ -53,11 +53,13 @@
### 5. Developed as open-source and compatible with AOSP Android
- Expose a unified developer-facing API surface across the Android ecosystem
-- Avoid proprietary services or closed-source libraries for core
- functionality, and instead provide integration points that allow a developer
- to choose a proprietary service as the backing implementation
- Develop in AOSP to provide visibility into new features and bug fixes and
encourage external participation
+- Avoid proprietary services or closed-source libraries for core
+ functionality, and instead provide integration points that allow a developer
+ to choose between a variety of services as the backing implementation
+- See [Integrating proprietary components] for guidance on using closed-source
+ and proprietary libraries and services
### 6. Written using language-idiomatic APIs
