About Flash...
Over the releases of new versions of Flash, Macromedia has made Flash more and more controllable via programming, where they have it positioned as a competitor to HTML to build interactive web sites and applications such as an e-commerce store. Macromedia argues that Flash is the way to go instead of HTML because of the following reasons:
Flash movies load faster and save on download time because Flash is vector based whereas HTML is not.
Flash intelligently ‘caches’ it’s movies so they don’t have to be reloaded.
Flash gives the user (the person viewing/using the Flash movie) a more responsive ‘rich-client’ like experience.
All of these points are true, but they can be true for HTML pages as well (except for the vectors). I will address these points now:
Flash pages can be made to load faster, but most of the time, the way they are designed in the real world, they do not. That is not a Flash problem, it is more an issue of the Flash developers going nuts with fancy and heavy Flash movies.
HTML caches pages as well, once images are downloaded they are held in your browser's cache. The cached images are then used instead of dowloading them from the server again.
With new technology like ASP.net and Java Server Faces, HTML now can react just like a ‘rich-client’ application. Even without these new tools, properly designed HTML for most dynamic sites can provide a good user experience.
A concern is that Flash does not cache (or store) non-vector images, therefore they must be reloaded each time. Not a pleasant thing for your visitors! This is in contrast to HTML-based scenarios where the browser will cache the imagery for instant retrieval.
As you can see, Flash is not always the right solution. This is true of any aspect of Web development, where you need to research your options carefully and choose the right combination of tools that works best for you. If you seek outside help, make sure you find a team with the right expertise and a solid track record to back it up.