Offline-Music-App

KO | EN

gitlite — search

#javascript #python #typescript #golang #android #linux #docker #nodejs #java #windows #awesome #cli #pytorch #mcp

Offline-Music-App

(★ 11)

A fully offline, modern, modularized music player app built with Kotlin and Jetpack Compose. This project demonstrates clean architecture, feature-based modularization, and modern Android development best practices.

Offline-Music-App Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Music - Modern Offline Audio Player

![Android](https://img.shields.io/badge/Android-3DDC84?style=for-the-badge&logo=android&logoColor=white)
![Kotlin](https://img.shields.io/badge/Kotlin-7F52FF?style=for-the-badge&logo=kotlin&logoColor=white)
![Jetpack Compose](https://img.shields.io/badge/Jetpack%20Compose-4285F4?style=for-the-badge&logo=jetpackcompose&logoColor=white)
![Hilt](https://img.shields.io/badge/Hilt-Dependency%20Injection-orange?style=for-the-badge&logo=google&logoColor=white)
![Media3](https://img.shields.io/badge/Media3-ExoPlayer-red?style=for-the-badge&logo=googleplay&logoColor=white)
![Clean Architecture](https://img.shields.io/badge/Clean-Architecture-blueviolet?style=for-the-badge)

<br />

## Test APK
A test APK is available for download via the GitHub Releases section.
👉 You can find the latest build under **Releases** on this repository to try out the app without building it locally.

**Music** is a fully offline, modern, modularized music player built with **Kotlin** and **Jetpack Compose**.

Designed with **Clean Architecture** principles, it features a robust audio engine powered by **Media3 (ExoPlayer)**, seamless modular navigation, and advanced features like audio trimming and tag editing. This project serves as a showcase for modern Android development best practices.

---

---

---

---

## Project Overview

Music is an offline-first music player focused on a clean, modular architecture. It showcases:

* Feature-first modularization (each feature lives in its own Gradle module).
* Clean Architecture (data, domain, presentation layers per feature).
* Modern Android libraries: Jetpack Compose, Hilt, Media3 (ExoPlayer successor), Room, DataStore, KSP.
* Offline media scanning and playback with Media3 + local metadata handling.

---

## Modules

The project uses Gradle modularization. Key modules included in `settings.gradle.kts`:

```kotlin
rootProject.name = "MusicPlayer"
include(":app")
include(":core")

// Feature modules are organized under the 'features' directory
include(":features:library")
include(":features:player")
include(":features:playlist")
include(":features:settings")
include(":features:trim")
include(":features:edit")
include(":features:dj_mix")
```

---

## Key Dependencies

The project uses a centralized version catalog. Selected versions used in the project:

* Kotlin
* Android Gradle Plugin (AGP)
* Jetpack Compose BOM
* Hilt
* Media3
* Room
* Coroutines
* Coil
* KSP
* accompanist-systemuicontroller

Refer to the `libs.versions.toml` for the full catalog.

---

## Architecture Decisions

### Clean Architecture (feature-first)

* Each feature module (`:features:player`, `:features:library`, etc.) contains `data`, `domain`, and `presentation` packages to enforce separation of concerns.
* `core` module holds cross-cutting concerns (DI setup, common models, utilities, theme, and UI components).

### Dependency Injection

* Hilt is used for DI across modules. Modules expose bindings through interfaces and rely on `@Module` + `@InstallIn` in `core`/feature modules.

### Media Playback

* Media3 (the modern successor to ExoPlayer) is used for playback and session management. Playback logic is isolated in the `:features:player` module with use-cases in `domain`.

### Persistence & Settings

* Room stores user playlists and cached metadata.
* DataStore (preferences) stores persistent settings (theme, playback preferences).

### Build & Compiler Tooling

* KSP is used for code generation where needed (e.g., Room, other annotation processors) — ensure KSP version is compatible with the Kotlin version.

---

## Folder Layout (feature-first example)

```kotlin
app/
core/
 ├─ di/
 ├─ ui/
 └─ utils/
features/
 ├─ library/
 │   ├─ data/
 │   ├─ domain/
 │   └─ presentation/
 ├─ player/
 │   ├─ data/
 │   ├─ domain/
 │   └─ presentation/
 ├─ playlist/
 ├─ settings/
 ├─ edit/
 ├─ dj_mix/
 └─ trim/
```

Each feature follows the same `data/domain/presentation` pattern. Keeping public interfaces in `domain` and implementation details in `data`.

Offline-Music-App

Offline-Music-App Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Offline-Music-App

Offline-Music-App Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README