Challenge Summary
For this contest you will create pages for a simplified e-mail client.
This application will be an e-mail client with a greatly simplified user interface, which is suitable for old people, and for some very young, and for any person having cognitive disabilities that would make using a regular e-mail client difficult.
The main goal of this application, is to satisfy elderly people and others who have trouble with complexity with an extremely simple and yet powerful communication client with a guided and very user-friendly GUI.
Client Goals As stated, the goal is to provide a simple, accessible, user-friendly system for the users. Most notably: - Simplified and visually attractive GUI to be used by users with NO computer experience - and without requiring instruction beyond simple, short orientation. - Ability to delegate all the configuration actions to more experienced user (like child, Assistant, etc.). - All actions will be performed easily and in the guided way. - The e-mail client will be quite full-featured with removal of some overly complex features. - E-mail client can work in different levels of user experience (simplest, moderate, advanced, etc.) - Improve the experience for the user Application Functionality - Automatic periodical checking of the incoming e-mail with ability to manually check too. - Alerts for New Mail - Ability to read incoming e-mail in the simplified way. - Ability to easily reply to the incoming e-mail. - Ability to make a new e-mail and send it in the easy way. - Ability to arrange e-mail on the desktop of our e-mail client. - All application actions will be performed through the context menus. - Ability to create/open/delete folders in easy way in the advanced mode. - Ability to delegate all the configuration actions to more experienced user (like child, tutor, etc.). Project Considerations - The application will meet WCAG 2.0 level A accessibility and preferably also meet level AA and as much of Level AAA as possible. (www.w3.org/TR/WCAG20) - The application is expected to be Flash based - that will provide great visual GUI, and at the same time is platform independent. Adobe Flex framework and Action Script 3.0 language will be used for coding this application. At the same time, a regular Java or .NET platforms can be used for this application - up to architect. Workflow Description The application is divided by three parts: 1. User application - the simplified e-mail client. 2. Tutor part - some configuration web-pages (like any regular web-application). 3. Admin Tool - the management web-pages for owners & maintenance of that application (AOL staff). It can be like any regular web-application. User/Parent - The User will open the e-mail client and it will automatically login with User credentials to this application web-site (some AOL web-site is expected). - The e-mail client will automatically receive the incoming e-mail. - The incoming e-mail will be instantly available for the User and displayed as thumbnails (small envelops) in the simplest mode, or as text line - in the advanced mode. - The User can click and open some e-mail for the next reading. - The e-mail message will be shown to the User. - In moderate and advanced modes the e-mail text can be scrolled. The area of e-mail thumbnails can be also scrolled in moderate and advanced modes. - The User can easily reply to the incoming e-mail, edit the reply message text and send it to the originating user. - The User can make a new e-mail, enter the e-mail data, select (or enter) e-mail address of recipient and send that e-mail. - If some e-mail is no more needed, then the User can easily remove it from the application. - In the advanced mode the removed e-mail is placed to the trash can and can be restored by the User if he/she mistakenly removed that message. - The e-mail messages can be arranged on the desktop - the User can move messages on the "desktop" by mouse. There will be an imaginable grid of placeholders on the desktop where the e-mail messages thumbnails can be placed by the User. - In the advanced mode - the User can create/open/edit folder for storing the e-mail messages. Some folders will be predefined (like Incoming, Sent Mail, Trash, etc.) Tutor/Assistant - Tutor will register on our application web-site. - Tutor will be required to manually login to our web-application. - Next he will edit his profile, register User and assign to use that User application together with his application. - Tutor can freely edit/remove his and User's profiles. - Tutor can configure every aspect of the User application. Admin - The Admin user will be able to register and manage other admins accounts for our web-site. - The Admin has to manually login until get access to the admin tool. - The Admin will manage every user profiles (if needed). He/she can create/update/remove any profile on the web-site. - The Admin will also configure entire web-application (like enabling/disabling some features, and so on). - The Admin will analyze all the user actions and can get some simple HTML-based reports with statistical information. Target Audience Older, younger or cognitively disabled persons with little experience on modern computers who are overwhelmed and confused by the features contained in a standard e-mail client like Mozilla Firebird or Microsoft Outlook. Provided Documentation We have provided two PDF files. The first is the output from the conceptualization contest "My Parents E-mail" (conceptulaization_document.pdf) web application. The second is feedback from the Advisory board called sdc_mpecomm.pdf. We are only concerned with the e-mail portion of this solution. Pages specifically: - 2-6: General Overview - 8-11: General e-mail functionality - 12: The Assistant Application - 13: Admin Application If you have questions, these two documents will likely contain the answer you are looking for. However, please feel free to post to the forum, the client is happy to clarify any point. Keep in mind that these screens may be branded. Your wireframes should NOT be branded in any way. Please refer to the Wireframe Requirements section below. Wireframe Considerations When designing your wireframes, ask yourself questions that the user is likely to ask when using this system. This will help with usability/accessibility issues and interaction. Some examples: - How will the user most commonly use this application? - What are the most used features? - When creating an e-mail, what will the user want to do next? What should be accessible, available? - How should the user be able to navigate through the application? - Would a progress bar aid in the experience? What other cues can be added for the user? Wireframe Requirements - Wireframes should NOT address design - Wireframes are meant to provide content, convey the hierarchy of information and show content groupings. - Provide an intuitive user experience - Analyze navigational possibilities and make recommendations - The amount of pages/screens is up to you, but should be less than what is currently being used - Wireframes must only be black, gray and white - color can be used for information call-outs - Wireframes must address the user interface as well as the flow of the application - Wireframes must be linked appropriately for page flow and interaction Wireframe Resources - Wireframes on Wikipedia: http://en.wikipedia.org - Wireframe software option: http://www.axure.com - Example Wireframe: http://www.gdoss.com/web_info/web-site-wireframe.php Wireframes can be built in HTML, Axure (listed above), MS Visio or OmniGraffle. The source files types are not critical in this contest. The most important point is that all the content in listed and the pages are linked together to show page flow. Judging Criteria Your submission will be judged on the following criteria: - How well your wireframes provide a consistent user flow - How well you implement the required screens and any suggestions, interactions and user flow you recommend. Preview Image Please provide a screenshot of the email client as your preview image. Do not alter, skew, modify or add drop shadows or other design filters for dramatic effect.
Client Goals As stated, the goal is to provide a simple, accessible, user-friendly system for the users. Most notably: - Simplified and visually attractive GUI to be used by users with NO computer experience - and without requiring instruction beyond simple, short orientation. - Ability to delegate all the configuration actions to more experienced user (like child, Assistant, etc.). - All actions will be performed easily and in the guided way. - The e-mail client will be quite full-featured with removal of some overly complex features. - E-mail client can work in different levels of user experience (simplest, moderate, advanced, etc.) - Improve the experience for the user Application Functionality - Automatic periodical checking of the incoming e-mail with ability to manually check too. - Alerts for New Mail - Ability to read incoming e-mail in the simplified way. - Ability to easily reply to the incoming e-mail. - Ability to make a new e-mail and send it in the easy way. - Ability to arrange e-mail on the desktop of our e-mail client. - All application actions will be performed through the context menus. - Ability to create/open/delete folders in easy way in the advanced mode. - Ability to delegate all the configuration actions to more experienced user (like child, tutor, etc.). Project Considerations - The application will meet WCAG 2.0 level A accessibility and preferably also meet level AA and as much of Level AAA as possible. (www.w3.org/TR/WCAG20) - The application is expected to be Flash based - that will provide great visual GUI, and at the same time is platform independent. Adobe Flex framework and Action Script 3.0 language will be used for coding this application. At the same time, a regular Java or .NET platforms can be used for this application - up to architect. Workflow Description The application is divided by three parts: 1. User application - the simplified e-mail client. 2. Tutor part - some configuration web-pages (like any regular web-application). 3. Admin Tool - the management web-pages for owners & maintenance of that application (AOL staff). It can be like any regular web-application. User/Parent - The User will open the e-mail client and it will automatically login with User credentials to this application web-site (some AOL web-site is expected). - The e-mail client will automatically receive the incoming e-mail. - The incoming e-mail will be instantly available for the User and displayed as thumbnails (small envelops) in the simplest mode, or as text line - in the advanced mode. - The User can click and open some e-mail for the next reading. - The e-mail message will be shown to the User. - In moderate and advanced modes the e-mail text can be scrolled. The area of e-mail thumbnails can be also scrolled in moderate and advanced modes. - The User can easily reply to the incoming e-mail, edit the reply message text and send it to the originating user. - The User can make a new e-mail, enter the e-mail data, select (or enter) e-mail address of recipient and send that e-mail. - If some e-mail is no more needed, then the User can easily remove it from the application. - In the advanced mode the removed e-mail is placed to the trash can and can be restored by the User if he/she mistakenly removed that message. - The e-mail messages can be arranged on the desktop - the User can move messages on the "desktop" by mouse. There will be an imaginable grid of placeholders on the desktop where the e-mail messages thumbnails can be placed by the User. - In the advanced mode - the User can create/open/edit folder for storing the e-mail messages. Some folders will be predefined (like Incoming, Sent Mail, Trash, etc.) Tutor/Assistant - Tutor will register on our application web-site. - Tutor will be required to manually login to our web-application. - Next he will edit his profile, register User and assign to use that User application together with his application. - Tutor can freely edit/remove his and User's profiles. - Tutor can configure every aspect of the User application. Admin - The Admin user will be able to register and manage other admins accounts for our web-site. - The Admin has to manually login until get access to the admin tool. - The Admin will manage every user profiles (if needed). He/she can create/update/remove any profile on the web-site. - The Admin will also configure entire web-application (like enabling/disabling some features, and so on). - The Admin will analyze all the user actions and can get some simple HTML-based reports with statistical information. Target Audience Older, younger or cognitively disabled persons with little experience on modern computers who are overwhelmed and confused by the features contained in a standard e-mail client like Mozilla Firebird or Microsoft Outlook. Provided Documentation We have provided two PDF files. The first is the output from the conceptualization contest "My Parents E-mail" (conceptulaization_document.pdf) web application. The second is feedback from the Advisory board called sdc_mpecomm.pdf. We are only concerned with the e-mail portion of this solution. Pages specifically: - 2-6: General Overview - 8-11: General e-mail functionality - 12: The Assistant Application - 13: Admin Application If you have questions, these two documents will likely contain the answer you are looking for. However, please feel free to post to the forum, the client is happy to clarify any point. Keep in mind that these screens may be branded. Your wireframes should NOT be branded in any way. Please refer to the Wireframe Requirements section below. Wireframe Considerations When designing your wireframes, ask yourself questions that the user is likely to ask when using this system. This will help with usability/accessibility issues and interaction. Some examples: - How will the user most commonly use this application? - What are the most used features? - When creating an e-mail, what will the user want to do next? What should be accessible, available? - How should the user be able to navigate through the application? - Would a progress bar aid in the experience? What other cues can be added for the user? Wireframe Requirements - Wireframes should NOT address design - Wireframes are meant to provide content, convey the hierarchy of information and show content groupings. - Provide an intuitive user experience - Analyze navigational possibilities and make recommendations - The amount of pages/screens is up to you, but should be less than what is currently being used - Wireframes must only be black, gray and white - color can be used for information call-outs - Wireframes must address the user interface as well as the flow of the application - Wireframes must be linked appropriately for page flow and interaction Wireframe Resources - Wireframes on Wikipedia: http://en.wikipedia.org - Wireframe software option: http://www.axure.com - Example Wireframe: http://www.gdoss.com/web_info/web-site-wireframe.php Wireframes can be built in HTML, Axure (listed above), MS Visio or OmniGraffle. The source files types are not critical in this contest. The most important point is that all the content in listed and the pages are linked together to show page flow. Judging Criteria Your submission will be judged on the following criteria: - How well your wireframes provide a consistent user flow - How well you implement the required screens and any suggestions, interactions and user flow you recommend. Preview Image Please provide a screenshot of the email client as your preview image. Do not alter, skew, modify or add drop shadows or other design filters for dramatic effect.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.