Challenge Overview
The main task of this project is to create Medical Form - iPad Application UI Prototype Challenge based on the provided PSD Storyboard design. In this prototype, we need you to develop the prototype that works in Tablet Platform (we need both orientations landscape and portrait).
The prototype must follow our standards and our guidelines, review the details below.
NOTE: This challenge will leverage Bootstrap (http://getbootstrap.com/getting-started). In the end of this challenge we need solid UI prototype result with best practice solution, that can be updated easily in the future challenges.
As part of this challenge we need you to document your HTML5/CSS3/JavaScript code (using best practices). We are looking for a clear explanation of the code to allow us the ability to quickly update and integrate with future development. We will allow documentation updates during final fixes (but still required).
Tips for Success: Asking questions early and getting Copilot or PM's feedback is very important for the success of this challenge.
Competition Task Overview:
The main task of this competition is to develop an HTML5 prototype based on the provided storyboard designs. Your prototype must work properly in all the required browsers of tablets (landscape and portrait).
CODE REQUIREMENTS:
For this prototype you need follow existing best practices look and feel also the functions from this website page (https://www.lightningdesignsystem.com/).
Key Requirements:
- We would like you to use Bootstrap.
- Test in all the required browsers (see the list below)
- Ensure your submission is clear of HTML and CSS Validation errors and warnings.
- You are provided with standard tablet storyboards, it needs to work in both portrait and landscape orientations
- Remember that this is a Salesforce1 application. The blue header in the design does not need to be developed (example included)
Challenge Assets:
All files for this challenge can be found in the forums
- Storyboard Screens and Source Files (PSD)
Page Requirements:
The following pages are required in your submission on tablet (landscape and portrait) by using responsive design solution:
Note: we have landscape screens only for the main screen, we need all interactions shown in portrait screens to be in landscape screens!
1) Patient List / Selection (01_00_Patient_Selection.png/01_00_Patient_Selection-(Landscape).png):
- This is the screen where user chooses a patient for whom the survey need to be entered.
- User will browse through list of patients.
- Menu and notification icons will be a dummy link.
Within each of the row:
- - Tapping on any part of the patient information section (Name, Address, Phone BU-ACIS#) takes the user to patient details (04_01_Patient_Overview.png)
- - Tapping on “Take Survey” takes the user to Survey Page (05_01_Survey.png)
Search (01_01_Patient_Selection_Search.png):
- Tapping on search icon in 01_00_Patient_Selection.png, should expand to show the search textbox (01_01_Patient_Selection_Search.png).
Filter (01_02_Patient_Selection_filter.png)
On the Patient List / Selection page, show this modal pop up! The filter should include the following:
- - - filter by ascending or descending
- - - filter by BU# - This is a 2 digit input box
- - - filter by ACIS# - This is up to a 6 digit input box
- - - filter by both BU# & ACIS# - a checkbox to combine the 2 numbers. This number would look like 12-123456 on a patient record. As seen in the mockups.
- On tapping “Done” or “Cancel” should hide the modal window.
2) Patient Details (04_01_Patient_Overview.png):
- User will reach this screen, when a user taps on the patient information section in 04_01_Patient_Overview.png
- Below the navigation icon, we have a back and patient’s icon - this takes the user back to patient list screen.
- Clicking on “Take Survey” button takes the user to survey screen (05_01_Survey.png).
Tabs:
- We have four Tabs in this screen, follow the storyboards for contents under these tabs
Overview (04_01_Patient_Overview.png/04_01_Patient_Overview_landscape.png)
- Follow the contents as shown under this tab.
- Make the contents under this tab scrollable, we need to keep the tabs fixed and all contents below these tabs need to be scrollable.
- Tapping on “View All” in “Survey History” takes the user to Survey History tab
- Note: All other blue colored text in this view will need to be “dummy” links.
Details (04_02_Patient_Details.png/04_02_Patient_Details_landscape.png)
- Follow the contents as shown under this tab.
- Make the contents under this tab scrollable, we need to keep the tabs fixed and all contents below these tabs need to be scrollable.
- All blue colored text in this view will need to be “dummy” links.
Notes (04_03_Notes.png/04_03_Notes_landscape.png)
- Create a free text notes input section. With a submit button below it.
- Notes history will be below this section (display last 10 notes)
- - History will contain a Date Title & First and Last Name. Below it will be the note. Use lorem ipsum text.
- - Add “More” button (button style similar to that of "Done" shown in filters) at bottom of the last note to load more notes if available, please show a simulation by having many notes (just repeat the items).
Survey History (04_04_Survey-History.png/04_04_Survey-History_landscape.png)
- This is the same as is seen in the bottom of the overview tab. This view will display the last 10 history information.
- Follow the storyboards
3) Tasks (06_00_Tasks.png):
Currently, we don’t have a way for users to navigate to this screen - so please create this page as a stand-alone page.
- This is a simple page with 2 tabs. Each tab will look similar to the patient list from Screen 1.
- Provide 2 tab (upcoming, past)
- Upcoming tasks will have the survey button available
- Past tasks will not have a survey button.
4) Survey Form (05_01_Survey.png/05_01_Survey_(Lanscape).png):
- This is survey form that a user fills for a patient.
- Below the navigation icon, we have a back and patient’s icon - this takes the user back to patient list screen.
- We will have a overall progress bar in percentage at the top that shows progress based on the data entered in each category/tab.
Survey Category Tabs:
- We have some Tabs in this screen, follow the storyboards.
- We could have many tabs and user will have options to scroll between the tabs by clicking on the scrollbar show on the either side. We would like you to include more than four tabs to show the functionality of these scrollbars.
- Note: Each category can have a sub-sections (05_01_Survey.png), please include sub-sections titles and user will move between these sub-sections and once completed, will move to the next main category.
UPDATE:
In 05_01_Survey.png, as you can see we have sub-sections tabs, we have the left/right buttons to scroll if needed. One thought we had, would be to swipe through the sub-section header, this could allow users to swipe through the survey sub-section quickly. We are looking for your suggestion on what interaction would be best here as our worry is having two navigations on top of each other and having users accidentally click a top nav.
- Note: We want to show the “Next Category” blue button (at the bottom) to be shown only when the user has completed all sub-sections under a particular category (05_05_Next_Category_button.png)
- Under each tab, we have a separate progress bar - this progress bar shows the number of questions that were answered (i.e. if 5 out of 8 questions were answered then we show it as “5/8").
- In the form, on tapping the 6th question (05_02_Survey_6thquestion_tap.png) - when the user selects “Yes” - we show a textbox to type some text, if no is selected then need to hide the textbox.
Categories and questions:
- We need you to come up with different fields / options as shown in the storyboards.
- Most of the fields shown in the storyboard are selectable options (yes/no, rating, multiple choice, etc)
- Drop-down styles need to be shown on clicking the last two questions (style is as shown in 05_03_Survey_Drop-down.png)
Error Style:
We would like you to show how the error screen will look like, when a user forgets to fill some mandatory fields and user hits the “Submits survey” button then we show this screen “05_04_Survey_error.png”.
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 (MIT License) for this contest.
Browsers Requirements
- Firefox, Safar, IE 10+i & Chrome browsers in Tablet.
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.