How do their APIs compare?

Comparing the two libraries' public APIs based on what's in the repository data:

greenrobot/eventbus — Publish/Subscribe API

EventBus's API is built around a small, declarative surface:

• Event classes: Plain POJOs with no required base class or interface — e.g. public static class MessageEvent { } as shown in the README excerpt.
• Subscriber registration: EventBus.getDefault().register(this) / unregister(this), typically tied to Android lifecycle callbacks (onStart/onStop).
• Subscribing methods: Declared via the @Subscribe annotation with a threadMode parameter (e.g. ThreadMode.MAIN), rather than a naming convention or manual listener interface. This is metadata-driven — the library reflects on annotated methods, or uses a precompiled index.
• Posting: A single post(Object event) call, with support for sticky events (cached most-recent event delivery) per the comparison table in [COMPARISON.md:L1-40].
• Supporting types for annotation-processed indexes: SubscriberMethod [EventBus/src/org/greenrobot/eventbus/SubscriberMethod.java:L1-20], SubscriberInfo [EventBus/src/org/greenrobot/eventbus/meta/SubscriberInfo.java:L1-20], and SubscriberInfoIndex [EventBus/src/org/greenrobot/eventbus/meta/SubscriberInfoIndex.java:L1-20] — these back the recommended annotation-processor/subscriber-index feature mentioned in the README, letting method lookup avoid runtime reflection.

So EventBus's API surface is intentionally minimal: register/unregister/post, annotate methods, done. It explicitly favors simplicity — per [COMPARISON.md], it also supports event inheritance and subscriber inheritance, unlike Otto.

hongyangandroid/okhttputils — Fluent HTTP builder API

OkHttpUtils exposes a fluent, chainable builder API wrapping OkHttp:

• Request construction: Static entry points like OkHttpUtils.get(), chained with .url(...), .addParams(key, value), .build(), and finally .execute(callback), as shown in [README.md:L139-164]. Other verbs (put(), delete(), head(), patch()) follow the same chain pattern, as sketched in the commented-out sample in [sample-okhttp/src/main/java/com/zhy/sample_okhttp/MainActivity.java:L312-351].
• Callbacks: Instead of annotated methods, consumers implement callback classes (StringCallback, or file-download callbacks with onBefore, inProgress, onError, onResponse methods as seen in the same MainActivity excerpt).
• HTTPS/TLS configuration API: HttpsUtils.getSslSocketFactory(...) [okhttputils/src/main/java/com/zhy/http/okhttp/https/HttpsUtils.java:L35-63] returns an SSLParams object bundling an SSLSocketFactory and X509TrustManager, letting callers configure custom certificates/trust managers directly rather than through OkHttp's lower-level builder.
• Logging: LoggerInterceptor provides an OkHttp Interceptor-based logging facility, with internal helpers like bodyToString [okhttputils/src/main/java/com/zhy/http/okhttp/log/LoggerInterceptor.java:L152-163].
• Platform abstraction: Platform [okhttputils/src/main/java/com/zhy/http/okhttp/utils/Platform.java:L1-24] wraps Android's Handler/Looper to dispatch callbacks onto the main thread — conceptually similar to EventBus's ThreadMode.MAIN, but implemented as an internal utility rather than exposed as an annotation option.

Key contrasts