BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to IBM - SiBM Internet of Things Assessment Mobile App Wireframe Challenge!

IBMers will use the app when they are with a client and start discussing about the “IoT” (Internet of Things). IoT being a new concept in the market, no one is sure about its currency, relevance and application to the scope.

By using this app the user will answer a few questions and the app will then do a IoT assessment. The IBMer then can share the results with the client and shows him IoT maturity of his organization and how it looks like against larger industry.

Round 1

Submit your wireframe for a Checkpoint feedback:
0. Navigation.
1. Landing Page.
2. Validation Page.
3. Analysis Page.
Notes.jpg: Any comments about your design for the Client.

Round 2

Final wireframe plus any Checkpoint feedback:
0. Navigation.
1. Landing Page.
2. Validation Page.
3. Analysis Page.
4. Recommendation Page.
Notes.jpg: Any comments about your design for the Client.


Challenge Details:
The goal of this challenge is to help users (IBMers) make a IoT assessment for their clients and show them IoT maturity of their organization.

We are looking for wireframe (Axure) solutions based on requirements below. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!

At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow of the application.

Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The app must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all screens mentioned in required new sections below, if any requirement is missing in final submission the client will not take a look at it, so make a checklist for the required screens to make sure you designed all of them.
- Please show us your proposal as a movie or series of wireframes that communicate the user’s intended interaction with your proposed solution.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.

Notes:
- Your solution need use Responsive Design Solution when viewed on Portrait and Landscape view of Mobile device.
- We would like YOU to pay attention to the IBM Design Language: http://www.ibm.com/design/language/
- Your wireframe submission need able to drill down for all page flow.
- Show your wireframe solution on Portrait View. Use this screen size (375px x 663px)
- Feel free to suggest any tools/function that can bring good User Experience for this Mobile Application.

Supporting Documents:
- IoT Questions (IoT Questions v1.xls.zip).
- Samples to help illustrate screen UI and functionality (IoT Visual v1 .pptx.zip).

Definitions:
- IoT: Internet of Things.
- Dimension: Name for each of the corners of the pentagon. There are hence 5 Dimensions.
- Questionnaire: 12 questions asked by the App to the user.
- User: Person using the App.
- User Radar chart: Pentagon picture plotted for the data fed into the App by the user.
- Benchmark Radar chart: Pentagon picture superimposed over the User Radar chart based on the historical data / data repository.  (Please note historical data is not there / very thin at this time).
- Relationship between Questionnaire and Dimension: It is difficult (and will confuse) if a radar chart has to be drawn as a polygon with 12 sides. It is hence proposed to group the 12 questions into 5 Dimensions so a meaningful (and easy to read) pentagon can be presented. Each Dimension will hence have either 2 or 3 Questions. Users should know which Questions have gone into which Dimension group.
- Dimension level: Numerical number associated with each of the Dimensions. Namely: 1 (innermost pentagon) to 4 (outermost pentagon).
- User Dimension Value: Value based on the data entered into related Questions. (can be between 1 and 4). This data is used to plot User Radar Chart.
- Benchmark Dimension Value: Value based on the benchmark Radar Chart.
- User Data: Numerical number associated with the response to each of the questions. There are hence 12 user data. (value generated by the App based on user’s input is between 1 and 4).

Required Screens:
0. Navigation:
- How does the user navigate this application?
- Include navigation that you think fits with this application.

1. Landing Page:
This is the landing page for the application.
- It should very clearly show what user can do with this application and what the application is all about.
- This page should contain basic info to explain features.
- Should contain Start button.

2. Validation Page:
- Should be able to list 12 questions (maybe 6 questions in each screen).
- At the top of the screen, "IoT" should just be a tab.
- Each question should have color band below so the user can place the “cursor” over the right place in the horizontal color band.
- Each question should have right to left navigation, so the user, if required, can find out more about the question by browsing over from right to left (Slide over from right to left to reveal more information).
- User should be able to (in screen 2) visually see all their responses placed over the color band.

3. Analysis Page:
- By placing the cursor over the radar chart’s dimension, user should be able to see which questions in the previous (with the color code of their response) is grouped to that particular dimension.
- The radar chart should have the boundaries colored in line with the color band chart.
- Radar chart’s spider diagrams (two are shown) should have transparent shading so, when two are superimposed, they will still be visible.
- Color band should have titles at the left and at the right.
- Color band should display the Assessment number for both the “squares”.

4. Recommendation Page:
- If the color of the circle is “blue”, answer will always be same. E.q., Already there!
- App should be able to generate a PDF report covering the three phases – e-mail ID can be asked here.
- App should also ask the user if they believe that their response should be a part of the Benchmark. (e-mail to be asked if not yet provided as a part of previous point)
- When a user does right to left navigation for any of the recommendation, user should see two color rounds with score : one reflecting their response and another benchmark score.

Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn

Target Users:
- The target audience for this application will be IBM employees.

Judging Criteria:
- User Experience of IoT Assessment App.
- Completeness and accuracy of the wireframe as defined in the spec requirements.
- How well your wireframes provide a consistent user flow.

Submission & Source Files:
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

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.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30050882