In the past, the search engines (Google, Yahoo, Microsoft Live, et all) couldn’t really search Flash files that well. Well Adobe has been working with the search engines to allow them to search the Flash sites, widgets, buttons, and more.

This is good news on the surface, but still requires one digging a little deeper before trying to get a nifty Flash site. Here are three quick take aways to know about, before

The first thing to know, is you still have to use text, as text, to be searchable. Many Flash developers convert the text into something known as shapes so that they can manipulate it easier to look nice on your screen. While your site will look nicer overall, it will cause the search engine to fail to read that part of you Flash site.

Second, most search engines cannot run JavaScript. Because of a software patent issue, Internet Explorer needs JavaScript to write the Flash file to the webpage. So now, in many cases, your Flash site is no longer searchable.

Flash screens, are not the same as web pages, and that means it will be harder to isolate a topic and rank for it, when looking at the overall site with all of the other text working along with it. Add upon that, that most Flash developers are inexperienced at Search Engine Optimization, and lack good tools to build a search optimized site (links, individual pages, helpful page elements, etc) they will most likely not be able to help you rank like a good HTML based website could.

Overall, I would hold off on developing your all Flash based sites if you are interested in long term Search Engine rankings. (Besides, most developers charge more for Flash sites – use that money to make more content which can rank in the search engines, it will be money better spent.)

SEOmoz has more information on his views on why Flash and Search Engines still don’t mix.

Popularity: 1% [?]

Image via WikipediaAdobe Dreamweaver is a tool used to design and develop web pages. I’ve used Dreamweaver for several versions, starting back in Version 4, when it was owned by Macromedia. Version 10 was just released to public beta yesterday.

I didn’t upgrade to the previous version (V.9) because Dreamweaver didn’t add all of the value I was wanting or needing, and as I’ve posted about before, there were some issues regarding how effective it was for me given the more complex types of web sites I have been working on. Dreamweaver for example didn’t support things like:

• JavaScript libraries and Frameworks
• Poor PHP support
• Produced Bloated Code
• No real support for version control systems

However, Version 10 seems to have added support for some of the features I’ve been wanting, including JavaScript libraries like JQuery and Prototype as well as content version control (a much needed feature for many versions). It also, from what I’ve heard, runs faster than the last couple of versions, which was desperately needed as site development was becoming slow if you had any complex CSS in the design, such as this web site.

This is where the bad experience sets in. I find the link to download the new version and I find out that I cannot use it because I don’t have the previous version (CS3/V9).

photo credit: Jay DuggerSoftware companies have been using the web to push out new products at a faster rate, which is good, but when a company requires you upgrade every 12 to 15 months, about how long Adobe puts out new versions, and pay hundreds to thousands of dollars, they need to realize that not everyone can or will upgrade, especially, if they do not give them the features they need.

Then if you block off part of your users, you risk alienating them. Because of the limitations I’ve found in some instances, I’ve already started using other tools, and might continue to based upon this latest run in with them.

So if you, want to leverage the Internet to brings products to market faster, that is good, just don’t do it at a rate which your customers can’t keep up (because of speed or time). And if you move at that rate, don’t expect everyone to upgrade every version.

Popularity: 22% [?]

There have been several discussions recently on if Ajax developers need Dreamweaver or not. Dreamweaver is a good tool, but it is just a tool not a solution.

The more I use Dreamweaver, the more I can see both its strengths and weaknesses. Let’s look from both points of view to determine if Ajax really needs Dreamweaver. As someone who doesn’t work for Adobe, but has used Dreamweaver for over six (6) years, I am a little bit more objective than some of the voices that have spoken.
(more…)

Popularity: 74% [?]