For this, I have added the Swipe-to-Refresh functionality in the My Cars and My Tracks. It would be an improvement if the user could also trigger the data loading. The My Cars and My Tracks sections load data automatically. Swipe-to-Refresh feature in My Cars and My Tracks section: One of them is a swipe-to-refresh feature. Various operators that can be used for data manipulation if needed.Īpart from successfully achieving all of my specified and assigned goals for Phase 1, I have also added various features to provide a better user experience and seamless functionalities to users (See PR’s).The team can have more control over threading techniques.Predefined methods for functionalities like subscribe and publish events are easier.It also simplifies the communication between components and avoids decoupling event senders and receivers.Ī few advantages of using the RxJava based event bus versus the Otto event bus are: Also, the RxJava based event bus is the best option for getting asynchronous data requests from APIs. Since the project already uses reactive components of RxJava and RxAndroid, applying the event bus implementation based on these libraries has been straightforward. My 3rd goal was to implement an RxJava/ RxAndroid based event bus library and to remove the Otto event bus library as it has been deprecated. Working of Jetpack ViewBinding Goal 3: Implement RxJava Event Bus to replace Otto Event Bus library Jetpack view binding is compile time safe.By upgrading to Jetpack view binding, the following impacts are seen in the app. The main impact of this goal is to provide a cleaner approach for separating views from models. My second goal for the period was to replace the dependency and usage of the ButterKnife view binding library with the latest and modular android released JetPack view binding technique. It helps to provide better code quality, readability and reusability of the views and components. View binding is very essential and crucial to large android projects. Goal 2: Replacement of ButterKnife View Binding with Jetpack View Binding Now the app is completely migrated to RxJava 3 and takes complete advantage of the new version. In the process, I faced many errors that also had to be fixed, such as a Gradle dependency error, class path error, importing dependencies, implicit/explicit conversion and abstract methods override errors. Reducing errors: Version 3 is not just an Observer implementation, it also provides good error handling and retry mechanisms, which come in handy.In addition, version 3 provides a lot of powerful operators that help to make the codebase much simpler while boosting performance. Performance improvement: Parallel execution of different, independent tasks improves performance.Threading, error handling, caching and cancellation are much easier.There are various benefits to RxJava 3 versus 2 : I replaced the deprecated RxJava version 2 with RxJava version 3. My first goal of GSOC 2022 was to update the RxJava library. Goals Goal 1: Migration of RxJava from version 2 to 3 My goal is to update all the deprecated libraries currently implemented by replacing them with superior alternatives or updating them to their latest stable release. The enviroCar app makes use of various 1st and 3rd party open source libraries to provide various functionalities along with a seamless experience to users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |