Obviously they were very concerned that they had lost all of their blog entries for an entire year.  They did not ... we had a backup of the site.  However, another problem lied in the fact that while we had a backup of the database from the night before, other people in the organization had made 40 other content changes.  We determined this by running a query against the database for changes since the backup the night before.  We could not simply restore the backup copy of the database because all of the other 40 plus content changes on the site would have been lost for that day.

On further inspection, one of our developers was able to take the backup copy of the database from the night before and retore ONLY the blog posts.  So, the only thing "lost" was one blog posting for that day.  We received this emergency notice from the client at 2:32PM.  The blogs were restored by 5:34pm.  This involved triaging the problem, restoring a backup copy of the database, verifying our what we could do, obtaining confirmation from the client, and restoring the blog to the production servers.

This is an example of the type of support we provide every day to our clients ... regardless of their size.  Every site and database gets backed up.  Every client is important.  Can your developer and/or hosting provider do this? 

I of course don't really mean we should get rid of Flash as I think it is a great technology.  But I do think Flash is being overused as a tool in the web designer/developer toolkit.

Ok, to the point ... first I am going to assume you are looking to implement some animation on a portion of your web site that highlights your services or work examples, etc.  Stop reading if you are one of those people who think building entire sites in Flash is a good idea ... we are going to have to agree to disagree.

Over the last several projects, we have been doing more and more with CSS, DHTML, jQuery and JavScript to where animations do not require Flash with very similar effects.  Why is this good?   

• Less overhead
• No special tools required
• Search engine-friendly markup
• More control

Some examples of non-Flash animation: 

• Adage Home
• Adage Client Examples
• Lovejoy Home
• Seko Logistics Home

Again, no Flash needed!  Let me detail why this is good.

Less Overhead 

To provide the effects you see on those pages, a Flash player is not required.  Therefore, the Flash player does not have to start and you do not have to stare at a spinning circle or other graphic telling you to wait a minute to see what you visited the web site for.  With Flash, you often have to wait for the content that has been deemed important enough to draw your attention but in many cases you have to wait.

No special tools needed

When a Flash movie is made, it requires that a file first be created by a developer or designer using a desktop tool from Adobe called Flash Professional.  This is not cheap and can be cumbersome to use in the wrong hands.  So, if you want to make ANY changes, they have to be made by someone with the software (your developer).  There are ways around this but it takes more time and effort to make simple changes.

Search engine-friendly markup

Search engines do not view Flash content in the same manner that they do HTML text.  In the last few years, they have taken steps to try an index Flash content but it is far from perfect.  It is getting better but the accepted general rule of thumb is do not rely on the search engines to index Flash well if at all.

More Control

Flash content that you see on web sites derives from an original source file in which the designer or developer manipulates all of the text, graphics, audio, video and animations. Once a developer is done working in this file, they output this source file as a compiled Flash movie, at which point it becomes uneditable without going back to the original source in Flash. This creates a problem later when changes need to be made to the Flash movie and the developer has left town or they do not want to give you the original source file.  This is something that happens often.

jQuery must live on the site in standard JavaScript files that can be edited and accessed if needed with standard HTML editing tools.  So, if your developer skips out, you already have the "source" and someone with a little knowledge of HTML, CSS and JavaScript can often make a change.

There must be a better way

Again, I am not advocating the elimination of Flash as a tool ... just suggesting a little more HTML, jQuery, and CSS can go a long way to a better web site.  HTML 5 is very compelling as an alternative but that discussion will have to wait for another blog.

As the article points out, a number of factors contribute to this problem but overall, those companies that employ and agile development methodology are more successful at delivering high quality, successful projects.  You can read the Redmond Magazine article here.

Microsoft Courier

Microsoft Windows 7 Touch on a Dell Lattitude

Microsoft Surface

Also, a lesser known technology of Microsoft's is Surface, a touch screen that comes in the form of a coffee table that provides multi-touch kiosk functionality.  This is still largely limited to vertical applications (i.e. retail, healthcare, public sector, etc.) but portions of its underlying technology were likely used in development of Courier.  Finally, Windows 7 is multi-touch capable.  A host of tablet-like devices are due out soon (read October) using this technology. 

What does all this mean?  We can start to expand on our conceptions of application interfaces in ways we never imagined.  At Adage, we have already begun experimenting with portions of the underlying technology and are excited about its potential.  Tablet applications that did not make sense before because they required a mouse, may be worth another look.

While we have been following an Agile development methodology for some time now, we realized we were have been adhering to lean development principles for some time.  

As a result, Patrick Emmons, our professional services director, felt it would be helpful if we shared how we apply these principles to our development process. You can read the entire article here.

The product works as promised.  We have begun the process of converting our developer machines from XP to Windows 7 (64 bit) allowing them to take advantage of memory that is well over the 4GB limit with XP.  All of or developers are running MS Office, Visual Studio, SQL Server, and a smattering of other development tools like TOAD for Oracle.  With all of these applications running, the memory can get gobbled up quickly.  The benefit is faster reponse time and quicker compiles for large Visual Studio projects.  If you are considering the change, I encourage you to make the leap ... this one is worth it.

In the beginning stages, the estimate can easily be off by a factor of 4x.  This means if you intend on getting estimates for development and the estimates range from $30,000 to $120,000 it is not abnormal.  Even when the requirements and user interface design is complete, the estimate can still be off by a factor of 25%.  Unfortunately, software development is a complex effort.  This is why we advocate smaller iterations and a more agile approach to application development.