ovseychik / playlistmaker

Playlist Maker app. Course project at Yandex Practicum

PlaylistMaker

Playlist Maker app. Course project at Yandex Practicum

Stack

• Language: Kotlin
• Architecture pattern: MVVM
• Network: Retrofit, Glide
• DI: Koin
• Ui: native Linear / Relative / Constraint Layout
• Local storage: Shared Preferences, Jetpack Room

Requirements

• Java 17
• Android min SDK 26 (Android 8)

How to build

1. Clone the repository to Android Studio either by downloading project archive or cloning via VCS tool built into IDE.
2. Wait for the project to index.
3. Build and run on an emulator or your physical device.

Screenshots

playlistmaker's Issues

Split library package into two features

.library package now has two separate features: working with favorite tracks and with playlists.
It would be better to split them in two.

Remove dependencies from UI layer in the Domain layer

For example:

https://github.com/ovseychik/PlaylistMaker/blob/dev/app/src/main/java/com/example/playlistmaker/library/domain/impl/PlaylistsInteractorImpl.kt#L7

import com.example.playlistmaker.library.ui.PlaylistDetailsScreenState

class PlaylistsInteractorImpl(private val playlistsRepository: PlaylistsRepository) :
    PlaylistsInteractor {
    override fun getTracksFromPlaylistByIds(trackIds: List<String>): Flow<PlaylistDetailsScreenState> {
        return playlistsRepository.getTracksFromPlaylistByIds(trackIds).map { tracks ->
            if (tracks.isNotEmpty()) {
                var durationTimeSum: Long = 0
                for (track in tracks) {
                    durationTimeSum += (track.trackTimeMillis ?: 0)
                }
                val duration = Duration.ofMillis(durationTimeSum)
                val minutes = duration.toMinutes()
                PlaylistDetailsScreenState.WithTracks(tracks.asReversed(), minutes)
            } else {
                PlaylistDetailsScreenState.NoTracks
            }
        }

    }
}

Split di package on a feature-basis

Currently, there's a single di package. It would be easier to maintain it, if it were split on a feature basis.