Your SlideShare is downloading. ×

10 Pitfalls to Avoid in Creating RIAs


Published on

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

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

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Top 10 Pitfalls to Avoid inCreating RIAsAnthony FrancoPresident & Founder, |
  • 2. R ichI nternetA pplication
  • 3. R ich ( engaging )I nternet ( connected )A pplication ( software )
  • 4. ( engaging ) ( connected ) ( software )
  • 5. should always be: software Rich Internet Applications
  • 6. pitfall #1using the term “ RIA“
  • 7. cure: care about creating engaging,connected software
  • 8. symptom:“we want to build anandroid application”
  • 9. question: do all users care about “multi channel”?
  • 10. pitfall #2 Putting channelbefore user needs
  • 11. cure: ask “why”(uncover user & business needs)
  • 12. symptom: “the development is complete, all we needto do now is add a skin”
  • 13. question: when should you think about skinning an application?
  • 14. pitfall #3skinning
  • 15. cure:ux first
  • 16. symptom:everything seems to be going great, until...
  • 17. question why do big problems show up late in a project?
  • 18. pitfall #4avoidingconflict
  • 19. cureembrace conflictand imperfection
  • 20. symptom: confused or disenfranchiseddevelopment team
  • 21. question how do you keep the team engaged and passionate about a project?
  • 22. pitfall #5developers are notinvolved in design
  • 23. cure get developmentpassionate about the end user
  • 24. symptom:the project is changedoften by stake holders
  • 25. symptom #2: the project hasconflicting objectives
  • 26. questionhave you been on a project where there was a lack of clarity and purpose?
  • 27. pitfall #6not defining successnot setting priorities
  • 28. cure: before you begin,ensure consensus on the “win” and set priorites
  • 29. symptom: never enough timefor good development, user testing or quality assurance
  • 30. question do great plans promise great products?
  • 31. you can not treat software development like a construction project
  • 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. Things you would never have to deal with while constructing a bridge:
  • 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. 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. 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. 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. pitfall #7Waterfall
  • 39. cure: plan for unpredictabilityand then interate
  • 40. symptom:the software meets therequirements but is not adopted by users
  • 41. do users careabout features?
  • 42. pitfall #8Putting requirements ahead of outcomes
  • 43. cureunderstanduser goals
  • 44. symptom: “I know best aboutwhat our users need”
  • 45. how does your organization derive features?
  • 46. pitfall #9Ego
  • 47. cure:the voice of the user (rigorous empathy)
  • 48. symptom:platform paralysis
  • 49. question HTML 5? Flash? Silverlight? HTML 4? Native To Device?
  • 50. pitfall #10 Choosing thewrong platform
  • 51. cure:it depends
  • 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. thank youAnthony FrancoPresident & Founder, |