billotp/polify

A cross platform S3 buckets music streaming app 🪣 🎶 📡

polify's Issues

Allow for a full offline usage

Current

• A signed url with 7 days validity is issued when a song is played
• It is then saved in embedded db and reused when song is played again

Issue(s)

• If the song is requested after signed url expiration, a network error will be raised preventing the song to be played again
• For offline use, a "download song in local device" feature is implemented but its mixed with id3 tag parsing feature; as such, its usage is confusing.

Suggestion(s)

Basic

• Separate the "download song in local device" and "parse id3 tags" features
• Add a manual toggle for offline mode to present only locally available songs
• Trigger the above toggle automatically when no internet connection is available at app startup

Elaborate

• Compress the downloaded songs with an efficient codec to save space on device

Add MPRIS - DBus linux media control

Current

Nothing done 🏄

Issue

Cannot play/pause , skip etc from an outside controller on linux

Suggestion(s)

Basic

• Use mpris_service with dbus

Elaborate

• Custom implementation ?

New cloud storage bucket in-app connection

Current

To load a bucket in app, edit dotenv file and build the app with the embedded (obfuscated) credentials.

Issue

Nobody wants to be forced to re-build the app to use it with its own bucket(s)

Suggestion(s)

Basic

• Add a dedicated form when app is first started to input s3 access credentials

Elaborate

• Use a kind of OAuth sign-in method to authorize the app to read user buckets

Add / Improve artists, albums and song metadatas

Current

Some kind of ID3 tag parsing is implemented and print a song artist, album and cover picture informations on a "snackbar" after a click on a button next to a song list item.

Issue

This feature is mixed with "download song" one and nothing is saved regarding the parsed metadata's.

Metadatas are extracted based on s3 scaffolding (see README ), as such its not consistent and album artworks are only available in each song id3 tag if any.

Suggestion(s)

Basic

• Separate the "read id3tag" feature from the "download song" one
• Save parsed metadatas

Elaborate

WIP

Add app build and distribution pipelines (CI /CD)

Current

Build and installation on a linux or android device is done locally via flutter build and install commands.

Issue

No one will use this app 😞

Suggestion(s)

Basic

• Add a test then build github ci yaml file for android and linux
• Create a release artifact on new tag via github ci
• Add a static website to present and distribute application from github releases

Elaborate

• Use a "specialized" CI saas like circle CI to add auto screenshots, code signing ...
• Add automatic F-Droid upload