I was browsing around the Adobe Dev Net sites this afternoon during lunch and read this article "Top 10 Mistakes when Building Flex Applications" by James Ward & Jon Rose I agree with about 90% of what they were talking about. Except for #5) "Trying to hire experienced Flex Developers". This statement to me is just emphasizing how easy it would be for a Java programmer to get into Flex, but I really think it's a marketing comment and doesn't belong on the top 10 list. Now if the title was "Top 10 Mistakes when Staffing for a Flex Project" I would definitely agree it should be on the list. ;)
Overall, a good article, short, sweet and to the point. I especially like #10 "Not Preparing for Offline Applications". Now that we have AIR every project that is using Flex or AJAX for that matter should have a offline/desktop supporting architecture, or at least a place holder to add it in later. In the next 2 years, users and customers will be demanding offline capability with data syncronization when the user is back "online".
Here is an example use case:
- John uses a tool to capture research & development projects to support his team
- John is going on a business trip and will be offline quite a bit
- John opens up the tool he uses (RIA/AIR Application) - Gets the latest data from the server and logs off
- Now that John is on the plane, John decides to do some work and opens up the tool
- John's tool recognizes he is offline and uses the SQL-Lite Database that was recently syncronized with the server before John Left work
- When John gets to his hotel or at a offsite location, John connects to his works VPN and opens up the tool he did his work in.
- Again, the tool recognizes John is now online and saves John's changes to the server, where it can now be viewed by all of the other employees in the company.
- John get's a gold star for being productive on a Airplane, something he simply couldn't do with a web application in the past.
The capabilities are really endless now that we have AIR + Flex/AJAX.
Recent Comments