How do their APIs compare?

I want to flag a scoping issue with this question: neither h2pl/javatutorial nor yuliskov/smarttube expose a public "API" in the sense of a library/service contract meant for external consumers. They're structurally very different projects, so let me clarify what's actually comparable based on what's in the repository data.

h2pl/javatutorial — Not an API at all This repo is a documentation/study-guide repository of Markdown files covering Java fundamentals, concurrency, JVM internals, collections, etc. There is no source code exposing classes or methods to call. Examples in the retrieved data are illustrative code snippets embedded in tutorials, such as:

• AQS lock acquisition walkthroughs in [docs/Java/concurrency/Java并发指南：JUC的核心类AQS详解.md:L160-L199] and the queue-insertion logic at [docs/Java/concurrency/Java并发指南：JUC的核心类AQS详解.md:L240-L279]
• An explanation of the Comparable interface and its compareTo contract in [docs/Java/collection/Java集合详解：Iterator，fail-fast机制与比较器.md:L426-L465]
• A rundown of java.lang.Enum's built-in methods (name(), ordinal(), valueOf(), values()) in [docs/Java/basic/枚举类.md:L471-L490]

So "its API" would really mean "the Java standard library APIs it explains," not something the repo itself defines.

yuliskov/smarttube — An actual internal application API surface This is a real Android application (an alternative YouTube client), and it does have internal Java interfaces/classes that form its architecture:

• SearchTagsProvider, a small interface with a search(String query, ResultsCallback callback) method and a nested ResultsCallback interface [common/src/main/java/com/liskovsoft/smartyoutubetv2/common/app/models/search/SearchTagsProvider.java:L7-L13], implemented by MediaServiceSearchTagProvider which wraps a reactive ContentService call [common/src/main/java/com/liskovsoft/smartyoutubetv2/common/app/models/search/MediaServiceSearchTagProvider.java:L13-L41]
• Presenter-layer methods like ChannelPresenter.onSearchSubmit(String query) that call into getContentService() and subscribe to an RxJava Observable<MediaGroup> [common/src/main/java/com/liskovsoft/smartyoutubetv2/common/app/presenters/ChannelPresenter.java:L389-L418]
• Domain model classes such as Video with custom equals/hashCode semantics based on multiple ID fields rather than reference equality [common/src/main/java/com/liskovsoft/smartyoutubetv2/common/app/models/data/Video.java:L236-L275], and Playlist with containment-checking methods like contains and containsAfterCurrent [common/src/main/java/com/liskovsoft/smartyoutubetv2/common/app/models/data/Playlist.java:L132-L171]
• Error-handling logic in ErrorFixerController that inspects player error types/renderer indices and error message strings to decide on remediation (disabling subtitles, lowering quality, restarting the engine) [common/src/main/java/com/liskovsoft/smartyoutubetv2/common/app/models/playback/controllers/ErrorFixerController.java:L142-L221, L262-L301]

Bottom line comparison

• javatutorial: no API — it's prose/reference material about Java language and JVM concepts.
• smarttube: has a real internal API layer, following a provider/presenter/controller pattern with heavy use of RxJava Observable/Disposable for async data (search, channel content), plus domain models with custom equality logic for UI diffing.

RepoPilot's computed verdict for javatutorial is "WAIT — Slowing — last commit 12mo ago," which is a maintenance/activity signal, not an API-quality signal — no equivalent computed signal was provided for smarttube in this data.

If you meant something more specific (e.g., comparing smarttube's ContentService/YouTube data API wrapper to something else, or comparing coding patterns), let me know and I can search for that.

FOLLOW_UPS:

• What does smarttube's ContentService interface look like?