

There are attempts to develop Flex web applications. Most of them I’ve seen are Flex applications on web. While Flash is omnipresent, people still feel odd and disoriented when getting on a Flex application while surfing the web. The usability of a windows style Flex application is indeed different from HTML web site. Going either directions, turn-web-to-desktop or leave-as-it-is, using Flex is OK with me. I just want to see people do it right. I think the Ultrashock guys did it right.
Ultrashock is a commerce site that basically selling multimedia assets. However, the site is developed (or redeveloped) in Flex and it closely reassembles a general HTML web site use experience. That approach actually makes the Flex (or Flash) features stand out. People will naturally and mentally compare browsing experience when jumping from site to site. At Ultrashock, they will compare it with the rest of the HTML web site. Therefor, it certainly gives Ultrashock a big advantage from usability stand point. That’s what happens when a Flex application becomes a web site.
I like its business model too. You sign up and buy credits, one dollar one credit. Then you browse through the contents to find the assets you like, while UI is very attractive so that you search and view will be very enjoyable (so that you will be willing to spend more time searching, clever.) When you find the one you love, download it by paying with your credits, there are lots of one credit good looking assets. That’s it.

If you would like to make a comment, please fill out the form below.
| Cox bundle ||| Verizon Deals ||| Comcast cable |
You make a good point, but something inside me still thinks that flex apps should be applications, and that trying to force an application into a document metaphor isn’t the right way to go.
I actually think that using Flex to build ‘websites’ isn’t such a bad idea after all. You get rid of all the quirks of HTML, Javascript, … and get all the nice stuff (that you can enhance yourself). I do think however that the actual content of each ‘page’ should remain available as xhtml & hyperlinks for Google etc (the Flex-based output for the first page could be shown by applying XSLT to the XML document - more info at the end of http://www.onflex.org/ted/2007/05/project-roloflex-aka-flex-directory.php). It’s however perfectly possible to generate Flex GUIs based on the same XML. In other words: it’s time for Flex-based CMS solutions that have an eye for Google page rank.
We allowed ourselves to be trapped in the document-centric world in order to transition from desktop apps to the internet, and users have adapted to the dumbed-down application interfaces. I don’t think we should assume that users can’t make the transition back to rich interactivity, though we have a clear opportunity to try to establish standards of UI behavior to make applications more intuitive while making them much richer than their HTML counterparts.
A rather poor analogy might be to say that since someone is used to reading a newspaper, then couldn’t deal with a well constructed RSS aggregator/portal.
How do I get my index file to point to my flex app. I created a web page with Flex 2 now I want to put it on my site. Help!!!!!!