That's ONE intent, and not even between two apps...
Have you ever had to pipe more than two applications to operate on something (image, video, whatever)? Or actually, more than one, since in your solution one app is am, or your intent-calling app?
> Re the “killing stuff” paragraph sounds like a memory size issue
Whatever it is, how about asking what to do, instead of assuming that users only care about the foreground app? (I risk smashing my monitor every time I read that in the documentation)
> And this model works exceedingly well, you just don’t even notice it
Nope, I notice it all the time, since apps are more likely to get killed than let to gracefully stop, in my experience.
I heard that the latest Samsung One UI versions behave better, though
Have you ever had to pipe more than two applications to operate on something (image, video, whatever)? Or actually, more than one, since in your solution one app is am, or your intent-calling app?
> Re the “killing stuff” paragraph sounds like a memory size issue
Whatever it is, how about asking what to do, instead of assuming that users only care about the foreground app? (I risk smashing my monitor every time I read that in the documentation)
> And this model works exceedingly well, you just don’t even notice it
Nope, I notice it all the time, since apps are more likely to get killed than let to gracefully stop, in my experience.
I heard that the latest Samsung One UI versions behave better, though