feat: rotate picks and add an all-new action
- mood settings gain a replacement threshold slider (default 3 plays, 0 never), sent with create and update requests - All new on the mood page calls POST /recommendations/rotate and refills the list with different tracks; Refresh keeps its top-up behaviour - show the rotation threshold, playCount-aware models and busy state, and refresh the selected mood from the rotate response - version 0.5.0
This commit is contained in:
1 parent
e6c1dae3c3
commit
9464ba53d0
10 files changed
+192
-18
No files matched your search
@@ -32,6 +32,10 @@ a server-driven radio session and songs are added from Deezer or YouTube Music.
|
||||
- Add to mood;
|
||||
- Not interested (permanent for the mood);
|
||||
- Retry for failed downloads.
|
||||
A pick is replaced automatically after `recommendationRotationPlays` plays
|
||||
(default 3, configurable per mood), and **All new** on the mood page swaps the
|
||||
whole list at once. **Refresh** only discovers and tops up empty slots, which
|
||||
is why it usually kept the same songs.
|
||||
- **Radio** mixes the collection and ready recommendations using the mood's
|
||||
`collectionPercent`. The app keeps a small queue and asks for more from the
|
||||
same mood session.
|
||||
@@ -58,8 +62,9 @@ a server-driven radio session and songs are added from Deezer or YouTube Music.
|
||||
- **Scrubbing**: the progress slider can be dragged on every platform. Android and
|
||||
web seek natively; desktop restarts the decoder at the requested position.
|
||||
- **Mood settings** live on their own screen: name, description, discovery hint,
|
||||
genres, source, collection share, recommendations, refresh interval, a
|
||||
**Keep this mood offline** switch, and Delete at the bottom.
|
||||
genres, source, collection share, recommendation count and replacement
|
||||
threshold, refresh interval, a **Keep this mood offline** switch, and Delete
|
||||
at the bottom.
|
||||
- **Downloads** screen for device-side copies: play, delete, clear, storage
|
||||
usage.
|
||||
- **Diagnostics**: warnings, errors and crashes are kept in a 500-entry local
|
||||
@@ -212,7 +217,7 @@ Tagged builds (`v*`) publish to internal testing from CI. The Gitea secrets are:
|
||||
| `ANDROID_KEY_PASSWORD` | key password |
|
||||
| `PLAY_SERVICE_ACCOUNT_JSON` | contents of the service account JSON |
|
||||
|
||||
Then `git tag v0.4.3 && git push --tags` builds, signs and uploads the bundle.
|
||||
Then `git tag v0.5.0 && git push --tags` builds, signs and uploads the bundle.
|
||||
Gradle Play Publisher asks Play for the next free `versionCode`
|
||||
(`ResolutionStrategy.AUTO`), so only the tag/version name needs to change.
|
||||
|
||||
|
||||
Reference in new issue
Block a user