Ryan Stewart geht in seinem Blog auf die “üblichen” Vorbehalte gegen Flex (bzw. RIA allgemein) ein. Man kennt das ja… Suchmaschinen, “Back-Button”, Links setzen….

• And what about search engines and other content-aware tools, which cannot easily access the content delivered by Flex applications? Flex is meant for web applications. How do you search an application? Help documentation, maybe, but a full application? Sure there are things you want to associate with your application so it shows up in Google, but is that really searching an application? Web search isn’t meant for applications, and the current methods just don’t apply. I think this goes for both Ajax and other RIA technologies.
• And permalinks, which do not work as naturally with Flex as they do with HTML? How do you bookmark a piece of content in a Flex application on Delicious? This always kills me. Applications aren’t made up of pages, they’re made up of states. Inherently, states aren’t made for the bookmarking model of the browser. States are all about which path you followed and what feature of the application you’re using. Trying to shoehorn that into the page model won’t work. Saving states is valuable, but the browser bookmark is a poor way to implement that.
• And - which surprises will you run into when you hit the browser’s Back button? There is no back button in Microsoft Word. Or Life. Again, the back button is great for turning a page, but when you’re in an application does “back” mean undo? Does it mean up one row? Does it mean the previous menu? Going back with pages is easy, but applications aren’t meant for the back button, and with good reason.

Gesamter Artikel: Stop Thinking of Flex As a Browser Technology. Seriously. Stop It.

Posted on Februar 24th, 2007 von Franz
Filed under: RIA