Isaac Udy

Can you provide some more information on what you're thinking could be done here?

I've done something like this in the past, providing unique ids for each Route/Fragment pair, storing the Route in memory, and using the Storage object to retrieve from memory. In...

> I did not understand why this solution would require us to save the routes to disk? Mainly because of onSavedInstanceState. See below: > Do you know whether or not...

I do agree with you there @Zhuinden - I'm certainly not suggesting that what we were doing at my workplace was good architecture at all. I just find that it's...

I've just spent some time looking at this, and I've got a proof-of-concept, but I'm no longer sure this is a good idea. I've spent some time looking at the...

@Zhuinden I agree

Ah yes, number 3 tricked me too! The clarification on the architecture was useful, I was obviously misunderstanding things a little bit. What would you think if we made `route...

You make a good point with the `(List) -> List` idea - this is very flexible, and very functional. I do like this as a concept. Currently the syntax used...

>Maybe removing the infix is enough? I think this is a good idea, but I think that we should also consider changing the signature of the invoke function - currently...

Hi! This is a great issue, thanks for raising it. Flows, and this kind of navigation, are something I've thought about before. Unfortunately, I didn't come to any super clear...