EventBus 3 released, now based on @Annotations
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.
Why did Parse fail?
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?
Android Architecture with EventBus
Google’s Android Dev Summit 2015 covered a talk on Android Application Architecture. Android Apps often have complex interactions among data models, application logic, UI views and controllers, and networking. A solid architecture is the key to get this right. Watch the two Googlers Yigit Boyar and Adam Powell using EventBus as an important app’s component:
On the progress of EventBus 3
You may have heard about the upcoming version 3 of EventBus:Continue reading
Recent Comments