What would be the proper "metro-friendly" paradigm accomplish the following: I have an enterprise saas/web-delivered app. It currently consists of hundreds of layouts / "screens" which are delivered through the browser via HTML and javascript. For my redesign,
I'd like to take advantage of the metro-style interface, but still have the app and all of it's different screens delivered dynamically through the web (as opposed to having to predefine screens and layouts on a downloadable app). So, I'd like a typical web
app architecture, yet also take advantage of all of the windows 8 metro UI goodness. Is this possible? What is the right way to do it? Can I deliver the screens/tiles through an instance/window/tab/tile of ie10? Would the tiles interface work within ie10 browser
this way? Or would I need to create a downloadable metro-style app and deliver the html to it (like in a web browser)? Or would I have to largely predefine the HTML layouts in a downloadable executable and just have it fetch the data as needed (basically making
it more like a typical cloud-connected desktop app).
I'm afraid this is maybe a painfully obvious answer - but I'm just not clear on it yet.
