Dependency Diagram

%%{
  init: {
    'theme': 'dark'
  }
}%%

graph TB
  :core:navigation -- api --> :core:data
  :core:network -- api --> :core:api
  :core:api-compose -- api --> :core:api
  :core:api -- api --> :core:data
  :feature:splash-screen -- api --> :core:navigation
  :feature:splash-screen -- implementation --> :core:api-compose
  :core:local -- api --> :core:api
  :core:ui -- api --> :core:data
  :core:ui -- api --> :core:design-system
  :feature:cv-content -- api --> :core:navigation
  :feature:cv-content -- implementation --> :core:api-compose
  :feature:cv-content -- implementation --> :core:ui
  :app -- implementation --> :core:api-compose
  :app -- implementation --> :core:ui
  :app -- implementation --> :core:model
  :app -- implementation --> :core:local
  :app -- implementation --> :core:network
  :app -- implementation --> :feature:splash-screen
  :app -- implementation --> :feature:cv-content
  :app -- implementation --> :feature:easter-eggs:gym
  :core:model -- api --> :core:api
  :feature:easter-eggs:gym -- api --> :core:navigation
  :feature:easter-eggs:gym -- implementation --> :core:api-compose
  :feature:easter-eggs:gym -- implementation --> :core:ui

classDef android-library fill:#3BD482,stroke:#fff,stroke-width:2px,color:#fff;
classDef android-application fill:#2C4162,stroke:#fff,stroke-width:2px,color:#fff;
class :core:navigation android-library
class :core:data android-library
class :core:network android-library
class :core:api android-library
class :core:api-compose android-library
class :feature:splash-screen android-library
class :core:local android-library
class :core:ui android-library
class :core:design-system android-library
class :feature:cv-content android-library
class :app android-application
class :core:model android-library
class :feature:easter-eggs:gym android-library

Loading

Preface

This project is greatly over-complicated on purpose. I wanted to show that I now how to:

• modularize app
• use advanced Gradle features likes:
  • precompiled convention plugins
  • precompiled binary plugins (:gradle:versioning-plugin)
  • included builds:
    • :backend project in ktor is in the same repository
    • :shared:data-model tiny module hosting DTO object for both this ktor backend and android app written in kotlin multiplatform
    • :build-logic aka slightly better buildSrc
    • :deployment where I use my own open source Gradle plugin gradle-ssh for very simple deployment of the backend. I encourage to also look at this project
  • configure gradle in a way that both build and configuration cache works
  • enable remote build cache (even when launching this project first time the build should be quicker thanks to this)
• use dependency injection pattern by not using any frameworks for it
• use resource local and external to app (that is the reason why some data is just hardcoded in app and for small things like languages there is ktor backend)
• how to work with jenkins (look at .jenkins folder) in docker and docker agents for which I created my own image encapsulating whole environment needed to build app. In theory this image can be used as a base for .devcontainer or some other cloud based dev environment to start delivering for this app in matter of seconds on any machine, although Intellij/Android Studio still has very bare bone devcontainer support so I haven't done it yet.

And most important aspect: just to have fun developing it.