How do their APIs compare?

These two repositories aren't really comparable in terms of "APIs" in the same sense, because they serve fundamentally different purposes:

crossoverjie/jcsprout

This is a Java learning/reference repository — a collection of standalone code examples and mini-implementations demonstrating core Java concepts. It doesn't expose a cohesive public API for consumption as a library. Instead it contains independent classes like:

• LRUAbstractMap — a hand-rolled LRU cache implementation with put/get, size limits, eviction callbacks (lruCallback), and timeout-based eviction (timeoutCallback) [src/main/java/com/crossoverjie/actual/LRUAbstractMap.java:L1-L26]
• Search — a word search/trie-like utility exposing static methods addWord(...) and search(String keyWord) with wildcard matching support (. as any-char) [src/main/java/com/crossoverjie/actual/Search.java:L101-L158]
• BloomFilters — exposes add(String) and check(String) methods plus several hash variants (hashcode_2, hashcode_3) [src/main/java/com/crossoverjie/algorithm/BloomFilters.java:L130-L156]
• ThreadCommunication — demonstrates thread communication using piped I/O and concurrency utilities [src/main/java/com/crossoverjie/actual/ThreadCommunication.java:L1-L17]

Each file is essentially a self-contained demo with a main method, not a designed public-facing API — it's meant to be read as educational material rather than integrated as a dependency.

hugeterry/coordinatortablayout

This is an Android UI library with an actual consumable API: a custom CoordinatorTabLayout view meant to be dropped into an XML layout alongside a ViewPager, wired via app:layout_behavior="@string/appbar_scrolling_view_behavior" [README.md:L25-L43]. Its surface area is much narrower and purpose-built — it's a widget you declare in XML and interact with as part of Android's CoordinatorLayout/AppBar scrolling system, rather than a grab-bag of algorithm demos.

It also has a small internal utility, SystemView.getStatusBarHeight(Context), used to compute the status bar height for layout purposes [coordinatortablayout/src/main/java/cn/hugeterry/coordinatortablayout/utils/SystemView.java:L9-L19] — this is an internal helper, not part of the consumer-facing API.

Key contrast

• jcsprout: no stable/versioned API contract — it's a study repo of many small, independent Java classes covering collections, concurrency, algorithms, JVM topics, etc.
• coordinatortablayout: a single-purpose Android custom view library with one primary integration point (the XML tag + ViewPager pairing).

One caveat from RepoPilot's computed signal: jcsprout is flagged "WAIT — Stale — last commit 2y ago", which is relevant if you're evaluating either as something to depend on going forward — I don't have an equivalent computed signal available for coordinatortablayout in the data retrieved so far.

If you want, I can search for more of coordinatortablayout's public methods (e.g., tab-selection listeners, offset/scroll callbacks) to give a fuller picture of its API surface.

FOLLOW_UPS:

• What other public methods does CoordinatorTabLayout expose?
• Is coordinatortablayout also stale/unmaintained?
• What algorithms does jcsprout implement besides BloomFilter?