ObjectBox is a new mobile object database optimized for performance. With ObjectBox, we are bringing technology from NoSQL server databases to mobile. We are impressed by the resulting performance advantage and invite you to try it for yourself. Go make your apps run faster!
Android Things™ was revealed by Google on December 13, 2016. Formerly know as Brillo, which was announced during Google IO 2015, Android Things now is available as a developer preview. The Android Things SDK documentation basically says that developers can use almost the full Android stack for mobile. On top of that there is the “Things Support Library” offering APIs to interact with peripherals and “user drivers”. Both expose a Java API, so “user drivers” are not that close to the metal as the name might suggest.
With greenDAO 3.2.x we are improving Android studio compatibility. Actually, greenDAO 3.2.0 was already released a couple of weeks ago, without a notification post. The first 3.2 release aligned an internal dependency (JDT ) to work nicely with Android Studio 2.2. Also, it added Protocol Buffers support to annotations. Today we are releasing 3.2.1 for the greenDAO plugin. Note that the core greenDAO lib and the generator did not have to be updated and thus remain at V3.2.0. This plugin update further improves Android Studio and Jack compiler integration and fixes some bugs. Check the changelog for details.
What is an Object-Relational-Mapper (ORM)?
An ORM is a layer between the relational SQLite database and the object-oriented app code. The ORM allows the developer to use the database without the need to transform objects into a format suited for the relational database.
Do I need an ORM to work with SQLite?
Today, core Java APIs lack high quality hash functions, and 3rd party implementations provide sub-optimal performance. As non-cryptographic hash function are important building blocks of software, this is a major bummer for developers.
Generally, the selection of available hash functions is plenty, and in the last decade, many new hash functions emerged with very good hashing properties. Surprisingly, the core Java API just still offers Adler32 and CRC32, which were designed as checksums many years ago. Of course, there are many hash implementations available outside of the core Java API. However, Continue reading
4 weeks ago we released greenDAO 3.0 introducing @Entity annotations as an alternative to the generator project. We noticed some issues with this rather big update, and fixed most of those in greenDAO 3.1 (thanks to everyone who reported bugs!). The update also brings two new features:
With greenDAO 3 released, it’s time again to look at the Android ORM performance landscape and do some benchmarks. This time, we also tested newer ORMs for SQLite like DbFlow, requery, SQLDelight, and SquiDB. Also, we had an extensive look at benchmarks done by others. Let’s get started with our results:
At Droidcon Berlin, we noticed a lot of questions around databases and that many people weren’t aware of SQLite alternatives and Object-Relational Mappers (ORMs). Therefore, we follow up with an overview of the mobile database landscape.
What is a mobile database?
While Wikipedia defines a mobile database as “either a stationary database that can be connected to by a mobile computing device […] over a mobile network, or a database which is actually stored by the mobile device,” we solely refer to databases that run on the mobile device itself.
Why use a mobile database?
There are some advantages associated with using a mobile database:
I don’t believe in any statistics I didn’t fake myself (German saying)
Doing good performance benchmarks is hard and benchmarking on Android is no exception. Here is a checklist on how to do fair and robust benchmarks: