3 ms·
This is a good and substantive piece that is better than the tone of its title. The question it addresses - html or Flash? - is one that we really struggled ove
by gruseom 19y ago
This is a good and substantive piece that is better than the tone of its title. The question it addresses - html or Flash? - is one that we really struggled over, and I would like to hear others' stories of how they made this decision. So here's mine.
We want to compete against established desktop software. UI is critical to us, and there's no way that an html-based UI is going to be as slick or performant as what we could do in an installed program. So the prospect of getting a richer and (presumably) easier to program UI out of Flash was very enticing. Yet in the end we decided against it.
What settled this in my mind was asking, How central is the web to what we're trying to do? Do we want our app to work roughly the way a website does? Is it natural to model it as a series of "pages" represented by URLs, connected by hyperlinks, and so on? Or is this an artificial imposition on our problem?
In our case, the question has a clear answer: making our product work roughly like a web site is key. In fact, the more it works like a website the better: our users need to navigate complex graphs of information, and the web is the established model for that. We want our new stuff to work in a way that users are already familiar with (albeit from a different context, namely web surfing), so as to keep their learning curve as low as possible.
So "webbiness" is an essential part of our product, which should therefore speak the native language of the web. The last thing I wanted to end up having to do was write an ad hoc, informally specified implementation of half of a web browser in Flash. Users would know that they weren't looking at "real" web pages, and it wouldn't feel right. So when I hear about people hacking their Flash app to support URLs and so on, I feel relieved we didn't go down that road.
On the other hand, the decision we did make has caused our programming efforts to become swamped by the minutiae of divs and doms and Javascript. We're hacking a platform that was never intended for what we're building. That sucks, too. And it has slowed us down. But I will say that making this work, and work well, in a web browser has been exhilirating.
Edit: the other thing I wanted to point out is that this webbiness criterion also holds if you look at the successful Flash apps: games, video, photo editing, and so on. These are not problems where it would make sense to structure the solution like a web site. I'd be interested in hearing counterexamples to either side of this.
- greendestiny 19y agoI choose to do my web application in flash for exactly same reasons that lead you to html and css. Its all interaction and not navigation. I actually think the mixing of content and interaction that web applications have become is incredibly powerful - I think the idea that we'll prefer desktop style buttons and widgets over text links is wrong, very very wrong. And I think that's where most of the reluctance for flash apps comes from but people don't recognise it. Also web pages progressively load by default and thats important. On a purely programming tip, actionscript 3 is a joy to program in. The flex components are good.