RIAPT Event – Best and Worse RIA practices

Enrique Duvos, Platform Evangelist, Adobe System
    As Group Manager of Flash Platform Evangelism in EMEA, my role is to manage the Adobe elite team of technical evangelists as they drive adoption and build thriving communities.
    Our role as Platform Evangelists is to help customers, partners and developers across Europe understand and adopt the benefits and characteristics of the Adobe Flash Platform core technologies, such asAdobe® Flash, AIR, Flex, Flash Catalyst, BlazeDS and Flash Media Server.

Bases on the Best and Worst Practices for building RIA By James Ward (Adobe Systems) and Josh Holmes (MSFT UX Evangelist), presented in the Web 2.0 2009 Expo.

Best Practices

  1. Forms follow function (MVC vs MVP)
    • Concentrate on the function first and the model after
  2. Leverage Design Tenents
  3. Use the right fidelity level
  4. What do your users and customers want?
    • We offer three kinds of service: Good – Cheap – Fast – Pick any two
    • Good service Cheap won’t be Fast
    • Good service Fast won’t be Cheap
    • Fast service Cheap won’t be Good
  5. Ease of use or power users? Both
  6. Are you thinking about concurrency?
  7. Balance the computing load
  8. Security vs Usability
  9. Maintenance and Versioning
  10. Contextual Applications

Worst Practices

  1. Not a RIA application … don’t use RIA Technology
  2. Remember the environment … Users Refresh
  4. Do you really have that much bandwidth?
  5. Animation-sickness
  6. Have you heard the word “Framework”?
  7. The wild developer (No Source Controls, TDD, CI)
  8. Too many containers
  9. Complex rendering
  10. Fanatic vs Pragmatic?

Flash Player 10.1

  • Smartphone enabled
  • Multitouch, accelerometer, screen orientation
  • Optimized memory, power, hardware acceleration
  • Http video streaming

Adobe Air 2.0

  • Contextual Apps and Desktop Integration
    • More peripheral support
    • More flexible networking
    • improved native OS
  • Mass Storage Device
  • Improved Socket Support
  • Invoke Native Applications
  • Multitouch
  • Updated Webkit Engine

Leave a Reply

Your email address will not be published. Required fields are marked *