RxPermissions - Android runtime permissions powered by RxJava2

  •        32

This library allows the usage of RxJava with the new Android M permission model. To use this library your minSdkVersion must be >= 11.

https://github.com/tbruyelle/RxPermissions

Tags
Implementation
License
Platform

   




Related Projects

RxJava2-Android-Samples - RxJava 2 Android Examples - Migration From RxJava 1 to RxJava 2 - How to use RxJava 2 in Android

  •    Java

RxJava 2.0 has been completely rewritten from scratch on top of the Reactive-Streams specification. The specification itself has evolved out of RxJava 1.x and provides a common baseline for reactive systems and libraries. Because Reactive-Streams has a different architecture, it mandates changes to some well known RxJava types.

android-data-binding-rxjava - Demo that shows how to use RxJava with Android Data Binding ObservableFields

  •    Java

Simple demo developed with love at Tango which demonstrates how to wrap Android DataBinding ObservableField into RxJava's Observable. With this solution it is possible to register for ObservableField's value changes and use it with RxJava operators.

RxJava-Android-Samples - Learning RxJava for Android by example

  •    Java

This is a repository with real-world useful examples of using RxJava with Android. It usually will be in a constant state of "Work in Progress" (WIP). I've also been giving talks about Learning Rx using many of the examples listed in this repo.


frodo - Android Library for Logging RxJava Observables and Subscribers.

  •    Java

Frodo is an android library inspired by Jake Wharton's Hugo, mainly used for logging RxJava Observables and Subscribers outputs on the logcat. It generates and weaves code based on annotations only on debug versions of the application where the plugin is applied, for instance, it is safe to persist any Frodo annotation in the codebase. @RxLogObservable.Scope Options: It is possible to narrow down the debug information shown by adding a debugging scope to @RxLogObservable annotation.

RxJavaDemoApp - This repository contains 100+ examples using RxJava for Android

  •    Java

This repository is intended to provide in a single place (i.e. a single Android app) over than 100 examples of RxJava for Android which you can use as a reference when dealing with RxJava. Some examples were already covered into details in one of the articles of our RxJava series (you can find the links below), while some other were based on external articles, so you can go directly to those articles and see the the authors' explanations.

Elephant - Elephant is PHPHub Community Android unofficial client, base on Material Design + MVP+RxJava+Retrofit

  •    Java

PHPHub is a Forum project written in Laravel 4.2, and it is also the project build up PHP & Laravel China community. Elephant is PHPHub Community Android unofficial client, App UI style follows the Google Material Design, architecture project using MVP mode, the data processing using RxJava + Retrofit network data processing.

ReactiveNetwork - Android library listening network connection state and Internet connectivity with RxJava Observables

  •    Java

ReactiveNetwork is an Android library listening network connection state and Internet connectivity with RxJava Observables. It's a successor of Network Events library rewritten with Reactive Programming approach. Library supports both new and legacy network monitoring strategies. Min sdk version = 9. Please note: Due to memory leak in WifiManager reported in issue 43945 in Android issue tracker it's recommended to use Application Context instead of Activity Context.

Grant - Simplifying Android Permissions

  •    Java

The Android permissions model has changed in Android Marshmallow. Now you can't count on all the permissions you've declared in your AndroidManifest file being granted at run-time. The user has control over granting these permissions to your app and can revoke them at any time, even while your app is running! Because of this, you need to check if you have permission to run certain code before executing it. The new Android permissions API is fairly simple to understand, but it can introduce unnecessary complexity into the flow of your application. Let's use the the WRITE_EXTERNAL_STORAGE permission as an example of this unnecessary complexity. You want to write a String to a file on the external storage of the device.

android-oss - Kickstarter for Android. Bring new ideas to life, anywhere.

  •    Java

Welcome to Kickstarter's open source Android app! Come on in, take your shoes off, stay a while—explore how Kickstarter's native squad has built and continues to build the app, discover our implementation of RxJava in logic- filled view models, and maybe even create an issue or two. We've also open sourced our iOS app, written in Swift: check it out here. Read more about our journey to open source here.

android-mvp-architecture - This repository contains a detailed sample app that implements MVP architecture using Dagger2, GreenDao, RxJava2, FastAndroidNetworking and PlaceholderView

  •    Java

This is a boilerplate project aimed to help bootstrap new Android MVP Applications. Feel free to fork this application or use AndroidStarters to create new app using this boilerplate. All pull requests are welcome, make sure to follow the contribution guidelines when you submit pull request.

android-RuntimePermissions

  •    Java

This sample shows runtime permissions available in Android M and above. It shows how to check and request permissions at runtime, handle backwards compatibility using the support library and how to declare optional permissions for M-devices only. Android M introduced runtime permissions. Applications targeting M and above need to request their permissions at runtime. All permissions still need to be declared in the AndroidManifest. However, when accessing APIs that require a permission, the Activity or Fragment has to verify that the permission has been granted or request the missing permissions using calls through the support library. Permissions are checked through ActivityCompat#checkSelfPermission(Context, String) or ContextCompat#checkSelfPermission(Context, String). Permission are requested through ActivityCompat#requestPermissions(Activity, String[], int), and the response received in a callback to ActivityCompat.OnRequestPermissionsResultCallback#onRequestPermissionsResult(int, String[], int[]). Applications can provide an additional rational for the use of permissions after calling ActivityCompat#shouldShowRequestPermissionRationale(Activity,String). This call will return true if the application should provide the user with more context on why the requested permissions is needed, for example if the permission request has been denied before.

AutoDispose - Automatic binding+disposal of RxJava 2 streams.

  •    Java

AutoDispose is an RxJava 2 tool for automatically binding the execution of RxJava 2 streams to a provided scope via disposal/cancellation.Often (especially in mobile applications), Rx subscriptions need to stop in response to some event (for instance, when Activity#onStop() executes in an Android app). In order to support this common scenario in RxJava 2, we built AutoDispose.

Android-RxJava - Learning RxJava for Android by example

  •    Java

Learning RxJava for Android by example