How do their APIs compare?

I can only meaningfully compare APIs between google/exoplayer and nanohttpd/nanohttpd by examining what you've shared, though they serve very different purposes—one is a media player library, the other is an HTTP server framework.

High-Level Differences

google/exoplayer (deprecated, now androidx/media):

• JNI-heavy: Uses native code for codec integration (AV1, FLAC decoders)
• Java extensions: Cast support, media handling via classes like DefaultMediaItemConverter
• Callback-driven: C++ layers use callback patterns for streaming (e.g., FLAC parser callbacks in [extensions/flac/src/main/jni/flac_parser.cc:L36-L75])

nanohttpd/nanohttpd:

• Pure Java HTTP stack: Router-based request handling with enumerated HTTP methods
• Method-centric: Uses Method enum [core/src/main/java/org/nanohttpd/protocols/http/request/Method.java:L40-L72] (GET, POST, PUT, DELETE, HEAD, etc.)
• Parameter decoding: Built-in query parameter parsing with decodeParameters() [core/src/main/java/org/nanohttpd/protocols/http/NanoHTTPD.java:L405-L444]

Concrete API Contrasts

Aspect	ExoPlayer	NanoHTTPD
Language blend	Java + C++ (JNI)	Pure Java
Request handling	Video frame callbacks, output buffers	HTTP method routing + URL parameters
Extensibility	Decoder plugins, cast converters	Custom responders, URL routing
Configuration	DecoderSettings, VideoDecoderOutputBuffer	Method enum, tempFileManager

The repositories don't overlap functionally—ExoPlayer decodes and plays media; NanoHTTPD serves HTTP requests.

FOLLOW_UPS:

• How does ExoPlayer handle DRM configuration in Cast?
• What HTTP methods does NanoHTTPD's router support?
• How does the FLAC decoder invoke C++ callbacks?