Valos

This is a Valorant app with multi module. The app has Navigation, Feature, Data, Domain, Common, App and buildSrc for better gradle control.

Project Screens

SPLASH SCREEN	AGENTS SCREEN	WEAPONS SCREEN	MAPS SCREEN	FAVORİTE SCREEN

Project Tech stack & Open-source libraries

• This app made %100 with Kotlin

• Made with Android Architecture Components for the Collection of libraries that help you design robust, testable, and maintainable apps.

• ViewModel:The ViewModel class is a business logic or screen level state holder. It exposes state to the UI and encapsulates related business logic. Its principal advantage is that it caches state and persists it through configuration changes. This means that your UI doesn’t have to fetch data again when navigating between activities, or following configuration changes, such as when rotating the screen.

• Kotlin Flow:In coroutines, a flow is a type that can emit multiple values sequentially, as opposed to suspend functions that return only a single value. For example, you can use a flow to receive live updates from a database.

• Kotlin Coroutine:On Android, coroutines help to manage long-running tasks that might otherwise block the main thread and cause your app to become unresponsive. Over 50% of professional developers who use coroutines have reported seeing increased productivity. This topic describes how you can use Kotlin coroutines to address these problems, enabling you to write cleaner and more concise app code.

• Dependency Injection with Hilt:Hilt is a dependency injection library for Android that reduces the boilerplate of doing manual dependency injection in your project. Doing manual dependency injection requires you to construct every class and its dependencies by hand, and to use containers to reuse and manage dependencies.

• Navigation Componenet:Navigation refers to the interactions that allow users to navigate across, into, and back out from the different pieces of content within your app. Android Jetpack's Navigation component helps you implement navigation, from simple button clicks to more complex patterns, such as app bars and the navigation drawer.

• Retrofit:Retrofit is the class through which your API interfaces are turned into callable objects. By default, Retrofit will give you sane defaults for your platform but it allows for customization.

• UseCase:Located domain layer that sits between the UI layer and the data layer.

• Repository:Located in data layer that contains application data and business logic.

• Glide :A library for imageView.

• Lottie :A library for animations.

Project Graph

• This app uses MVVM (Model View View-Model)architecture

This project has 7 Module ;

• App

• buildSrc

• Data

• Domain

• Feature

• Navigation

• Common

DATA MODULE

Data Layer: While the UI layer contains UI-related state and UI logic, the data layer contains application data and business logic. The business logic is what gives value to your app—it's made of real-world business rules that determine how application data must be created, stored, and changed.

inside the DATA Module:

-- Repository

-- Dto

-- Service

-- Source

-- DataStore

-- Mapper

-- Di

DOMAİN MODULE

Domain Layer: The domain layer is responsible for encapsulating complex business logic, or simple business logic that is reused by multiple ViewModels. This layer is optional because not all apps will have these requirements. You should only use it when needed-for example, to handle complexity or favor reusability.

inside the DOMAİN Module:

-- Di

-- UseCase

FEATURE MODULE

UI Layer: The role of the UI is to display the application data on the screen and also to serve as the primary point of user interaction. Whenever the data changes, either due to user interaction (like pressing a button) or external input (like a network response), the UI should update to reflect those changes. Effectively, the UI is a visual representation of the application state as retrieved from the data layer.

inside the FEATURE Module:

-- Fragments

-- Components

-- Di

-- Mapper

-- Utility

COMMON MODULE

inside the COMMON Module:

-- Fragments

-- Components

-- Di

-- Mapper

-- Utility

NAVİGATİON MODULE

inside the NAVİGATİON Module:

-- NavGraph

buildSrc MODULE

inside the buildSrc Module:

-- Dependency

APP MODULE

inside the APP Module:

-- MainActivity

-- Application Class