3 Responses to “Top 10 Mistakes when building Flex Applications”

1. Ian Rae writes:
   No. 1 — April 21st, 2008 at 7:15 pm

   How about posting the top 10 coolest approaches for building a great flex app ;) I know it leads to the same darn points but its sooo much more positive!

2. James Ward writes:
   No. 2 — April 22nd, 2008 at 6:37 am

   Hi Ian,

   Haha. People don’t ever read positive articles. ;)

   -James

3. Bill Shirley writes:
   No. 3 — April 22nd, 2008 at 8:43 am

   “Let us know what you think,” he said innocently, unaware…

   1. You were very nice not to title it: Don’t be a Dumb Ass.

   2. I don’t think you meant “book marketing”.

   3. It sounds more like exposing a flaw in the implementation of Flex. But it’s good to know to be wary of it.

   4. !!! I totally agree. XML cool-aid should be avoided when possible. Too bad someone though MXML would be a good “language” (it’s a perfectly fine file format – and luckily the IDE eases using it).

   5. Yes. I suggest looking for UI developers familiar with event-driven models. Not flash coders. Not “web app” coders.

   6. Yes (see “no flash coders”, above). If the project is large enough, there should be a human factors/interface specialist with the final call on how the interaction with the application should work. Maybe send a promising developer to a SIG CHI conference – http://www.sigchi.org/conferences/

   7. Yes – true of all development efforts, but good to mention.

   8. Good tip.

   9. I’ve loaded 1000’s of objects into DataGrid with no custom renderers and it’s almost instant. I’ll watch for this in the future.

   10. Hmm, offline is nice. Something to think about.

Leave a Reply

Name (required)

Mail (will not be published) (required)

Website

Notify me of followup comments via e-mail