Makes it easy to create a beautiful about screen for your app.
The library was created in order to provide new animations for activities on Android.
When we use
startActivityForResult(), we have to receive result/data in
This is very complex and inconvenience to us.
The LifecycleModel class is designed to store and manage UI-related data in a lifecycle conscious way, The LifecycleModel class allows data to survive configuration changes such as screen rotations, It also handles the communication of the Activity / Fragment with the rest of the application.
Once you start tugging on the thread of the master-detail pattern, you quickly realize that there are many other design patterns that Google recommends that would affect your implementation, such as using contextual action bars (a.k.a., action modes) for operations on content. Getting all of this design guidance to work, and dealing with classic Android challenges like configuration changes, results in a lot of infrastructure code, before you even begin to start writing actual business logic for the app.
This library is designed to supply that infrastructure code, leaving you free to focus more on what makes your app unique or otherwise important.
Simple universal framework for the Android platform that may be used as base for Activities and Fragments in Android applications.
The utilities provided here allow for automatic unsubscription from sequences based on
Fragment lifecycle events. This capability is useful in Android, where incomplete subscriptions can cause memory leaks.
A Lollipop material design styled android pin-code library.
A library that helps implementing Android's LifeCycleObserver interface for variables instead of Classes, for example:
LiteCycle.with(10).forLifeCycle(this).onResumeUpdate(i -> i + 1).onPauseUpdate(i -> i + 1).observe()
Rx binding of new Android Architecture Component Lifecycle.
CWAC-Presentation: Second Screens Supported Succinctly
This project offers a series of classes that wrap around the Presentation and DisplayManager of Android 4.2.
Rx binding of stock Android Activities & Fragment Lifecycle, avoiding memory leak.
You can dispose an Rx operation when the activity state changes.
Or pause an Rx chain until it's not on an event, for example wait for activity to be resumed to perform an animation.
Android Library that provide simpler way to start the Activities with multiple arguments.
Field and method binding for Android Activity arguments, which uses annotation processing to generate boilerplate code for you, and:
Eliminate all putExtra and getXXXExtra methods. Allows you to forget about all keys that were used to pass agruments. Support flags and Intent provide.
Android library which allows you to swipe down from an activity to close it.
Composition over inheritance
Allows to add functionality into an Android Activity. Just because we all have a BaseActivity in our projects containing too much unused stuff. When it grows, it get unmaintainable.
An example project / library of outside layout activity.
This is contains below components:
This library is an easy to use series of commands to interact with a hashmap across multiple fragments attached to any running activity. This also allows users to pass information between fragments, without a transaction or bundle.
This library allows to use Material activity choosers on Jelly Bean+.
Now you can preserve object instance without any hassle during orientation change.
Android library allowing to preserve instance of any object across orientation changes.
An android library which enables activity/fragment fields retention through configuration changes (e.g screen rotatio) by generating boilerplate code for you.
Android library that adds methods isForeground / isBackground / isReturnedFromBackground.
StayWoke essentially has two features:
This project is an implementation of the User Profile Interface Animation.
An Rx wrapper for receiving results from startActivityForResult() as an