I think there is current a fundamental problem in rabbit os, it seems as if there is no uniform substructure for the current application options that can manage the ongoing processes correctly.
It currently seems as if different things are being implemented that are able to fulfil their main task, at least in a single specific application scenario, but not in conjunction with the other options offered by the rest of the system and the other application options.
One eexample for that I often use is Suno, where you can see the problem quite clearly.
The main functionality works, at least most of the time, without any problems (sometimes the song generation is interrupted in the middle, but most of the time it works, but that’s not the problem I’m talking about). What I mean is, if the main-screen then opens or you want to change the volume during Suno playback, then it’s no longer possible to return to Suno playback, for example, and if you then generate a new song, the application will open again, but it’s not the new Suno song that’s displayed in the application, but the old song.
However, if you use Spotify or the Timer, you can always go back to that application as long as the corresponding rabbit is still running.
What I’m trying to say is that there is currently clearly not enough management for running applications, and that will continue to cause problems as long as this problem exists.
It currently seems as if people are trying to eliminate requirements from an object-oriented world with solutions from a script-based world.
Therefore, I think it is absolutely important to first implement the necessary basics for managing running applications (rabbits) before implementing other great application possibilities that may run in one use case, but are not compatible with the other functions of the system without causing problems.