Open Source libraries to speed up app developers

Our open source libraries run on over a billion devices and are used by large companies with especially high performance requirements.
Learn about our widely used, battle-tested, and performance-optimized open source libararies for mobile app development:

> 2.000.000.000 people rely on greenrobot libraries

Slim & fast - that is what we stand for and that is why thousands of mobile developers wordlwide use our solutions, leading to more than a billion mobile users relying on our code

apps fast on the road

Superfast

Above all, we value performance. Speed matters. Thus, we constantly benchmark our solutions against alternatives and optimize for performance.
lean and light development

Lean & light

We keep all our solutions small and frugal. We also ensure all our open source libraries are optimized for maximum battery-friendliness. Perfect for mobile.
Easy to use libraries

Easy-to-use

We are developers ourselves and value the fun aspects of coding. Accordingly, our libraries are easy to use and save developers from tedious and unituitive tasks.
Open development

Developer-driven

We are passionate to deliver high performant, slim, and elegant solutions. Our libraries have more than 15.000 GitHub stars and are industry-proven.

Mobile News from greenrobot

Library updates, new releases, related developments in open source, mobile databases, and Android

greenDAO 2.2 with Database Encryption

Encryption is the central feature of today’s greenDAO 2.2 release. Actually, greenDAO seems to be the first Android ORM to officially support SQLCipher (non-beta). Since it’s first (source-only) release in August 2015, greenDAO’s encryption support has been successfully tested in a complex setup for months. So, if you want to store sensitive data in your database, give it a try!
Continue reading

Avoid NoClassDefFoundError during EventBus registration

There is an obscure scenario causing some older Android versions to throw java.lang.NoClassDefFoundError when trying to register subscribers in EventBus. It was reported often in connection to the class  PersistableBundle, which was introduced in Android API level 21. It seems like an Android bug with reflection, but of course you don’t want your app to crash. Thus, we just added an FAQ entry with covering some background and a couple of solutions. One preferred solution is to update to EventBus 3 along with the subscriber index. Because the index is created during build time, it avoids problematic (and slow) reflection altogether!

EventBus 3 released, now based on @Annotations

EventBus3
Today, we are pleased to release EventBus 3. Previous versions of EventBus rejected to use annotations for performance reasons. Now, version 3 embraces annotations to improve performance. How does that make sense? Unfortunately, Android’s performance did not get any better. Reflection on annotations is still very bad compared to Desktop Java, even on Android 6 and ART. EventBus 3 resolves this problem by introducing a new annotation processor, which will index all annotations at build time. It generates a class containing all the data that would be expensive to get at run time. Build-time indexing makes EventBus 3 the fastest EventBus ever.

Continue reading

Why did Parse fail?

drowing_duck_1600x446
On January, 28th, Facebook announced the retirement of Parse. Parse was one of the leaders in the “mobile backend as a service” (MBaaS) space. It gave app developers a hosted alternative to building a custom backend from scratch for data storage and some logic around that data. Parse was acquired in 2013 by Facebook for $85 million and was powering 500,000 apps in 2014 according to Wikipedia. So what turned the success story into a failure?

Continue reading

Spread the love
  • 12
  •  
  • 940
  •  
  • 1
  •  
  •  
  •  
  •  
  •  
  •