The last commit in the library is also in Dec. 2014.
That library does not do very much, and so I would not expect it to be changing. SQLiteAssetHelper works just fine.
However, SQLiteAssetHelper is a solution for a specific problem: shipping a database with an app.
On the other hand, in this official guide, they are saying that the recommended method for creating an SQLite database is to subclass SQLiteOpenHelper, from which one can infer that Google is now recommending the use of native Android API to create and work with databases.
Um, SQLiteAssetHelper extends SQLiteOpenHelper, and it uses the “native Android API to create and work with databases”.
Furthermore, SQLiteOpenHelper, on its does, does nothing for a specific problem: shipping a database with an app.
now as of 2016, what is the recommended way of creating and working with and shipping an SQLite database in an Android application?
Given the “and shipping” bit, I strongly recommend SQLiteAssetHelper.
Conversely, if you are not shipping a database with your app — which computer programmers would define as “having a database with a schema and data that you want to include in the shipped app to use as a starting point” — then just use SQLiteOpenHelper and define your database on the fly.
solved How to go about developing an Android app with SQLite database? [closed]