What are the migration paths between them?

I can only answer questions about blankj/androidutilcode or cymcsg/ultimaterecyclerview.

Based on the repository data provided, there is no direct migration path between these two projects—they serve fundamentally different purposes:

blankj/androidutilcode is a utility library providing common Android development functions (33,678 stars), organized into:

• utilcode: frequently-used utilities
• subutil: specialized utilities for less common cases

cymcsg/ultimaterecyclerview is a specialized library for RecyclerView and BaseAdapter enhancements (seen in quickAdapter components like [BaseAdapterHelper.java:L44-L83] and [BaseQuickAdapter.java:L1-L39]), focused on adapter patterns and scrollable widgets.

Why no direct migration:

1. Different scopes: androidutilcode is a broad utility collection; ultimaterecyclerview targets RecyclerView/adapter patterns specifically
2. Different dependencies: ultimaterecyclerview has its own BaseAdapter and helper infrastructure; androidutilcode is general-purpose
3. Different use cases: You'd use androidutilcode for general Android helpers; ultimaterecyclerview specifically for enhanced list/grid rendering

Practical coexistence: A project could use both libraries together—androidutilcode for general utilities and ultimaterecyclerview for list rendering—but there's no "migration" between them. They're complementary rather than alternatives.

If you need RecyclerView enhancements, ultimaterecyclerview is purpose-built. If you need general Android utilities, androidutilcode is broader.

FOLLOW_UPS:

• What utilities does androidutilcode provide specifically?
• How does ultimaterecyclerview enhance BaseAdapter performance?
• Can both libraries coexist in one project?