10Jan/105
Best Practices for Designing RIAs
These best practices come from an eight part series written in the fall of 2007. Although the series was written specifically for designing applications in Flex 3, this list is a general list of best practices for improving user experience. I stumbled across hard copies of the series while going through some files this afternoon. Some of the examples are dated, but the core information is still relevant and applicable.
Whether designer or developer, we can not forget or lose sight of the users' experience. Too many times UX is sacrificed for other priorities. We can't all be Microsoft - if we ignore our users, we will no longer have users.
January 11th, 2010 - 07:57
I can attest to these guidelines being equally valuable in web development. If you’re more into HTML than flash like me, just replace the word application with “website” in your mind and these make a incredibly helpful read.
Thanks Michelle!
January 11th, 2010 - 08:37
Hi Michelle. Keep them coming. This is great!
January 11th, 2010 - 19:03
http://www.adobe.com/devnet/flex/articles/fig_pt1.html
March 5th, 2010 - 06:48
http://www.adobe.com/education/instruction/teach/ria.html?trackingid=DYDOY
March 19th, 2010 - 13:16
Requirements Technical Writer – building a job description
Postulate #1: The thorough gathering of requirements is defined as: “The gathering and recording of details pertaining to what the customers want the application to be and to do. This includes nuance. Subtlety. Attention to the smallest detail.”
Postulate #2: Requirements must be exhaustively recorded, then carefully organized and written into a set of deliverable documents. The audience for these is the team of programmers and developers who will write the code and build the application.
Postulate #3: A technical writer who is schooled in programming methodologies and object-oriented processes and design patterns can best translate and organize those customer requirements into verbage that can be transformed by software engineers into modules and functional components.
Postulate #4: In a Flex development project, the requirements technical writer will:
1. Meet with customers to capture requirements.
2. Draft a set of requirements, review them with customer base and gain their approval.
3. Mock up the UI of the application in Photoshop or Illustrator wireframes. Get customer approval.
4. Deliver those wireframes to a designer with instructions for building them in Illustrator and then in Catalyst. (Pay attention to layers.)
5. Gain approval of the Catalyst UI from the customer base.
6. Write the requirements in terms of the design patterns that will be used by the programmers.
7. Deliver to the programmers a full set of requirements docs ( Functional spec; External spec; Internal spec; Design spec; Process spec) together with the Catalyst-generated Flex files.