How do their APIs compare?

I can address this, but it's worth flagging that these two repositories are very different in scope, so an "API comparison" mostly highlights that contrast rather than a like-for-like feature comparison.

hugeterry/coordinatortablayout — a UI widget API

This is a single Android custom view (Java), and its "API" is a small, fluent builder-style set of public methods on the CoordinatorTabLayout class, meant to be called from an Activity/Fragment after inflating the view:

• setTitle(String title) — sets the collapsing toolbar's title
• setImageArray(int[] imageArray) — supplies header background images per tab
• setImageArray(int[] imageArray, int[] colorArray) — same, plus a content scrim color per tab
• setupWithViewPager(ViewPager viewPager) — wires the TabLayout to a ViewPager
• Accessors to reach nested views: getActionBar(), getTabLayout(), getImageView()

These are chainable, e.g.:

mCoordinatorTabLayout.setTitle("Demo")
        .setImageArray(mImageArray)
        .setupWithViewPager(mViewPager);

as shown in [README.md:L44-L63] and mirrored in [README_CN.md:L26-L44] for XML setup, with getters documented in [README_CN.md:L181-L189]. There's no network/service API here — it's purely a client-side view composition API, and the retrieved source shows only placeholder unit test stubs [coordinatortablayout/src/test/java/cn/hugeterry/coordinatortablayout/ExampleUnitTest.java:L1-L11], not substantive API implementation code.

Per the RepoPilot verdict, this project is flagged AVOID — looks unmaintained, solo project with stale commits, so its API surface should be considered frozen/unlikely to evolve.

yunaiv/ruoyi-vue-pro — a full backend platform's APIs

This is a large Spring Boot multi-module enterprise system, and "API" here means RESTful backend endpoints, RPC interfaces, and infrastructure integration points, not UI widget methods:

• RESTful APIs auto-documented via Swagger, described in the "系统接口" feature row in [README.md:L201-L219]
• An internal RPC convention, e.g. a constant defining the RPC path prefix: RPC_API_PREFIX = "/rpc-api" in [yudao-framework/yudao-common/src/main/java/cn/iocoder/yudao/framework/common/enums/RpcConstants.java:L10-L18]
• API access/error logging is itself modeled as persisted data (e.g. infra_api_access_log table capturing request method, URL, params, response body, IP, duration, result code) as seen in [sql/postgresql/ruoyi-vue-pro.sql:L71-L110]
• Broader integration "APIs" span WebSocket, third-party OAuth logins (WeChat, DingTalk), payment gateways, cloud storage (MinIO/Aliyun/Tencent/Qiniu), and SMS providers, per the feature table in [README.md:L36-L61]

Summary of the comparison

Aspect	coordinatortablayout	ruoyi-vue-pro
API type	Android view/widget methods	RESTful + RPC backend endpoints
Consumer	App developers embedding the view	Frontend apps / other services
Scope	~5 public methods, single class	Multi-module platform-wide APIs
Maintenance signal	RepoPilot: AVOID, unmaintained	No RepoPilot verdict shown in data; actively documented with multiple branches/versions [README.md:L24-L35]

They aren't really comparable in kind — one is a narrow, static UI component API frozen in an unmaintained repo, the other is a sprawling, evolving backend platform's set of service APIs.

FOLLOW_UPS:

• What does RepoPilot say about ruoyi-vue-pro's maintenance status?
• How is RPC_API_PREFIX used elsewhere in ruoyi-vue-pro?
• What UI behaviors does CoordinatorTabLayout implement internally?