You may want to look at the ViewStack class. If the states' stuff isn't superficial, they can become unwieldy VERY quickly.
a (high level) discussion of how to make this conversion would be immensely helpful. I've inherited the maintenance of an app that has six view states and a huge switch statement that handles the display.
What you want is something we call “multi-dimensional states”. We’ve looked into providing support for it in the SDK, but haven’t had the time and resources to implement it. One of the tricky aspects of it has to do with handling conflicts. Another is how you would specify transitions.
I don’t know if there is a recommended implementation for “multi-dimensional states” especially one that uses the view states model, but you might find other blog posts about it. I haven’t had to really deal with it myself, but I would consider using a presentation model and have view elements come and go based on the model’s properties. It would make it easy to map the model to the BrowserManager as well.