Why use Flash for site development?
I am currently working with a client to develop a highly interactive news/portal style web site. The project will feature several prominent elements developed in Flash, but the bulk of site (architecture, navigation, etc.) is to be scripted in HTML/AJAX. Having built many internet-connected, database-driven applications in Flash, I couldn’t help wondering if it might be better to build the entire site with Flash, so I proposed this as an option, initially to our team and then to the client. Now, the client has not yet decided one way or another, but did come back with questions, one of which has me a bit dumbfounded. They wanted to know, “If Flash is so well suited for site development, why isn’t anyone else using it?” That no one else in this particular space is using Flash aggressively doesn’t surprise me - while they are technically competent, they are not exactly ‘early adopters’. What did surprise me was that I was unable to find anyone - outside of the usual genX(y,z,?)-directed promotional sites for cars, shoes or energy drinks - using Flash to deliver anything more the demo/presentation/advertising in the enterprise space. Sure, a few sites feature some clever whiz-bang flash interactives, but not even Macr… Adobe is using Flash for site development. Is the dog food so distasteful?
Assuming that Flex is off the table (because it is), how do I make a valid argument for site development in Flash vs. AJAX, for example, or simple HTML and ASP?
Below is the argument I am currently presenting (some of the terminology has been simplified for consumption by non-developers). Let me know if you can think of anything I’m missing or failing to consider.
_____________________________________________________________________
It makes sense to build simple web pages in HTML and to extend the functionality of HTML web sites with AJAX. However, even with AJAX, HTML is not a particularly robust platform on which to build an application. HTML is designed to get and display relatively static pages. AJAX is a layer of code (i.e. JavaScript) injected into the HTML to override the static page model and extend the functional capabilities of web pages in the browser. Again, with simpler pages/sites this makes sense. But, as the complexity of a site increases, the need for clean, unified application architecture becomes more critical. In recent years, the Flash platform has grown to fill this need.
Delivering site navigation and client-side functionality in Flash:
Common criticisms of Flash-based web development:
This has been addressed with the ExternalInterface component which allows Flash to reference JavaScript and vice versa.
This is common to AJAX as well, and can been remedied with effective workarounds and ‘shared objects’ (similar to cookies).
This is certainly a trap that many Flash designers fall into, but is not inherent to Flash, just poorly directed UI design.
In addition to the concerns addressed above, I think the problem is the lack of industry mind share. While almost every web developer is comfortable building web sites with HTML and JavaScript, there are relatively few Flash developers capable of building more complex web-based applications. Organizations generally default to the technologies with which they are most familiar.
What are you seeking?
(I could understand “site development” in any of several ways.)
For “How many websites use no HTML but all SWF?” then I don’t know, but I would hope not very many… the idea is to use SWF for its strengths, HTML/JS for its strengths.
“how do I make a valid argument for site development in Flash vs. AJAX”
Find out what the project needs to accomplish, and find out what the other person thinks they’re talking about when they use the label “AJAX”, that’s one possible path.
May 2nd, 2006 at 4:14 pmI can give you one reason that gets used on me why clients generally do not want to use Flash for site development.
UPDATESTypically a client will need the ability to make quick updates to sites and not always want to bring in a vendor for those changes. Most companies will not have the skills required in Flash to make updates (at least that is their thought since a well designed site will be as easy to update in Flash as it would be in HTML w/AJAX). The mind set for the client is that HTML will be easier for updates than Flash would be and they usually step away from using Flash.
May 2nd, 2006 at 4:25 pmHi John,
Assume that the site will consist of at least one HTML page with JavaScript that will extend the capabilities of the embedded SWF(s). I am proposing that the site navigation and core functionality be contained within the Flash along with most of the content (dynamic and static). Exceptions might include pre-built chat/forum/RSS widgets that are impractical to recreate or skin with Flash, which could be delivered in iframes.
Either way, both Flash and HTML/JavaScript will be used. The question is whether the client-side logic resides primarily within the Flash or the JS.
May 2nd, 2006 at 4:52 pmHi Tim,
Agreed. In fact, a well designed Flash app/site can pull all or most of its assets (text, HTML, CSS, graphics, audio, video and config data) from external sources, so NO editing of Flash source would be required.
May 2nd, 2006 at 5:14 pmI build lots of Websites in Flash. They are template based sites which are controlled with a separate Content Management System (also in Flash).
There are links to some I have create on my website (which is flash) http://www.tvwonline.net
Two important things to cover, 1. Address the Back Button issue (which is easy) and 2, create a Text Version of the content for Search Engines.
May 2nd, 2006 at 5:17 pmFlash helps websites to really come alive on screen. And for visual effects, and slickness in a web site or web app, Flash is much more efficient and maintainable, no cross browser development.
I saw the light a few days ago in a little matter regarding regarding SWFObject, and realized that the biggest drawback to building websites with Flash is that Adobe controls Flash, and the only *usable* swf player. So the future of all Flash work is in their hands at the moment.
Nobody owns HTML and Javascript, PHP etc.
That being said- I love the tool for what it is, and right now I only offer websites in Flash which the users update themselves (easily!).
May 2nd, 2006 at 5:50 pmIt says it all.
The other major problem is that Flash performs poorly when it comes to display a lot of information, or just a few UI components.
May 2nd, 2006 at 11:57 pmI’m so glad to finally start seeing some posts like this. Flash is ready for prime time and it’s up to us to move Flash from eye-candy, portfolio sites and slick advertisements to its place as the most compelling internet client application platform in the world. I’m talking about a full-blown CMS written in actionscript that handles SEO, BACK / FWD button functionality, text, page transitions, database integration, blogs, etc. Everything needed in a modern web-based presence for a large Enterprise.
I continue to think that adobe must put its money where its mouth is by using Flash for a major portion of its website. How can we sell Flash to an Enterprise as a serious platform for their Internet presence if the company who sells it refuses to use it in this way?
All we have to do is look at the first comment here by Adobe’s rep. He addresses the question of all Flash websites by saying he hopes there aren’t many??!! That is alarming.
A Flash-based CMS can be efficient, functional, and much more user-friendly and interactive than HTML. And the EXPERIENCE is far superior.
I thought that’s what Flashers believed in - experience.
How many high-profile Flashers use Flash for their websites other than portfolio sites? I can’t think of one.
C’mon Flash community. Let’s build some reusable classes and frameworks. There is very little Flash cannot do, but Companies aren’t just going to take our word for it. We have to show them.
May 7th, 2006 at 3:07 pmJust a quick update:
The client has given us the green light on our proposed implementation of Flash - hurrah! Now the work begins.
I will track our progress and describe some of the technical challenges/solutions in future posts (time and NDA permitting).
May 7th, 2006 at 9:52 pm[...] In an earlier post I asked the question “Why use Flash for site development?” and went on to give a list of valid reasons why Flash could be a suitable platform for (RIA) site development. I presented a similar list to a client I am working with on a (perhaps overly) rich internet app. After some consideration we decided to move forward on my recommendation and build the client architecture and components in Flash. This is where the previous post left off. [...]
June 26th, 2006 at 12:06 amI do have hopes the general consensus will finally be that Flash holds the greatest promise in web developement. Your client will of course be very pleased.
September 16th, 2006 at 3:17 pmHi all - I LOVE Flash and have been using it a lot just as an extra in my designed sites as I come from a corporate background where the client comes first, etc, etc and so because of all the previous historical problems with Flash have just used it to add some interaction or nice effects to my sites (ie, fading pics and text as part of the design).
I am currently diliberating on whether to design one of my sites completely in Flash for my current client who has a small business. It’s such a good programme and I can’t understand why we as designers haven’t bitten the bullet and used the programme! Anyway, I would like to learn more about how to make Flash dynamic, ie, using external files so my clients can easily update and learn more about site optimisation. However, I’m a designer NOT a programmer - doesn anyone know where I could find some “easy to read” tutorials on these subjects? Or advice on how I could get round this?
August 12th, 2007 at 2:41 am