// the take
A drop-in replacement for Android's SQLiteOpenHelper that lets you ship a pre-built SQLite database as an app asset instead of writing onCreate SQL by hand, with a naming convention for versioned upgrade scripts. Aimed at Android apps shipping reference data (dictionaries, geodata, seed content) that needs to exist on first launch.
The asset-naming convention for upgrades (dbname_upgrade_from-to.sql) is a genuinely clean way to chain schema migrations without writing imperative Java/Kotlin migration code. Supports ZIP/GZIP-compressed assets to work around APK asset compression issues on old Android versions. The samples cover the full lifecycle (initial create, single-step upgrade, multi-step chained upgrade) so the upgrade path is easy to verify before shipping.
Explicitly unmaintained since 2021 — no Kotlin coroutines support, no Room integration, and it predates Jetpack entirely, so it sits awkwardly next to a modern Android stack. It depends on the old Maven Central coordinate (com.readystatesoftware.sqliteasset) and compile() Gradle syntax, both of which current Android Gradle plugin versions will reject without manual rewriting. onCreate, onUpgrade's low-level control and onDowngrade are all sealed off (declared final), so any app needing custom migration logic beyond plain SQL scripts has to fork the library rather than extend it. No AndroidX artifact exists, and scoped storage changes since Android 10 complicate the alternate constructor that writes the DB to external storage.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →