There's a great function from the web that I want to reproduce in iOS and Android. I'm calling it a recursive tableview because I can't think of any other descriptive name.
For example, in a shopping app, you go into "cars", then "hatchbacks", then pick one from the list, say "SX4". When viewing the details of SX4, I want to show recommendations of other cars they might be interested in, so at the bottom I add "Cobalt" and "Volt". Tapping on Cobalt pushes a new view, adding to the hierarchy. The Cobalt view also has recommendations, like "Volt", and tapping on Volt pushes another view. And so on... infinitely. Eventually the app will die because of memory, because both iOS and Android automatically store the hierarchy to allow the back button functionality that we're all used to.
I'm curious if anyone has come up with a clever way to solve this interface problem. Memory problems aside, when users want to get back to the category list (hatchbacks), they have to tap the back button dozens of times to pop up the hierarchy. Not a great user experience.
The only "solution" I've come up with is to change the behaviour of the back button; tapping the back button brings you back to the category list (hatchbacks), essentially short-circuiting the hierarchy and not storing the moves down the hierarchy.