How do their APIs compare?

I can only provide a meaningful API comparison if you specify which components from these two repositories you'd like to compare. They serve very different purposes:

google/exoplayer is a media playback library for Android, with APIs for:

• Media playback control
• Ad insertion (e.g., ImaServerSideAdInsertionUriBuilder [extensions/ima/src/main/java/com/google/android/exoplayer2/ext/ima/ImaServerSideAdInsertionUriBuilder.java:L126-L165])
• Network providers (e.g., Cronet integration in CronetUtil [extensions/cronet/src/main/java/com/google/android/exoplayer2/ext/cronet/CronetUtil.java:L121-L160])
• Media session callbacks

nanohttpd/nanohttpd is a lightweight HTTP server library with APIs for:

• HTTP request/response handling (GET, HEAD, POST, PUT, DELETE, OPTIONS)
• Query parameter decoding [core/src/test/java/org/nanohttpd/junit/protocols/http/HttpGetRequestTest.java:L88-L127]
• CORS header management [webserver/src/main/java/org/nanohttpd/webserver/SimpleWebServer.java:L582-L607]

These are fundamentally different—one is for Android media playback, the other is a web server. Could you clarify what specific APIs or use cases you'd like to compare?

FOLLOW_UPS:

• What components specifically interest you?
• Are you looking for architectural patterns across both?
• Do you want examples of method chaining patterns used?