GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - orcchg/SampleAndroidArchAtScale: Sample project that demonstrates Android Architecture at scale in 2021-th

This repository was archived by the owner on Jun 29, 2024. It is now read-only.
BranchesTags
Open more actions menu

Latest commit

 

History

69 Commits
69 Commits

Folders and files

NameName
Last commit message
Last commit date
.idea
.idea
 
 
androidUtil
androidUtil
 
 
app
app
 
 
base
base
 
 
core
core
 
 
design
design
 
 
feature
feature
 
 
gradle
gradle
 
 
navigation
navigation
 
 
util
util
 
 
.gitignore
.gitignore
 
 
README.md
README.md
 
 
build.gradle.kts
build.gradle.kts
 
 
gradle.properties
gradle.properties
 
 
gradlew
gradlew
 
 
gradlew.bat
gradlew.bat
 
 
screenshot_main.png
screenshot_main.png
 
 
settings.gradle.kts
settings.gradle.kts
 
 

Repository files navigation

SampleAndroidArchAtScale

Sample project that demonstrates Android Architecture at scale in 2021-th

Medium Article

The main idea of the Architecture is the statement that any product feature (or core library) could have its functionality separated from the UI and shared with the others within the whole project. This allows us to reuse features’ functionality flexibly, test it in isolation using demo apps, and write tests easier. Separation of the UI and the logic in different modules also simplifies usage of Android dynamic features and increases a degree of the project’s modularity, which is good for build performance and dependency management. The Architecture follows the principles of Clean Arch, but the presentation layer is still open to extension or alter: it’s possible to choose between MVP, MVI or MVVM, though the latter is preferred due to ubiquitous usage of Jetpack. An explicit separation between API and implementation is good when we need to have multiple implementations. It is also good for testing and for better clarity. The Architecture is scalable: every feature has the same structure and usage, and there is no systematic debt that could accumulate over time as the project grows. And last, but not least, DI is also an important foundation of Architecture. Thanks to Dagger 2, it’s compile-time safe.

About

Sample project that demonstrates Android Architecture at scale in 2021-th

Resources

Readme
Activity

Stars

32 stars

Watchers

1 watching

Forks

2 forks
Report repository

Releases

Packages

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.