How do their APIs compare?

These two projects are fundamentally different in kind, so "API comparison" means different things for each — one is a UI widget library with a fluent builder-style Java API, the other is a large backend microservices framework with RPC/REST interfaces. Let me lay out what's actually visible in the retrieved data.

hugeterry/coordinatortablayout: a single custom-view API

This is an Android UI library exposing one main class, CoordinatorTabLayout, configured via chained setter calls rather than a service API. From the README and sample usage:

• setTitle(String title) — sets the header title [README.md:L25-L43]
• setupWithViewPager(ViewPager viewPager) — links the ViewPager to the tab layout
• setImageArray(int[] imageArray) — sets header background images per tab
• setImageArray(int[] imageArray, int[] colorArray) — same, plus a content-scrim color per tab
• setTranslucentStatusBar(this), setBackEnable(true), setLoadHeaderImagesListener(...) — additional chained configuration, as seen in the sample activity [sample/src/main/java/cn/hugeterry/coordinatortablayoutdemo/LoadHeaderImageFromNetworkActivity.java:L24-L51]

The whole "API" is this builder chain returning this, e.g.:

mCoordinatorTabLayout.setTranslucentStatusBar(this)
        .setTitle("Demo")
        .setBackEnable(true)
        .setContentScrimColorArray(mColorArray)
        .setLoadHeaderImagesListener(...)
        .setupWithViewPager(mViewPager);

[sample/src/main/java/cn/hugeterry/coordinatortablayoutdemo/LoadHeaderImageFromNetworkActivity.java:L45-L51]

There's also a small utility, SystemView.getStatusBarHeight(Context), used internally for layout math [coordinatortablayout/src/main/java/cn/hugeterry/coordinatortablayout/utils/SystemView.java:L9-L19]. There is no network, RPC, or data-access API — it's purely a presentation-layer widget.

yunaiv/yudao-cloud: RPC/service interfaces and structured response envelopes

yudao-cloud exposes many backend APIs across modules. From what's retrieved, two representative patterns:

1. A common HTTP response wrapper, CommonResult<T>, used across all service responses — with static factories like success(T data), error(ErrorCode, Object...), and instance methods isSuccess(), checkError() that throw a ServiceException on failure [yudao-framework/yudao-common/src/main/java/cn/iocoder/yudao/framework/common/pojo/CommonResult.java:L20-L122]. This is the standard envelope nearly every controller/RPC method returns.

2. RPC-style inter-service APIs defined as Spring interfaces with annotations, e.g. ApiErrorLogCommonApi:

@PostMapping(PREFIX + "/create")
CommonResult<Boolean> createApiErrorLog(@Valid @RequestBody ApiErrorLogCreateReqDTO createDTO);

plus a default async wrapper createApiErrorLogAsync(...) that calls checkError() on the result [yudao-framework/yudao-common/src/main/java/cn/iocoder/yudao/framework/common/biz/infra/logger/ApiErrorLogCommonApi.java:L17-L36]. Request DTOs like ApiErrorLogCreateReqDTO use @NotNull/Swagger annotations for validation and documentation [yudao-framework/yudao-common/src/main/java/cn/iocoder/yudao/framework/common/biz/infra/logger/dto/ApiErrorLogCreateReqDTO.java:L1-L10].

Comparison

Aspect	coordinatortablayout	yudao-cloud
API style	Fluent/builder chained setters on a View	Annotated REST/RPC interfaces (@PostMapping)
Return convention	this (for chaining)	CommonResult<T> envelope with code/msg/data
Error handling	None visible (no exceptions surfaced)	ServiceException