You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main problem here is to decide how it should work.
A standalone player.
It opens an independent Sweyer instance in a separate activity, with a separate audio_service and player. The main app still could be launched and interfere with the playback of a standalone one.
I already experimented with a UI for this feature, which I kept unifinished under a StandalonePlayer class.
The main app is launched and a file from Intent is fed into the main player.
This breaks the paradigm of accesing all the content through the MediaStore.
In its turn, this leads to the uncertainty of what we should do with the queue, as a major problem, but certainly not limited.
But this example poses a deeper thought of how we should handle a case with different song sources in the future.
It's very likely this could happen.
For example, if the app becomes a Spotfiy/YT music/whatever else client.
Should the queue be united and allow multiple sources of songs?
Should it fundamentally allow only one source in it?
Something else?
Answering these questions should be done very carefully, since this is a major architechtural decision and could inflict very big problems down the road, if not done right.
For example YT music doesn't allow you mixing local and non-local songs.
The text was updated successfully, but these errors were encountered:
Suggestion
The main problem here is to decide how it should work.
It opens an independent Sweyer instance in a separate activity, with a separate
audio_service
and player. The main app still could be launched and interfere with the playback of a standalone one.I already experimented with a UI for this feature, which I kept unifinished under a
StandalonePlayer
class.This breaks the paradigm of accesing all the content through the MediaStore.
In its turn, this leads to the uncertainty of what we should do with the queue, as a major problem, but certainly not limited.
But this example poses a deeper thought of how we should handle a case with different song sources in the future.
It's very likely this could happen.
For example, if the app becomes a Spotfiy/YT music/whatever else client.
Should the queue be united and allow multiple sources of songs?
Should it fundamentally allow only one source in it?
Something else?
Answering these questions should be done very carefully, since this is a major architechtural decision and could inflict very big problems down the road, if not done right.
For example YT music doesn't allow you mixing local and non-local songs.
The text was updated successfully, but these errors were encountered: