Challenge Overview
Welcome to the "IBM - Lost and Found Mobile HTML Prototype Challenge". The goal of this challenge is to create mobile HTML5 Prototype application based on provided storyboards from client. The prototype must follow best practices for HTML application since we will develop the prototype as hybrid apps for ios and android platform. 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.
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 targetted 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.
Competition Task Overview:
The main task of this competition is to develop HTML5 prototype based on the provided storyboard designs. Your prototype must work properly in all the required browsers. We're only concern about mobile browser since this apps will run in mobile devices, especially for ios and android.
Required Pages:
01. Login Screen
- Reference screens "01 Login.png" and 0"2 Login_Error.png"
- By default this screen will appear for the first time when user open the apps.
- User needs to enter their IBM credential first before able to use the apps.
- If user provide wrong credential or forgot to enter one of the login fields, error screen will appear.
02. Report List Screen
- Reference screens "03 Default_Report List_All.png to 10 Report List_Found List.png", Filter Case Scenario folder.
- After successfull login, user will be redirected to this screen.
- User can view all list (lost and found) unfiltered based on latest report creation.
- Touch/Tap the hamburger menu will open "04 Menu.png".
- User can create new report from menu or by clicking "+" button on top right of the screens.
- User can filter the list view by touch "All" button. by doing this, user can see "found", "lost" or "all" report list.
- User can do advance filter, check "Filter Case Scenario" folder for more details about it. Only 3 filters criteria available, Date, Location, Category, remove Alphabetic filter from this section.
- Filter needs to be working, when user select "lost" or "found" or from advance filter, the filter needs to be working.
03. Report List Lost/Found Details Screens
- Reference Screens "11 Report List_Found List_Detail.png", "12 Report List_Found List_Detail Poster.png", "15 Search Lost iPad_Detail.png".
- User can see details of Lost/Found report from this screen.
- There are several information will be presented in this screen :
* Section of report type "lost" or "found"
* Date of report creation
* Name of Item Lost/Found
* Description of item
* Location of item lost/found (from list of IBM office - use dummy content for the list)
* Date of Item Lost/Found
* Notes
* Button to see Contact information.
- Touch button to see Contact Information will bring user to Detail poster information "12 Report List_Found List_Detail Poster.png".
04. My Reports Screen
- Reference screens "17 My Reports.png", "18 My Reports_Swipe Menu.png".
- User can access this screen via report list screen -> My reports tab.
- This screen will listed all reports created by user.
- User can swipe each list reports and do some updates to their report, edit the report, or marked the item which lost/found as "returned".
- User also can delete their report if the item has been returned.
05. Search Screen
- Reference screens "14 Search Lost iPad + Result.png", "16 Search Found iPad + Empty Result.png".
- User can do searching by click/tap magnifying glass icon in report list.
- User needs to define what kind of report they want to see, lost, found or both of them.
- There will be textbox to enter user search criteria (14 Search Lost iPad + Result.png) and show the result if any match report available.
- If after user enter their search criteria and no report founds, apps should letting the user knows about it (16 Search Found iPad + Empty Result.png).
06. New Item Lost/Found Report Screen
- Reference Screens "19 Post Report Found.png to 25 Post Report Lost_Data Filled.png".
- User can create new report from hamburger menu or by click/tap "+" button. There are 2 type of report that user can create, Lost or Found item reports.
- For found items, user will be able to keep the records for particular time (for example, 1 year).
- For lost items, there is no limit for keeping the records in the apps.
- User needs to enter detail information about the items, flow for enter the information available from "19 Post Report Found.png" to "25 Post Report Lost_Data Filled.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 for this contest.
Browsers Requirements:
- Firefox, Safari & Chrome Mobile Browsers
- Android Browser.
Documentation Provided:
- Storyboard and flow documents can be found in forum!
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.