vinayak90 / sessionmanager

Login/register app using Reqres REST API with auto-re-authentication when the app launches. The app uses MVVM architecture with Jetpack (Room, ViewModel, LiveData, DataStore, View Binding), Hilt, Coroutines, Flows, etc...

SessionManager

Faking login/register app using Reqres REST API with auto-re-authentication when the app launches. The app uses MVVM architecture with Jetpack (Room, ViewModel, LiveData, DataStore, View Binding), Hilt, Coroutines, Flows, etc...

Project features

This app uses some modern Android tech stacks & libraries:

• 100% Kotlin + Coroutines + Flow for asynchronus
• Hilt - for dependency injection.
• Retrofit2 - A type-safe HTTP client for Android.
• Moshi - a modern JSON library for Android.
• JetPack:
  • LiveData - observable data holder class.
  • ViewModel - store and manage UI-related data in a lifecycle conscious way.
  • Room Persistence - local database.
  • ViewBinding - interact with views (replacement for findViewById).
  • DataStore - replacement for SharedPreferences - allows to store key-value pairs.
• Architecture:
  • MVVM Architecture
  • Repository pattern with use-cases.
  • Mapping local entities and remote data transfer objects (DTOs) into Domain Model.
• Timber - logging.

Open API (Reqres)

SessionManager uses the Reqres REST API for faking login/registration and receiving an auth token. Reqres simulates real application scenarios. If you want to test a user authentication system, Reqres will respond to a successful login/register request with a token for you to identify a sample user, or with a 403 forbidden response to an unsuccessful login/registration attempt. With Reqres you can only login/register with predefined users.

How does auto-authentication work?

When a user successfully logs in or registers, the user's email gets saved into the DataStore (the key-value email denotes what the previously authenticated user was). When the app opens the next time, the first thing that is checked is this email key-value. Then the email is used to query the token from the Room Persistence library.
If the token is found, the user is automatically authenticated. If the token isn't found, the user won't be authenticated.
When the user logs out, the token is deleted from the database, so even though the email is still in the DataStore, the token will never be found, so the user won't be authenticated