A blazing fast, powerful, and simple ORM Android database library built on SQLite with Kotlin and annotation processing.
DBFlow is an ORM (Object-Relational Mapping) Android database library built on SQLite that writes database code for you using annotation processing. It provides a powerful SQLite query language and eliminates boilerplate code, making database operations fast and simple. The library is designed to be efficient and feature-rich, supporting modern Android development patterns.
Android developers using Kotlin who need a robust, efficient database solution with minimal boilerplate and support for reactive programming and architecture components.
Developers choose DBFlow for its blazing fast performance, automatic code generation via annotation processing, and comprehensive feature set including Kotlin integration, architecture components support, and optional encryption. It combines the best features of many database libraries into one simple yet powerful tool.
A blazing fast, powerful, and very simple ORM android database library that writes database code for you.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates SQLite boilerplate code automatically, eliminating manual work as highlighted in the README's key features, which simplifies database setup.
Built with Kotlin for null-safe and concise code, making database operations more efficient and enjoyable, as emphasized in the library's philosophy.
Integrates with Android Architecture Components like LiveData and Paging, plus Coroutines and RX Java for reactive programming, as listed in the features section.
Supports SQLCipher for database encryption through a dedicated module, providing secure data storage as an optional feature in the dependencies.
Requires adding multiple dependencies for different features, which can complicate setup and increase APK size compared to all-in-one solutions.
Current version is 5.0.0-alpha2, indicating potential breaking changes and instability, as noted in the release status from the README.
Detailed usage is in a separate GitBook, which might not be as accessible or up-to-date compared to inline documentation, potentially slowing onboarding.