🥄
One Library
  • 🤖onelib
  • 🏡Home
    • Overview
    • Setup Project
    • What's New
  • ☀️Fundamental
    • Basic Android
    • Data Flow
    • Dependency Injection
      • Hilt
      • Koin
  • 📿Layers
    • Data Layer
    • Domain Layer
    • Presentation Layer
  • 🪶Features
    • Views
      • Activity
      • Fragment
      • Bottom Sheet
      • Dialog
    • Adapters
      • Recycler Adapter
      • Filterable Adapter
      • Paging Adapter
      • Selectable Adapter
      • ViewPager Adapter
    • Firebase
      • One Firebase Auth
      • One Firebase Firestore
      • One Firebase Realtime
      • One Firebase Storage
    • Extension Functions
      • Any
      • Common
      • Context
      • Edittext
      • Image View
      • LiveData
      • OneMap
      • State Flow (Jetpack Compose)
      • View
    • Notification
    • One State View
    • Local Database
    • Permission
    • Validation
      • Passive Validator
      • Reactive Validator
      • Extension Validation
Powered by GitBook
On this page
  • Assumptions
  • Technical Capabilities Prerequisite and Preference
  • 1. Clean Code
  • 2. Clean Architecture
  1. Fundamental

Basic Android

Android Minimun Basic Technical Knowledge

Last updated 11 months ago

Assumptions

  1. Have a strong understanding and practical of Algorithm and Data Structure

  2. Have a strong knowledge in Object Oriented Programming

  3. Have a strong understanding and Practical Object Oriented Programming with programming language such as Java

  4. Already have experience in Android App Development and produced at least an app Previously

  5. Have a strong understanding and Practical GIT

Technical Capabilities Prerequisite and Preference

1. Clean Code

2. Clean Architecture

Clean Architecture is a design pattern that promotes separation of concerns, making code more readable, maintainable, and testable. It structures the codebase into multiple layers, each with a distinct responsibility. The key layers are:

  1. Presentation Layer: Contains UI components (Activities, Fragments) and ViewModels.

  2. Domain Layer: Contains use cases and business logic.

  3. Data Layer: Manages data sources (network, database, etc.) and repository implementations.

Layers in Clean Architecture

  1. Presentation Layer

    • View: Activities, Fragments

    • ViewModel: Handles UI-related logic and communicates with the domain layer.

  2. Domain Layer

    • Use Cases (Interactors): Encapsulate business rules and application-specific logic.

    • Entities: Simple data classes representing the core business objects.

  3. Data Layer

    • Repositories: Interfaces defining data operations.

    • Data Sources: Implementations for fetching data (network, local database).

☀️