Compose-BreakingBad - GitLite

KO | EN

gitlite — search

#javascript #hacktoberfest #typescript #llm #android #rust #linux #docker #macos #nodejs #java #windows #security #open-source

Compose-BreakingBad

(★ 101)

☢️ 🧪 ☠️ Jetpack Compose - Breaking Bad

파일 탐색기

최종 버전 다운로드 (.zip)

- - CD.yaml
  - CI.yaml
- ci-gradle.properties
- spotlessApply.run.xml
- .gitignore
- build.gradle.kts
- proguard-rules.pro
- - build.gradle.kts
- settings.gradle.kts
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
  - consumer-rules.pro
  - proguard-rules.pro
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
  - consumer-rules.pro
- - .gitignore
  - build.gradle.kts
  - consumer-rules.pro
  - proguard-rules.pro
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
- - build.gradle.kts
- - .gitignore
  - build.gradle.kts
- - .gitignore
  - build.gradle.kts
- 0.gif
- 1.gif
- 2.gif
- - gradle-wrapper.jar
  - gradle-wrapper.properties
- init.gradle.kts
- libs.versions.toml
- projectDependencyGraph.gradle
- checksum.sh
- copyright.kt
.editorconfig
.gitignore
build.gradle.kts
debug.keystore
gradle.properties
gradlew
gradlew.bat
LICENSE
project.dot.png
README.md
settings.gradle.kts

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<h1 align="center"> 🧪 Breaking Bad - Jetpack Compose</h1>

<p align="center">
  <a href='https://developer.android.com'><img src='http://img.shields.io/badge/platform-android-green.svg'/></a>
  <a href="https://kotlinlang.org/docs/whatsnew1920.html"><img src = "https://shields.io/badge/kotlin-2.0.20-blue" /></a>
  <a href="https://developer.android.com/jetpack/compose/bom"><img src = "https://img.shields.io/badge/jetpack%20compose-2024.09.00-brightgreen" /></a>
  <a href="https://opensource.org/licenses/Apache-2.0"><img src="https://img.shields.io/badge/license-Apache%202.0-blue.svg"/></a>
</p>

<p align="center">
  <img src="/gif/0.gif" width="32%"/>
  <img src="/gif/1.gif" width="32%"/>
  <img src="/gif/2.gif" width="32%"/>
</p>

## Tech Stack

- [Jetpack](https://developer.android.com/jetpack)
  - Compose - Define your UI programmatically with composable functions that describe its shape
    and data dependencies.
  - Hilt - Extend the functionality of Dagger Hilt to enable dependency injection.
  - Lifecycle - Build lifecycle-aware components that can adjust behavior based on the current
    lifecycle state
  - Room - Create, store, and manage persistent data backed by a SQLite database.
  - ViewModel - Store and manage UI-related data in a lifecycle conscious.
  - App Startup - initialize components at app startup.
- Clean Architecture (multi module)
- MVVM pattern
- Kotlin
  - Coroutines
  - Flows
  - Serialization
- [Type Safety Navigation](https://developer.android.com/guide/navigation/design/type-safety)
- Material Design 3
  - [Material Theme Builder](https://material-foundation.github.io/material-theme-builder/)
- Single Activity
- StaggeredVerticalGrid
- [Gradle Version Catalog](https://docs.gradle.org/7.4/userguide/platforms.html)
- [Retrofit2](https://github.com/square/retrofit)
- [Coil-Compose](https://coil-kt.github.io/coil/compose)
- [Timber](https://github.com/JakeWharton/timber)
- [Haze](https://github.com/chrisbanes/haze)
- [SharedElement](https://developer.android.com/guide/fragments/animate#shared)
- [Kover](https://github.com/Kotlin/kotlinx-kover)

## Multi Module

```
├── app
├── core
│   ├── common
│   ├── data
│   ├── database
│   ├── datastore
│   ├── designsystem
│   ├── domain
│   ├── model
│   └── network
└── feature
    ├── bottombar
    ├── detail
    ├── favorite
    ├── list
    ├── main
    └── setting
```

The file structure is similar to Now in Android, but to follow Clean Architecture, the domain layer
does not reference the data layer.

## Nested NavHosts

```mermaid
graph TD
    A[Main NavHost] --> B[BottomBar]
    A --> C[Detail]
    B --> D[Bottom NavHost]
    D --> E[List]
    D --> F[Favorite]
    D --> G[Setting]
```

Even though using nested NavHosts makes things more complex, this approach was chosen to achieve screen transition animations similar to those between Activities.

(One NavHost needs to manage how to hide the bottom navigation and apply animations during screen transitions.)

# Module Graphs

![](https://raw.githubusercontent.com/shinhyo/Compose-BreakingBad/develop/project.dot.png)