Top 10 Pitfalls to Avoid inCreating RIAsAnthony FrancoPresident & Founder, EffectiveUItwitter.com/anthonyfranco | anthonyf...
R ichI nternetA pplication
R ich ( engaging )I nternet ( connected )A pplication ( software )
( engaging )      ( connected )               ( software )
should always be:   software      Rich    Internet  Applications
pitfall #1using the term “ RIA“
cure:     care about creating engaging,connected software
symptom:“we want to build anandroid application”
question:    do all users care about       “multi channel”?
pitfall #2 Putting channelbefore user needs
cure:       ask “why”(uncover user & business needs)
symptom:  “the development is complete, all we needto do now is add a skin”
question:    when should you think      about skinning an        application?
pitfall #3skinning
cure:ux first
symptom:everything seems to be  going great, until...
question   why do big problems show up late in a project?
pitfall #4avoidingconflict
cureembrace conflictand imperfection
symptom:   confused or disenfranchiseddevelopment team
question how do you keep the team  engaged and passionate     about a project?
pitfall #5developers are notinvolved in design
cure  get developmentpassionate about the      end user
symptom:the project is changedoften by stake holders
symptom #2:   the project hasconflicting objectives
questionhave you been on a project where there was a lack of   clarity and purpose?
pitfall #6not defining successnot setting priorities
cure:  before you begin,ensure consensus on  the “win” and set       priorites
symptom:  never enough timefor good development, user testing or quality       assurance
question    do great plans promise       great products?
you can not treat software    development like a   construction project
The Broken Analogy“A bridge is the sum of itsparts. The pieces of metaland welds and everythingelse all add up to a single...
Things you would never have to deal with while constructing a bridge:
Can we move the bridge 17     feet to the left? It’s only 17 feet, so that’s    not a big deal, right?
We aren’t very happy withhow the bridge looks so far.Can you propose a change  in the kind of materials  you’re using to m...
Remember when you asked uswhether the bridge would ever need to support vehicle traffic and not just pedestrian traffic,and ...
We’ve hired an offshore company to start building fromthe other side of the valley so we can cut the construction time in ...
pitfall #7Waterfall
cure:     plan for unpredictabilityand then interate
symptom:the software meets therequirements but is not   adopted by users
do users careabout features?
pitfall #8Putting requirements ahead of outcomes
cureunderstanduser goals
symptom: “I know best aboutwhat our users need”
how does your organization     derive features?
pitfall #9Ego
cure:the voice of the user   (rigorous empathy)
symptom:platform paralysis
question               HTML 5?                 Flash?              Silverlight?               HTML 4?           Native To ...
pitfall #10 Choosing thewrong platform
cure:it depends
1.    Using the term RIA2.    Putting channel before product3.    Skinning4.    Avoiding conflict5.    Developers aren’t in...
thank youAnthony FrancoPresident & Founder, EffectiveUItwitter.com/anthonyfranco | anthonyfranco.wordpress.com
Upcoming SlideShare
Loading in...5
×

10 Pitfalls to Avoid in Creating RIAs

478

Published on

Anthony Franco, president of EffectiveUI, outlines 10 pitfalls to avoid when developing rich internet applications (RIAs).

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
478
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

10 Pitfalls to Avoid in Creating RIAs

  1. 1. Top 10 Pitfalls to Avoid inCreating RIAsAnthony FrancoPresident & Founder, EffectiveUItwitter.com/anthonyfranco | anthonyfranco.wordpress.com
  2. 2. R ichI nternetA pplication
  3. 3. R ich ( engaging )I nternet ( connected )A pplication ( software )
  4. 4. ( engaging ) ( connected ) ( software )
  5. 5. should always be: software Rich Internet Applications
  6. 6. pitfall #1using the term “ RIA“
  7. 7. cure: care about creating engaging,connected software
  8. 8. symptom:“we want to build anandroid application”
  9. 9. question: do all users care about “multi channel”?
  10. 10. pitfall #2 Putting channelbefore user needs
  11. 11. cure: ask “why”(uncover user & business needs)
  12. 12. symptom: “the development is complete, all we needto do now is add a skin”
  13. 13. question: when should you think about skinning an application?
  14. 14. pitfall #3skinning
  15. 15. cure:ux first
  16. 16. symptom:everything seems to be going great, until...
  17. 17. question why do big problems show up late in a project?
  18. 18. pitfall #4avoidingconflict
  19. 19. cureembrace conflictand imperfection
  20. 20. symptom: confused or disenfranchiseddevelopment team
  21. 21. question how do you keep the team engaged and passionate about a project?
  22. 22. pitfall #5developers are notinvolved in design
  23. 23. cure get developmentpassionate about the end user
  24. 24. symptom:the project is changedoften by stake holders
  25. 25. symptom #2: the project hasconflicting objectives
  26. 26. questionhave you been on a project where there was a lack of clarity and purpose?
  27. 27. pitfall #6not defining successnot setting priorities
  28. 28. cure: before you begin,ensure consensus on the “win” and set priorites
  29. 29. symptom: never enough timefor good development, user testing or quality assurance
  30. 30. question do great plans promise great products?
  31. 31. you can not treat software development like a construction project
  32. 32. The Broken Analogy“A bridge is the sum of itsparts. The pieces of metaland welds and everythingelse all add up to a single, static bridge. A software system is the behavior created by the dynamic interaction of its parts” EffectiveUI The art of building great experiences in software
  33. 33. Things you would never have to deal with while constructing a bridge:
  34. 34. Can we move the bridge 17 feet to the left? It’s only 17 feet, so that’s not a big deal, right?
  35. 35. We aren’t very happy withhow the bridge looks so far.Can you propose a change in the kind of materials you’re using to make it more attractive?
  36. 36. Remember when you asked uswhether the bridge would ever need to support vehicle traffic and not just pedestrian traffic,and we weren’t sure, so we just settled on the cheaper pedestrian version? Well, wewere wrong. What can you do to make this work for our needs?
  37. 37. We’ve hired an offshore company to start building fromthe other side of the valley so we can cut the construction time in half. They’re making some improvements on your design, so please coordinate with them to make sure everything comes together ahead of schedule.
  38. 38. pitfall #7Waterfall
  39. 39. cure: plan for unpredictabilityand then interate
  40. 40. symptom:the software meets therequirements but is not adopted by users
  41. 41. do users careabout features?
  42. 42. pitfall #8Putting requirements ahead of outcomes
  43. 43. cureunderstanduser goals
  44. 44. symptom: “I know best aboutwhat our users need”
  45. 45. how does your organization derive features?
  46. 46. pitfall #9Ego
  47. 47. cure:the voice of the user (rigorous empathy)
  48. 48. symptom:platform paralysis
  49. 49. question HTML 5? Flash? Silverlight? HTML 4? Native To Device?
  50. 50. pitfall #10 Choosing thewrong platform
  51. 51. cure:it depends
  52. 52. 1. Using the term RIA2. Putting channel before product3. Skinning4. Avoiding conflict5. Developers aren’t involved in design6. Not defining success7. Waterfall8. Requirements ahead of outcomes9. Ego10. Choosing the wrong platform
  53. 53. thank youAnthony FrancoPresident & Founder, EffectiveUItwitter.com/anthonyfranco | anthonyfranco.wordpress.com

×