How do their APIs compare?

I don't have enough retrieved evidence here to do a rigorous side-by-side "API comparison," since these two projects are fundamentally different kinds of libraries. Let me lay out what I can say from what's in front of me and flag where I'd need to search for more.

Nature of the two "APIs"

scwang90/smartrefreshlayout is an Android UI widget library. Its "API" is a set of Java classes/interfaces you use in an Android app's layout XML and Activity/Fragment code:

• A custom ViewGroup, SmartRefreshLayout, placed in layout XML wrapping a scrollable child (RecyclerView, ListView, WebView, etc.) plus optional Header/Footer views like ClassicsHeader/ClassicsFooter [README_EN.md:L141-L157].
• Programmatic API on a RefreshLayout interface: setRefreshHeader(...), setRefreshFooter(...), setOnRefreshListener(...), setOnLoadMoreListener(...), and completion callbacks like finishRefresh(...)/finishLoadMore(...) [README_EN.md:L159-L181].
• It's distributed as multiple Maven artifacts (kernel + separate header/footer modules) that you assemble via Gradle dependencies [README_EN.md:L120-L128].
• There's also a drawable-parsing utility API, e.g. PathParser for parsing vector path data, adapted from AOSP [refresh-drawable-path/.../PathParser.java:L1-L28].

springfox/springfox is a Java/Spring library for generating OpenAPI/Swagger documentation from Spring MVC/WebFlux applications. Its "API" is almost entirely annotation- and configuration-driven, not something you call imperatively at runtime the way you call SmartRefreshLayout's listener methods:

• You add a starter dependency (springfox-boot-starter) and enable it via annotations like @EnableOpenApi (or @EnableSwagger2WebMvc/@EnableSwagger2WebFlux for older versions) [README.md:L35-L75].
• You annotate REST controllers with Swagger annotations (@ApiOperation, @ApiParam, @ApiResponses, etc.) to describe endpoints, as shown in the pet store sample controller [springfox-petstore/.../PetStoreResource.java:L45-L107].
• For Spring Integration flows, there's a separate "documenting" API built on spring-restdocs conventions, where you tag an integration endpoint with .id(...) and correlate it to a document("...") call in a MockMvc/WebTestClient test [springfox-spring-integration-webmvc/README.md:L73-L112], [springfox-spring-integration-webflux/README.md:L72-L111].
• There's also a browser-facing JS API in springfox-swagger-ui/src/web/js/springfox.js that fetches configuration and resource metadata (/swagger-resources/...) to build the Swagger UI at runtime [springfox-swagger-ui/src/web/js/springfox.js:L5-L54].

Key contrasts

I haven't retrieved springfox's core Docket/plugin configuration API or its @Api-related annotation definitions, nor smartrefreshlayout's full RefreshLayout/RefreshHeader/RefreshFooter interface definitions — if you want a deeper comparison of the actual public interfaces/classes (not just usage snippets), I can search for those.