"something else" -> "web browsing" -> back is handled by the application wrapping the Safari web browser using the included browser control in the API.
Good point. I was just doing an inversion in the example to simplify the argument mechanics a bit.
But doesn't that wrapping rely on something else's developers realizing that the user might want to go off to the browser and back? What if it wasn't Safari in the middle but any one (or three) of the numerous other programs the user might want to take a side trip through. It gets back to the crap shoot of trying to guess every multi-application use case that will be wanted. All this to defend not putting together the general solution which is entirely doable to begin with.
