Challenge Overview
Project Overview:
Welcome to the Asclepius - Support Cases UI Prototype Challenge! The goal of this challenge is to create an HTML5 Prototype for mobile-based application on provided storyboards for Asclepius Mobile Application. The prototype must follow our standards and our guidelines. Please see more details below.
The main task of this project is to create the UI Prototype based on the provided Storyboard design by re-use existing best practices look and feel also the functions of HTML5 mobile and tablet.
This UI Prototype will use Responsive Design solution that will works within Mobile Platform. You must use mobile web HTML5 best practices so it will looks good in targeted device. Read more details for UI Prototype Requirements and Flow below.
As part of this challenge you will need to document all HTML5/CSS3/JavaScript code. We need clear explanation of the code to help us figure all the HTML5/CSS3/JS code functions and make it easier for future developers and the client to understand what you have built.
Tips for Success: Asking questions early and getting Copilot or PM's feedback is very important for the success of this challenge.
CODE REQUIREMENTS:
HTML5
- Provide comments on the page elements to give clear explanation of the code usage. The goal is to help future developers understand the code.
- Please use clean INDENTATION for all HTML code so future developers can follow the code.
- All HTML code naming should not have any conflicts or errors.
- You’re encouraged to use HAML to make the HTML code clean, and provide source files on your submission.
- Each of the HTML pages need adapted both difference of tablet and phone layout.
CSS3
- Provide comments on the CSS code. We need CSS comments to give a clear explanation of the code usage. The goal is to help future developers understand the code.
- Please use clean INDENTATION for all CSS so developers can follow the code.
- All CSS naming should not have any conflicts.
- As possible use CSS3 style when create all styling.
- You’re encouraged to use LESS/SCSS or SASS to make the CSS code clean, provide source files on your submission.
- You MUST use CSS media query for tablet and phone
IMAGES
- Images should be properly compressed while still having good visual quality.
- Please use best practice repetition usage of background based image.
- Please use sprites when using icons for your submission.
- You need make sure all images support Retina display
JAVASCRIPT
- We encourage you use the latest technology javascript library and framework of Jquery.
- Bootstrap is allowed.
- AngularJS is allowed.
Required Pages:
Required Pages:
1) Landing Page:
Mobile View:
- 01-Landing-iphone.png, 01B-System-message-hide.png, 01C-System-message-hide.png, 01D-Landing-iphone-hide.png & 01E-Landing-iphone-hide.png.
- Navigation, messages and alerts are dead links.
- Blue header will be fixed at top when scroll page, also top tabs (Open Cases, Closed Cases & Hidden Cases) should be fixed at top as well.
- Duplicate the content of Open cases for Closed and Hidden cases.
- Capture the swipe functionality to hide system message and alert (01B-System-message-hide.png & 01C-System-message-hide.png).
- Swipe left will display the right action buttons.
- Swipe right will swipe back.
- Only one row could be swiped, if user swipe other row, previous row will swipe back.
- If user tap top right "Done" link we will swipe back.
- If user clicks "hide" should we hide the row.
- Capture the swipe functionality for cases (01D-Landing-iphone-hide.png & 01E-Landing-iphone-hide.png).
- If user clicks on a case (whole row) he will be redirected to view case page.
- If user clicks on Create a case he will be redirected to create a case page.
- Start a chat is a dead link for now.
- If user clicks on call support he will be redirected to call support page.
Tablet View:
- 06-Landing-ipad.png, 06B-System-message-hide-ipad.png, 06C-System-message-hide-ipad.png, 06D-Landing-hide-ipad.png, 06E-Landing-hide-ipad.png.
- Same functionality like mobile.
2) Create a Case Page:
Mobile View:
- 02-Create-case-iphone.png, 02A-Create-case-validation-iphone.png &03-Articles-iphone.png.
- Subject and Description are required fields.
- Type is a drop down list; you can use dummy data to fill it out.
- After user clicks submit he will be redirected to suggested articles view (03-Articles-iphone.png).
- The 3 articles are dead links.
- If user clicks on “Continue to submit case” button he will be redirected back to Landing page.
- If user clicks on “Call support center” button he will be redirected to call support page.
Tablet View:
- 07-Create-case-ipad.png, 07A-Create-case-validation-ipad.png & 08-Articles-ipad.png
- Same functionality like mobile.
3) View Case page:
Mobile View:
- 05-View-case-iphone.png, 05A-View-case-iphone.png, 05B-Case-comment-iphone.png & 05C-Activities-iphone.png.
- Mark as resolved, Hide case and escalate case are enabled when the case is still open (05-View-case-iphone.png).
- Mark as resolved, Hide case and escalate case are disabled when the case is closed (05A-View-case-iphone.png).
- Mark as resolved, Hide case and escalate case are dead links.
- When user clicks on Case Comments links he will be redirected to case comments view (05B-Case-comment-iphone.png):
-- Will Smith, Reply and Delete links are dead links.
-- Back arrow will take you back to View case page.
- When user clicks on Activities link he will be redirected to Activities view (05C-Activities-iphone.png):
-- Will Smith and Right arrow are dead links.
-- Back arrow will take you back to View case page.
- Green footer is fixed at bottom.
Tablet View:
- 09-View-case-ipad.png, 09A-View-case-ipad.png, 09B-Case-comment-ipad.png & 09C-Activities-ipad.png.
- Same functionality like mobile.
Specific HTML/CSS/JavaScript Requirements:
HTML/CSS Requirements:
- Your HTML code must be valid HTML5 and follow best practices
- Validate your code - reviewers may accept minor validation errors, but please comment your reason for any validation errors. Use the validators listed in the scorecard.
- Use CSS to space out objects, not clear/transparent images (GIFs or PNGs) and use proper structural CSS to layout your page. Only use table tags for tables of data/information and not for page layout.
- No inline CSS styles - all styles must be placed in an external style-sheet.
- Use semantically correct tags - use H tags for headers, etc. Use strong and em tags instead of bold and italic tags.
- Element and Attribute names should be in lowercase and use a "-" or camel naming to separate multiple-word classes (i.e.. "main-content", or "mainContent)
- Label all CSS, JavaScript, or HTML hacks with explanations so others will understand.
- Your code must render properly in all browsers listed in the scorecard in both Mac and PC environments.
JavaScript Requirements:
- All JavaScript used must not have any copyrights to any third party. You are encouraged to use your own scripts, or scripts that are free, publicly available and do not have copyright statements or author recognition requirements anywhere in the code.
- You are allowed to use JQuery for this contest.
Browsers Requirements:
- Firefox, Safari & Chrome Tablet Browsers
- Firefox, Safari & Chrome Mobile Browsers
Documentation Provided:
- Storyboard Screens and PSD files can be found in forums.
Note: The provided screens are for retina display, we need to support both normal and retina displays.
Final Submission Guidelines
Submission Deliverables:
- A complete list of deliverables can be viewed in the UI Prototype Competitions Tutorial.
Final Submission:
- For each member, the final submission should be uploaded to the Online Review Tool.