[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-7466":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":22,"hasPages":22,"topics":23,"createdAt":10,"pushedAt":10,"updatedAt":44,"readmeContent":45,"aiSummary":46,"trendingCount":16,"starSnapshotCount":16,"syncStatus":17,"lastSyncTime":47,"discoverSource":48},7466,"android-modular-architecture","vmadalin\u002Fandroid-modular-architecture","vmadalin","📚  Sample Android Components Architecture on a modular word focused on the scalability, testability and maintainability written in Kotlin, following best practices using Jetpack.","https:\u002F\u002Fproandroiddev.com\u002Fandroid-components-architecture-in-a-modular-word-7414a0631969",null,"Kotlin",2436,390,94,3,0,2,59.98,"Apache License 2.0",false,"master",true,[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"android","android-architecture","android-boilerplate","android-showcase","architecture","best-practices","clean-architecture","clean-code","component-architecture","dynamic-features","gradle-kotlin-dsl","hacktoberfest","jetpack","kotlin","modern-android-development","modular-architecture","mvvm-architecture","solid","solid-principles","testing","2026-06-12 04:00:33","## Android Components Architecture in a Modular Word\n[![CircleCI](https:\u002F\u002Fcircleci.com\u002Fgh\u002FVMadalin\u002Fandroid-modular-architecture\u002Ftree\u002Fmaster.svg?style=shield)](https:\u002F\u002Fcircleci.com\u002Fgh\u002FVMadalin\u002Fandroid-modular-architecture\u002Ftree\u002Fmaster)\n[![Codecov](https:\u002F\u002Fcodecov.io\u002Fgh\u002FVMadalin\u002Fandroid-modular-architecture\u002Fcoverage.svg)](https:\u002F\u002Fcodecov.io\u002Fgh\u002FVMadalin\u002Fandroid-modular-architecture)\n[![Codacy](https:\u002F\u002Fapi.codacy.com\u002Fproject\u002Fbadge\u002FGrade\u002F5970b6648df0465588f9781ae6e3332e)](https:\u002F\u002Fwww.codacy.com\u002Fmanual\u002FVMadalin\u002Fkotlin-sample-app?utm_source=github.com&utm_medium=referral&utm_content=VMadalin\u002Fkotlin-sample-app&utm_campaign=Badge_Grade)\n[![CodeStyle](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fcode%20style-%E2%9D%A4-FF4081.svg)](https:\u002F\u002Fktlint.github.io\u002F)\n[![Kotlin Version](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fkotlin-1.4.10-blue.svg)](http:\u002F\u002Fkotlinlang.org\u002F)\n[![Gradle](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fgradle-6.6.1-blue.svg)](https:\u002F\u002Flv.binarybabel.org\u002Fcatalog\u002Fgradle\u002Flatest)\n[![API](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FAPI-21%2B-blue.svg?style=flat)](https:\u002F\u002Fandroid-arsenal.com\u002Fapi?level=21)\n[![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-Apache%202.0-lightgrey.svg)](http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0)\n\n\u003Cimg src=\"screenshots\u002Fdemo\u002Fdemo.gif\" width=\"250\" align=\"right\" hspace=\"20\">\n\nAndroid Components Architecture in a Modular Word is a sample project that presents modern, 2020 approach to [Android](https:\u002F\u002Fwww.android.com\u002F) application development using [Kotlin](https:\u002F\u002Fkotlinlang.org\u002F) and latest tech-stack.\n\nThe goal of the project is to demonstrate best practices, provide a set of guidelines, and present modern Android\napplication architecture that is modular, scalable, maintainable and testable. This application may look simple, but it\nhas all of these small details that will set the rock-solid foundation of the larger app suitable for bigger teams and\nlong application lifecycle management.\n\n## Table of Contents\n\n-   [Mentions](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#mentions)\n-   [Development](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#development)\n-   [Design](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#design)\n-   [Architecture](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#architecture)\n-   [Documentation](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#documentation)\n-   [Tech-stack](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#tech-stack)\n-   [Resources](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#resources)\n-   [Contributions](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#contributions)\n-   [Authors](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#authors)\n-   [License](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app#license)\n\n## Mentions\n\nThe project received different mentions\u002Freference from Android Developer Community:\n\n-   [Android Weekly](https:\u002F\u002Fandroidweekly.net\u002Fissues\u002Fissue-407) Newsletter that helps you to stay cutting-edge with your Android Development.\n-   [AndroidSweets](https:\u002F\u002Fandroidsweets.ongoodbits.com\u002F2019\u002F12\u002F13\u002Fbrowsing-through-the-android-open-source-project-was-never-easier) Fresh news from Droid zone.\n-   [Android Awesome](https:\u002F\u002Fgithub.com\u002FJStumpp\u002Fawesome-android#code-examples) A curated list of awesome Android libraries and resources.\n-   [Droidcon](https:\u002F\u002Fwww.droidcon.com\u002Fnews-detail?content-id=\u002Frepository\u002Fcollaboration\u002FGroups\u002Fspaces\u002Fdroidcon_hq\u002FDocuments\u002Fpublic\u002Fnews\u002Fandroid-news\u002FAndroid%20Components%20Architecture%20in%20a%20Modular%20Word) Blog posts from leading authorities and video archive from droidcons around the world.\n-   [DroidconKE](https:\u002F\u002Fgithub.com\u002FdroidconKE\u002FdroidconKE2020App#referencesresources-1) The official DroidconKE 2020 conference App.\n-   [Github trending](https:\u002F\u002Fgithub.motakasoft.com\u002Ftrending\u002F?d=2019-12-11&l=all) See what the GitHub community is most excited about today.\n-   [KotlinBy](https:\u002F\u002Fgithub.com\u002FKotlinBy\u002Fawesome-kotlin#projects-back--1) A curated list of awesome Kotlin related stuff.\n-   [Reddit](https:\u002F\u002Fwww.reddit.com\u002Fr\u002FKotlin\u002Fcomments\u002Few30x4\u002Fgithub_vmadalinkotlinsampleapp_android_sample_app\u002F?utm_source=share&utm_medium=web2x): Discussion about Kotlin, a statically typed programming language for the JVM, Android, JavaScript, and native.\n\n## Development\n\n### Environment setup\n\nFirst off, you require the latest Android Studio 4.1.0 (or newer) to be able to build the app.\n\nYou need to supply keys for Marvel API. You can find information about how to gain access by using the [link](https:\u002F\u002Fdeveloper.marvel.com).\n\nWhen you obtain the keys, you can provide them to the app by putting the following in the `local.properties` project root file:\n\n```properties\n#Marvel API KEYS\nmarvel.key.public = \u003Cinsert>\nmarvel.key.private = \u003Cinsert>\n```\n\n### Code style\n\nTo maintain the style and quality of the code, are used the bellow static analysis tools. All of them use properly configuration and you find them in the project root directory `.{toolName}`.\n\n| Tools                                                   | Config file                                                                       | Check command             | Fix command               |\n|---------------------------------------------------------|----------------------------------------------------------------------------------:|---------------------------|---------------------------|\n| [detekt](https:\u002F\u002Fgithub.com\u002Farturbosch\u002Fdetekt)          | [\u002F.detekt](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Ftree\u002Fmaster\u002F.detekt)     | `.\u002Fgradlew detekt`        | -                         |\n| [ktlint](https:\u002F\u002Fgithub.com\u002Fpinterest\u002Fktlint)           | -                                                                                 | `.\u002Fgradlew ktlint`        | `.\u002Fgradlew ktlintFormat`  |\n| [spotless](https:\u002F\u002Fgithub.com\u002Fdiffplug\u002Fspotless)        | [\u002F.spotless](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Ftree\u002Fmaster\u002F.spotless) | `.\u002Fgradlew spotlessCheck` | `.\u002Fgradlew spotlessApply` |\n| [lint](https:\u002F\u002Fdeveloper.android.com\u002Fstudio\u002Fwrite\u002Flint) | [\u002F.lint](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Ftree\u002Fmaster\u002F.lint)         | `.\u002Fgradlew lint`          | -                         |\n\nAll these tools are integrated in [pre-commit git hook](https:\u002F\u002Fgit-scm.com\u002Fbook\u002Fen\u002Fv2\u002FCustomizing-Git-Git-Hooks), in order\nensure that all static analysis and tests passes before you can commit your changes. To skip them for specific commit add this option at your git command:\n\n```properties\ngit commit --no-verify\n```\n\nThe pre-commit git hooks have exactly the same checks as [CircleCI](https:\u002F\u002Fcircleci.com\u002F) and are defined in this [script](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Fblob\u002Fmaster\u002Fscripts\u002Fgit-hooks\u002Fpre-commit.sh). This step ensures that all commits comply with the established rules. However the continuous integration will ultimately be validated that the changes are correct.\n\n## Design\n\nApp [support different screen sizes](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Fmultiscreen\u002Fscreensizes) and the content has been adapted to fit for mobile devices and tablets. To do that, it has been created a flexible layout using one or more of the following concepts:\n\n-   [Use constraintLayout](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Fmultiscreen\u002Fscreensizes#ConstraintLayout)\n-   [Avoid hard-coded layout sizes](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Fmultiscreen\u002Fscreensizes#TaskUseWrapMatchPar)\n-   [Create alternative layouts](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Fmultiscreen\u002Fscreensizes#alternative-layouts)\n-   [Use the smallest width qualifier](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Fmultiscreen\u002Fscreensizes#TaskUseSWQuali)\n-   [Use the available width qualifier](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Fmultiscreen\u002Fscreensizes#available-width)\n-   [Add orientation qualifiers](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Fmultiscreen\u002Fscreensizes#TaskUseOriQuali)\n\nIn terms of design has been followed recommendations [android material design](https:\u002F\u002Fdeveloper.android.com\u002Fguide\u002Ftopics\u002Fui\u002Flook-and-feel) comprehensive guide for visual, motion, and interaction design across platforms and devices. Granting the project in this way a great user experience (UX) and user interface (UI). For more info about UX best practices visit [link](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Fgoogle-play-instant\u002Fbest-practices\u002Fapps).\n\nMoreover, has been implemented support for [dark theme](https:\u002F\u002Fdeveloper.android.com\u002Fguide\u002Ftopics\u002Fui\u002Flook-and-feel\u002Fdarktheme) with the following benefits:\n-   Can reduce power usage by a significant amount (depending on the device’s screen technology).\n-   Improves visibility for users with low vision and those who are sensitive to bright light.\n-   Makes it easier for anyone to use a device in a low-light environment.\n\n| Mode  | Characters list                                                          | Characters favorite                                                          | Character detail                                                          |\n|-------|--------------------------------------------------------------------------|------------------------------------------------------------------------------|---------------------------------------------------------------------------|\n| Light | \u003Cimg src=\"screenshots\u002Fphone\u002Flight_mode_characters_list.png\" width=\"250\"> | \u003Cimg src=\"screenshots\u002Fphone\u002Flight_mode_characters_favorite.png\" width=\"250\"> | \u003Cimg src=\"screenshots\u002Fphone\u002Flight_mode_character_detail.png\" width=\"250\"> |\n| Dark  | \u003Cimg src=\"screenshots\u002Fphone\u002Fdark_mode_characters_list.png\" width=\"250\">  | \u003Cimg src=\"screenshots\u002Fphone\u002Fdark_mode_characters_favorite.png\" width=\"250\">  | \u003Cimg src=\"screenshots\u002Fphone\u002Fdark_mode_character_detail.png\" width=\"250\">  |\n\n## Architecture\n\nThe architecture of the application is based, apply and strictly complies with each of the following 5 points:\n\n\u003Cimg src=\"screenshots\u002Farchitecture\u002Fproject_structure.png\" width=\"300\" align=\"right\" hspace=\"20\">\n\n-   A single-activity architecture, using the [Navigation component](https:\u002F\u002Fdeveloper.android.com\u002Fguide\u002Fnavigation\u002Fnavigation-getting-started) to manage fragment operations.\n-   [Android architecture components](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Flibraries\u002Farchitecture\u002F), part of Android Jetpack for give to project a robust design, testable and maintainable.\n-   Pattern [Model-View-ViewModel](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FModel%E2%80%93view%E2%80%93viewmodel) (MVVM) facilitating a [separation](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSeparation_of_concerns) of development of the graphical user interface.\n-   [S.O.L.I.D](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSOLID) design principles intended to make software designs more understandable, flexible and maintainable.\n-   [Modular app architecture](https:\u002F\u002Fproandroiddev.com\u002Fbuild-a-modular-android-app-architecture-25342d99de82) allows to be developed features in isolation, independently from other features.\n\n### Modules\n\nModules are collection of source files and build settings that allow you to divide a project into discrete units of functionality. In this case apart from dividing by functionality\u002Fresponsibility, existing the following dependence between them:\n\n\u003Cp align=\"center\">\n \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_communication_modules.png\">\n\u003C\u002Fp>\n\nThe above graph shows the app modularisation:\n-   `:app` depends on `:core` and indirectly depends on `:features` by dynamic-features.\n-   `:features` modules depends on `:commons`, `:core`, `:libraries` and `:app`.\n-   `:core` and `:commons` only depends for possible utils on `:libraries`.\n-   `:libraries` don’t have any dependency.\n\n#### App module\n\nThe `:app` module is an [com.android.application](https:\u002F\u002Fdeveloper.android.com\u002Fstudio\u002Fbuild\u002F), which is needed to create the app bundle.  It is also responsible for initiating the [dependency graph](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fdagger), [play core](https:\u002F\u002Fdeveloper.android.com\u002Freference\u002Fcom\u002Fgoogle\u002Fandroid\u002Fplay\u002Fcore\u002Frelease-notes) and another project global libraries, differentiating especially between different app environments.\n\n\u003Cp align=\"center\">\n \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_dependency_app.png\">\n\u003C\u002Fp>\n\n#### Core module\n\nThe `:core` module is an [com.android.library](https:\u002F\u002Fdeveloper.android.com\u002Fstudio\u002Fprojects\u002Fandroid-library)  for serving network requests or accessing to the database. Providing the data source for the many features that require it.\n\n\u003Cp align=\"center\">\n \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_dependency_core.png\">\n\u003C\u002Fp>\n\n#### Features modules\n\nThe `:features` module are an [com.android.dynamic-feature](https:\u002F\u002Fdeveloper.android.com\u002Fstudio\u002Fprojects\u002Fdynamic-delivery) is essentially a gradle module which can be downloaded independently from the base application module. It can hold code and resources and include dependencies, just like any other gradle module.\n\n| features                                                                                 |\n|:----------------------------------------------------------------------------------------:|\n| \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_dependency_features_home.png\">                |\n| \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_dependency_features_characters_list.png\">     |\n| \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_dependency_features_characters_favorite.png\"> |\n\n#### Commons modules\n\nThe `:commons` modules are an [com.android.library](https:\u002F\u002Fdeveloper.android.com\u002Fstudio\u002Fprojects\u002Fandroid-library) only contains code and resources which are shared between feature modules. Reusing this way resources, layouts, views, and components in the different features modules, without the need to duplicate code.\n\n| ui                                                                     | views                                                                     |\n|:----------------------------------------------------------------------:|:-------------------------------------------------------------------------:|\n| \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_dependency_commons_ui.png\"> | \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_dependency_commons_views.png\"> |\n\n\n#### Libraries modules\n\nThe `:libraries` modules are an [com.android.library](https:\u002F\u002Fdeveloper.android.com\u002Fstudio\u002Fprojects\u002Fandroid-library), basically contains different utilities that can be used by the different modules.\n\n\u003Cp align=\"center\">\n \u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_dependency_libraries_test_utils.png\">\n\u003C\u002Fp>\n\n### Architecture components\n\nIdeally, ViewModels shouldn’t know anything about Android. This improves testability, leak safety and modularity. ViewModels have different scopes than activities or fragments. While a ViewModel is alive and running, an activity can be in any of its lifecycle states. Activities and fragments can be destroyed and created again while the ViewModel is unaware.\n\nPassing a reference of the View (activity or fragment) to the ViewModel is a serious risk. Lets assume the ViewModel requests data from the network and the data comes back some time later. At that moment, the View reference might be destroyed or might be an old activity that is no longer visible, generating a memory leak and, possibly, a crash.\n\n\u003Cimg src=\"screenshots\u002Farchitecture\u002Fdiagram_communication_layers.png\">\n\nThe communication between the different layers follow the above diagram using the reactive paradigm, observing changes on components without need of callbacks avoiding leaks and edge cases related with them.\n\n### Build variants\n\nThe application has different product flavours: `Dev`, `QA`, `Prod`. Each variant has a specific target environment and to make easier to distinguish them the app uses a specific icon colour for `debug` and `release` build variant with descriptive app name. In this case and given that it's a sample, all variants have the same Marvel API endpoint.\nBut the idea is to have different environments target for Development and QA respectively, what doesn't affect the production environment. This is applicable to any tool, platform, service what is being used. For more information about build variant, check this [link](https:\u002F\u002Fdeveloper.android.com\u002Fstudio\u002Fbuild\u002Fbuild-variants).\n\n| Types   | DEV                                                                             | QA                                                                             | PROD                                                                         |\n|---------|:-------------------------------------------------------------------------------:|:------------------------------------------------------------------------------:|:----------------------------------------------------------------------------:|\n| Debug   | \u003Cp>\u003Cimg src=\"app\u002Fsrc\u002Fdebug\u002Fres\u002Fmipmap-xhdpi\u002Fic_launcher.png\">\u003Cbr> MarvelDEV\u003C\u002Fp> | \u003Cp>\u003Cimg src=\"app\u002Fsrc\u002Fdebug\u002Fres\u002Fmipmap-xhdpi\u002Fic_launcher.png\">\u003Cbr> MarvelQA\u003C\u002Fp> | \u003Cp>\u003Cimg src=\"app\u002Fsrc\u002Fdebug\u002Fres\u002Fmipmap-xhdpi\u002Fic_launcher.png\">\u003Cbr> Marvel\u003C\u002Fp> |\n| Release | \u003Cp>\u003Cimg src=\"app\u002Fsrc\u002Fmain\u002Fres\u002Fmipmap-xhdpi\u002Fic_launcher.png\">\u003Cbr> MarvelDEV\u003C\u002Fp>  | \u003Cp>\u003Cimg src=\"app\u002Fsrc\u002Fmain\u002Fres\u002Fmipmap-xhdpi\u002Fic_launcher.png\">\u003Cbr> MarvelQA\u003C\u002Fp>  | \u003Cp>\u003Cimg src=\"app\u002Fsrc\u002Fmain\u002Fres\u002Fmipmap-xhdpi\u002Fic_launcher.png\">\u003Cbr> Marvel\u003C\u002Fp>  |\n\n## Documentation\n\nThe documentation is generated following [KDoc](https:\u002F\u002Fkotlinlang.org\u002Fdocs\u002Freference\u002Fkotlin-doc.html) language (the equivalent of Java's [JavaDoc](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FJavadoc)) via documentation engine for Kotlin [Dokka](https:\u002F\u002Fgithub.com\u002FKotlin\u002Fdokka).\n\nTo consult it check this [link](https:\u002F\u002Fvmadalin.github.io\u002Fandroid-modular-architecture\u002F) or open the project `\u002Fdocs` directory.\n\n## Tech-stack\n\nThis project takes advantage of many popular libraries, plugins and tools of the Android ecosystem. Most of the libraries are in the stable version, unless there is a good reason to use non-stable dependency.\n\n### Dependencies\n\n-   [Jetpack](https:\u002F\u002Fdeveloper.android.com\u002Fjetpack):\n    -   [Android KTX](https:\u002F\u002Fdeveloper.android.com\u002Fkotlin\u002Fktx.html) - provide concise, idiomatic Kotlin to Jetpack and Android platform APIs.\n    -   [AndroidX](https:\u002F\u002Fdeveloper.android.com\u002Fjetpack\u002Fandroidx) - major improvement to the original Android [Support Library](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Flibraries\u002Fsupport-library\u002Findex), which is no longer maintained.\n    -   [Benchmark](https:\u002F\u002Fdeveloper.android.com\u002Fstudio\u002Fprofile\u002Fbenchmark.html) - handles warmup, measures your code performance, and outputs benchmarking results to the Android Studio console.\n    -   [Data Binding](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Flibraries\u002Fdata-binding\u002F) - allows you to bind UI components in your layouts to data sources in your app using a declarative format rather than programmatically.\n    -   [Lifecycle](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Flibraries\u002Farchitecture\u002Flifecycle) - perform actions in response to a change in the lifecycle status of another component, such as activities and fragments.\n    -   [LiveData](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Flibraries\u002Farchitecture\u002Flivedata) - lifecycle-aware, meaning it respects the lifecycle of other app components, such as activities, fragments, or services.\n    -   [Navigation](https:\u002F\u002Fdeveloper.android.com\u002Fguide\u002Fnavigation\u002F) - helps you implement navigation, from simple button clicks to more complex patterns, such as app bars and the navigation drawer.\n    -   [Paging](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Flibraries\u002Farchitecture\u002Fpaging\u002F) - helps you load and display small chunks of data at a time. Loading partial data on demand reduces usage of network bandwidth and system resources.\n    -   [Room](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Flibraries\u002Farchitecture\u002Froom) - persistence library provides an abstraction layer over SQLite to allow for more robust database access while harnessing the full power of SQLite.\n    -   [ViewModel](https:\u002F\u002Fdeveloper.android.com\u002Ftopic\u002Flibraries\u002Farchitecture\u002Fviewmodel) - designed to store and manage UI-related data in a lifecycle conscious way. The ViewModel class allows data to survive configuration changes such as screen rotations.\n-   [Coroutines](https:\u002F\u002Fkotlinlang.org\u002Fdocs\u002Freference\u002Fcoroutines-overview.html) - managing background threads with simplified code and reducing needs for callbacks.\n-   [Dagger2](https:\u002F\u002Fdagger.dev\u002F) - dependency injector for replacement all FactoryFactory classes.\n-   [Retrofit](https:\u002F\u002Fsquare.github.io\u002Fretrofit\u002F) - type-safe HTTP client.\n-   [Coil](https:\u002F\u002Fgithub.com\u002Fcoil-kt\u002Fcoil) - image loading library for Android backed by Kotlin Coroutines.\n-   [Moshi](https:\u002F\u002Fgithub.com\u002Fsquare\u002Fmoshi) - makes it easy to parse JSON into Kotlin objects.\n-   [Timber](https:\u002F\u002Fgithub.com\u002FJakeWharton\u002Ftimber) - a logger with a small, extensible API which provides utility on top of Android's normal Log class.\n-   [Stetho](http:\u002F\u002Ffacebook.github.io\u002Fstetho\u002F) - debug bridge for applications via Chrome Developer Tools.\n-   [and more...](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Fblob\u002Fmaster\u002FbuildSrc\u002Fsrc\u002Fmain\u002Fkotlin\u002Fdependencies\u002FDependencies.kt)\n\n### Test dependencies\n\n-   [UIAutomator](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Ftesting\u002Fui-automator) - a UI testing framework suitable for cross-app functional UI testing across system and installed apps.\n-   [Espresso](https:\u002F\u002Fdeveloper.android.com\u002Ftraining\u002Ftesting\u002Fespresso) - to write concise, beautiful, and reliable Android UI tests\n-   [Robolectric](https:\u002F\u002Fgithub.com\u002Frobolectric\u002Frobolectric) - industry-standard unit testing framework for Android.\n-   [JUnit](https:\u002F\u002Fgithub.com\u002Fjunit-team\u002Fjunit4) - a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks.\n-   [Mockk](https:\u002F\u002Fgithub.com\u002Fmockk\u002Fmockk) - provides DSL to mock behavior. Built from zero to fit Kotlin language.\n-   [AndroidX](https:\u002F\u002Fgithub.com\u002Fandroid\u002Fandroid-test) - the androidx test library provides an extensive framework for testing Android apps.\n-   [and more...](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Fblob\u002Fmaster\u002FbuildSrc\u002Fsrc\u002Fmain\u002Fkotlin\u002Fdependencies\u002FTestDependencies.kt)\n\n### Plugins\n\n-   [Ktlint](https:\u002F\u002Fgithub.com\u002Fpinterest\u002Fktlint) - an anti-bikeshedding Kotlin linter with built-in formatter.\n-   [Detekt](https:\u002F\u002Fgithub.com\u002Farturbosch\u002Fdetekt) - a static code analysis tool for the Kotlin programming language.\n-   [Spotless](https:\u002F\u002Fgithub.com\u002Fdiffplug\u002Fspotless) - a code formatter can do more than just find formatting errors.\n-   [Versions](https:\u002F\u002Fgithub.com\u002Fben-manes\u002Fgradle-versions-plugin) - make easy to determine which dependencies have updates.\n-   [SafeArgs](https:\u002F\u002Fdeveloper.android.com\u002Fguide\u002Fnavigation\u002Fnavigation-pass-data#Safe-args) - generates simple object and builder classes for type-safe navigation and access to any associated arguments.\n-   [Jacoco](https:\u002F\u002Fgithub.com\u002Fjacoco\u002Fjacoco) - code coverage library\n-   [and more...](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Fblob\u002Fmaster\u002FbuildSrc\u002Fbuild-dependencies.gradle.kts)\n\n## Resources\n\n### Projects\n\nThis is project is a sample, to inspire you and should handle most of the common cases, but obviously not all. If you need to take a look at additional resources to find solutions for your project, visit these interesting projects:\n\n-   [iosched](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fiosched) (by [google](https:\u002F\u002Fgithub.com\u002Fgoogle)) - official Android application from google IO 2019.\n-   [plaid](https:\u002F\u002Fgithub.com\u002Fandroid\u002Fplaid) (by [android](https:\u002F\u002Fgithub.com\u002Fandroid)) - app which provides design news & inspiration, being an example of implementing material design.\n-   [sunflower](https:\u002F\u002Fgithub.com\u002Fandroid\u002Fsunflower) (by [android](https:\u002F\u002Fgithub.com\u002Fandroid)) - a gardening app illustrating Android development best practices with Android Jetpack.\n-   [architecture-components-samples](https:\u002F\u002Fgithub.com\u002Fandroid\u002Farchitecture-components-samples) (by [android](https:\u002F\u002Fgithub.com\u002Fandroid)) - collection of samples for Android Architecture Components.\n-   [architecture-sample](https:\u002F\u002Fgithub.com\u002Fandroid\u002Farchitecture-samples) (by [android](https:\u002F\u002Fgithub.com\u002Fandroid)) - collection of samples to discuss and showcase different architectural tools and patterns for Android apps.\n-   [android-clean-architecture-boilerplate](https:\u002F\u002Fgithub.com\u002Fbufferapp\u002Fandroid-clean-architecture-boilerplate) (by [bufferapp](https:\u002F\u002Fgithub.com\u002Fbufferapp)) - an android boilerplate project using clean architecture\n-   [android-kotlin-clean-architecture](https:\u002F\u002Fgithub.com\u002Fsanogueralorenzo\u002FAndroid-Kotlin-Clean-Architecture) (by [sanogueralorenzo](https:\u002F\u002Fgithub.com\u002Fsanogueralorenzo)) - android sample Clean Architecture app written in Kotlin.\n-   [modularization-example](https:\u002F\u002Fgithub.com\u002FJeroenMols\u002FModularizationExample) (by [JeroenMols](https:\u002F\u002Fgithub.com\u002FJeroenMols)) - easy to understand real-life example of a modularized Android app.\n-   [lego-catalog](https:\u002F\u002Fgithub.com\u002FEli-Fox\u002FLEGO-Catalog) (by [Eli-Fox](https:\u002F\u002Fgithub.com\u002FEli-Fox)) - app illustrating current Android Architecture state using Android development best practices.\n-   [tivi](https:\u002F\u002Fgithub.com\u002Fchrisbanes\u002Ftivi) (by [chrisbanes](https:\u002F\u002Fgithub.com\u002Fchrisbanes)) - an app which attempts to use the latest cutting edge libraries and tools.\n-   [android-showcase](https:\u002F\u002Fgithub.com\u002Figorwojda\u002Fandroid-showcase) (by [igorwojda](https:\u002F\u002Fgithub.com\u002Figorwojda)) - app following best practices: Kotlin, coroutines, Clean Architecture, feature modules, tests, MVVM, static analysis.\n\n### Articles\n\nA collection of very interesting articles related last android community tendencies and recommendations for start to take in consideration for your current\u002Fnext project:\n\n-   [Transform monolith to modularization application](https:\u002F\u002Fmedium.com\u002Fandroiddevelopers\u002Fa-patchwork-plaid-monolith-to-modularized-app-60235d9f212e)\n-   [Using the Navigation Component in a Modular World](https:\u002F\u002Fmedium.com\u002Fswlh\u002Fusing-the-navigation-component-in-a-modular-world-e7578825962)\n-   [Dependency injection in a multi module project](https:\u002F\u002Fmedium.com\u002Fandroiddevelopers\u002Fdependency-injection-in-a-multi-module-project-1a09511c14b7)\n-   [ViewModels and LiveData: Patterns + AntiPatterns](https:\u002F\u002Fmedium.com\u002Fandroiddevelopers\u002Fviewmodels-and-livedata-patterns-antipatterns-21efaef74a54)\n-   [Dynamic feature and regular modules using Dagger2](https:\u002F\u002Fblog.q42.nl\u002Fdynamic-feature-and-regular-modules-using-dagger2-12a7edcec1ff)\n-   [Android Architecture starring Kotlin Coroutines, Jetpack (MVVM, Room, Paging), Retrofit and Dagger 2](https:\u002F\u002Fproandroiddev.com\u002Fandroid-architecture-starring-kotlin-coroutines-jetpack-mvvm-room-paging-retrofit-and-dagger-7749b2bae5f7)\n-   [Official Kotlin Style Guide with Ktlint](https:\u002F\u002Fproandroiddev.com\u002Fofficial-kotlin-style-guide-with-ktlint-4a649c172956)\n-   [Gradle dependency management with Kotlin (buildSrc)](https:\u002F\u002Fproandroiddev.com\u002Fgradle-dependency-management-with-kotlin-94eed4df9a28)\n-   [Detecting Kotlin Code Smells with Detekt](https:\u002F\u002Fproandroiddev.com\u002Fdetecting-kotlin-code-smells-with-detekt-e79c52a35faf)\n-   [Best coding practices, tips and more for Android](https:\u002F\u002Fmedium.com\u002Fmindorks\u002Fbest-coding-practices-tips-and-more-for-android-4ec03c7eeb2c)\n\n### Libraries\n\nThe open-source community create and maintains tons of awesome libraries making your job more easy, giving the opportunity to use them in your developments. Here are a very important collection of them:\n\n-   [awesome-android-ui](https:\u002F\u002Fgithub.com\u002Fwasabeef\u002Fawesome-android-ui) - collection list of awesome Android UI\u002FUX libraries.\n-   [awesome-android-libraries](https:\u002F\u002Fgithub.com\u002FKotlinBy\u002Fawesome-kotlin#android-libraries) - collection of awesome Kotlin related stuff.\n-   [android-arsenal](https:\u002F\u002Fandroid-arsenal.com\u002F) - android developer portal with tools, libraries, and apps.\n\n### Best practices\n\nAvoid reinventing the wheel by following these guidelines:\n\n-   [Google best practices](https:\u002F\u002Fdeveloper.android.com\u002Fdistribute\u002Fbest-practices)\n-   [Android development best practices](https:\u002F\u002Fgithub.com\u002Ffuturice\u002Fandroid-best-practices)\n\n### Codelabs\n\nGoogle Developers Codelabs provide a guided, tutorial, hands-on coding experience. Most codelabs will step you through the process of building a small application, or adding a new feature to an existing application. They cover a wide range of android concepts to learn and practice:\n\n-   [Android Developer Fundamentals](https:\u002F\u002Fdeveloper.android.com\u002Fcourses\u002Ffundamentals-training\u002Ftoc-v2)\n-   [Android Developer Codelabs](https:\u002F\u002Fcodelabs.developers.google.com\u002F?cat=Android)\n\n## Contributions\n\nAll contributions are welcome!\nPlease feel free to post questions, recommendations, ideas, bugs by create [new issue](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Fissues\u002Fnew) following the template or if you want create directly [new pull request](https:\u002F\u002Fgithub.com\u002FVMadalin\u002Fkotlin-sample-app\u002Fcompare).\n\n## Authors\n\n\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002FMValceleanu\" target=\"_blank\">\n  \u003Cimg src=\"https:\u002F\u002Favatars0.githubusercontent.com\u002Fu\u002F18151158?s=400&u=bd6e5ddff1df0d632b93855da0300410854b806e&v=4\" width=\"70\" align=\"left\">\n\u003C\u002Fa>\n\n**Madalin Valceleanu**\n\n[![Linkedin](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002F-linkedin-grey?logo=linkedin)](https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fvmadalin\u002F)\n[![Twitter](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002F-twitter-grey?logo=twitter)](https:\u002F\u002Ftwitter.com\u002FMValceleanu)\n[![Medium](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002F-medium-grey?logo=medium)](https:\u002F\u002Fmedium.com\u002F@vmadalin)\n[![Web](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002F-web-grey?logo=appveyor)](http:\u002F\u002Fvmadalin.com\u002F)\n\n## License\n\n```license\nCopyright 2019-2020 vmadalin.com\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n    http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n```\n","该项目是一个采用模块化架构设计的Android示例应用，旨在展示如何使用Kotlin和最新的技术栈构建可扩展、可测试且易于维护的应用程序。其核心功能包括遵循SOLID原则的干净架构实现、Jetpack组件的集成以及动态特性支持，强调了代码质量和项目结构的最佳实践。特别适合于需要长期维护和支持大型团队协作开发的复杂Android应用程序场景。通过提供详尽的设计文档和技术指南，此项目为开发者们搭建了一个坚实的基础，帮助他们更好地理解和应用现代Android开发理念。","2026-06-11 03:12:36","top_language"]