BONUS: 3‌ CHECKPOINTS AWARDED WORTH ‌$50‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the “ACME Feature Request Form - Responsive Web Design Challenge”! In this challenge, we are looking for you to create the UI design for feature request form for both admin and user view.

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

Round 1

Submit the following screen requirements for checkpoint feedback:
01) Admin View
02) User View
  • As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
  • Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit the following screen requirements with checkpoint feedback applied:
01) Admin View
02) User View
  • As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
  • Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
  • If you're not submitting in the Checkpoint/Round 1, you are not eligible to submit in the Final/Round 2

CHALLENGES OBJECTIVES
  • Create 2 scenarios for both desktop and responsive mobile.
  • Create elegant, clean, and simple user-centered design with modern design aesthetics.
  • Best practice of color usage, visual comparison, and drill-down charts to highlight comparison
  • The overall design and user experience should be engaging and easy to use.
 
BACKGROUND INFORMATION
  • Our customer is a telecommunication company that is looking for a different design approach for their current feature request form.
 
JUDGMENT CRITERIA
  • Creativity: Impactful; the solution is different or unique from what is already out there and can be implemented.
  • Exploration: Flexible; follow the provided screen requirements section and propose improvements or different paths that positively impact the user goals.
  • Aesthetics: Hi-fidelity design; provide a top-notch finished-looking visual design.
  • Branding: Strict; carefully follow the provided guidelines and stick to them.
 
REQUIRED FEATURES:
  • Intuitive experience for end users to fill out the form request.
  • Allow a different variety of questions to be added/shown for user view.
  • Show response recorded from the form in a meaningful way, eg using charts and summary tables.
  • Design shall be compatible with PrimeNG Sapphire Template Angular 11.
 
TARGET AUDIENCE
  • Admin: company admin who manages the master data of the application, including questionnaire.
  • End User: users who will respond to the questions on the questionnaire.
 
PERSONA 1: ADMIN
  • Name: Bob Stevenson
  • Occupation: Admin
  • Role: Manages master data (add/update/delete). Master data includes the focus areas, questionnaire and the feature details.
  • Pain Points: Basic table that needs lots of effort to analyze.
  • Wants: Easy to use, smart and informative form response.
  • Proposed Solution: Build an interactive and smart form response table.
 
USER STORY 1: ADMIN
  • Bob logs into the system (out of scope) and can manage master data, as well as Bob can see all the responses submitted by end users grouped by focus area with each question and answer from users.
 
PERSONA 2: USER
  • Name: David Harrison
  • Occupation: User
  • Role: identifying features in scope using the form questionnaire.
  • Pain Points: Limited and outdated form questionnaires which are not easy to fill out.
  • Wants: Easy to use and informative form questionnaire.
  • Proposed Solution: Build an easy to use and informative form questionnaire.
 
USER STORY 2: USER
  • David wants to identify the scope (features) with the help of this questionnaire.
  • He sees the list of questions in an interactive way. He responds to the question with a yes or no (could be checkmark, text, radio button), and if his answer is yes, the system shows the feature that shall be in scope.
  • He completes all the required questions and then submits them to the system.
 
SCREEN REQUIREMENTS
For this challenge, we are looking for you to create a set of screens that are easy to use for the following scenarios. Feel free to take creative liberties when designing the screens:
 
01) Admin View
  • Refer to sheet “Master Data”.
  • This is a segregated table which has the Master Data - Focus Area, Questionnaire, and corresponding Features.
  • The questions should be grouped based on the focus area with the option to expand all rows.
  • Show how admins can navigate between each screen.
 
02) User View
  • Refer to sheet “User View”.
  • Think on how to present this view to the user.
  • If the user answers ‘yes’, then potential scope shall appear on the right hand side with details like feature title, feature description, acceptance criteria, and resources.
  • If user answers ‘no’, then right hand side shall remain blank
  • ‘Push to JA’ is a toggle option (could be a check mark or radio button) that shall be given for each feature that appears on the right. 
  • Show how users can navigate between each screen.
 
DOCUMENTATION AND BRANDING GUIDELINES
Check the challenge forum for available documentation and branding guidelines.

TARGET DEVICES
  • Web: 1366 x 768px, with height adjusting accordingly. 
  • Responsive Mobile: 375 x 812px, with height adjusting accordingly. 
 
DESIGN TOOL
  • Adobe XD
  • Figma
  • Sketch
 
MARVEL PROTOTYPE
  • We need you to upload your screens to Marvel App
  • Please request for marvel app in the challenge forum
  • You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment on this link while you upload)
 
SUBMISSION AND SOURCE FILES
Submission File
  • Submit JPG/PNG image files based on Challenge submission requirements stated above
  • MarvelApp link for review and to provide feedback
  • Declaration files document contains the following information:
    • Stock Photos Name and Links from allowed sources
    • Stock Art/Icons Name and Links from allowed sources
    • Fonts Name and Links source from allowed sources
 
Source Files
All source files of all graphics created in either Adobe XD, Figma or Sketch.
 
FINAL FIXES
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors.

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.

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.

ELIGIBLE EVENTS:

2022 Topcoder(R) Open

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

  • Sketch
  • Adobe XD
  • Figma

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30257534