Abstract class containing the common logic and ui for the identification process

Defines common methods for every views, this class should be implemented by the base fragment

Defines a custom checkbox error resources and attach a text to this checkbox If you have a android.text.style.ClickableSpan inside your text you should use this class rather than CheckBox in order to avoid to give a focus to the android.text.style.ClickableSpan when clicking on the CheckBox

Widget made to allow the user to enter a 6 digits code

This class extends the basic EditText and provides a custom InputConnection. The custom InputConnection dispatches a key event when the delete key is pressed with a soft keyboard The default EditText doesn't dispatch the delete key event after API 16, that is not considered as a bug https://developer.android.com/reference/android/view/KeyEvent.html

a Fragment displaying the email identification screen

Util class used to provide error related resources depending on ClientError.ErrorType

Used as a wrapper for data that is exposed via a LiveData that represents an event.

a Fragment used to represents a part of a UI flow, as such, this fragment can continue a flow. the flow could be continue thanks to the keyboard or a button.

Following the MVP design pattern this interface represent the contract for the view and the presenter responsible for the identification feature.

Following the MVP design pattern this interface represent the implementation of the IdentificationContract.Presenter. this class executes the mobile identification business logic and ask for UI updates depending on results.

Defines an information pop up containing an image a title, a description and an additional action this class could be use for any kind of information as error or basic feedback

Describes an input field which is entitled to prevent access to its content if it is considered invalid. Implementations should verify their input before potentially providing it.

This interface should be implemented by every activity managing the soft keyboard state

a listener of the keyboard visibility

a Fragment displaying the phone number identification screen

Base navigation controller defining common method to navigate through screens every and each controller should extend it.

an RuntimeException occurring when a navigation is not set up for a screen

a actionListener of navigation events

a Fragment displaying the one step login screen

an Activity use as navigation controller for the UI login flow. This activity manage the keyboard visibility.

View use for phone number input

Following the MVP design pattern this interface represent the contract for the view and the presenter responsible for the terms and condition feature

a Fragment displaying the terms and conditions screen

Following the MVP design pattern this interface represent the implementation of the TermsContract.Presenter. this class executes the terms and condition business logic and ask for UI updates depending on results.

Following the MVP design pattern this interface represent the contract for the view and the presenter responsible for the code verification feature

a Fragment displaying the code verification screen

Following the MVP design pattern this interface represent the implementation of the VerificationContract.Presenter. this class executes the code verification business logic and ask for UI updates depending on results.

a Fragment used to display a website into the application