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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to “Campus Internal Crowdsourcing Platform UI/UX Design Challenge”, in this challenge you will be working on creating the user interface for  a modern and intuitive internal crowdsourcing tool to post simple and moderately complex tasks and ideas; where qualified contacts from the company can pick the tasks and deliver them in a timely manner.  The requestor can create the tasks on the tool and the worker can pick the tasks from the pool and deliver them.

Round 1

Please provide the following screens for checkpoint along with your clickable Marvel prototype with hotspots.
1) Login (Requestor and Worker)
2) Landing (Requestor and Worker)
3) Task Detail (Requestor and Worker)

Round 2

Please provide the following screens with checkpoint feedback incorporated for final review along with your clickable Marvel prototype with hotspots.
1) Login (Requestor and Worker)
2) Landing (Requestor and Worker)
3) Task Detail (Requestor and Worker)
4) Submit Work (Worker)
5) Profile Page (Worker)
6) User help page (Requestor and Worker)
7) UI Kit Generic
 
This project will be developed as a Web based application, specifically to be used in desktop/laptop computers; so no mobile experiences are required.
  • You will be focused on creating the whole user experience from the login to the submission and review of the work. We welcome your creative ideas !!!
  • As information, this web application will be developed using Material UI, so have this technology in mind while designing your UI.
  • We expect to see High Fidelity design, this means your design should be ready to develop a production web application.

User Roles
For this web application there are basically two main user roles:
- Requestor: Person in charge of creating, assigning and reviewing the tasks.
- Worker: Person who will perform the task.

Required Screens / Functionalities

1) Login (Requestor and Worker)
You must design a modern login page following the colors provided in the branding section of this challenge.
This screen will be accessible for both “Requestor” and “Worker” users.
  • Add the most common login features on this screen:
  • Email
  • Password
  • Recovery password
  • Submit/Login button
  • Do not add any social media connection


2) Landing (Requestor and Worker)
Once the users successfully access this web application, they must be able to see a dashboard looks like page with the following information:
  • Main navigation with access to application features
  • List of Task created / available
  • Think on search, filtering and sorting features such like: date, trending, active/inactive, deadlines, type, etc.

There are two main different actions to perform by each user on this page:
A) Requestor
  • This user can Create/update/Delete task
  • Activate/inactivate tasks
  • View additional overall stats: # of workers, # of submissions
  • Assign tasks to X Worker in particular.

B) Worker
  • Access the tasks, no edit options available
  • Tasks should be visible only for the Worker who have that skillset in their profile. For example: a ReactJS related development task, should be visible only for a worker who has this skill marked in their profile page.
  • No overall stats

Both users needs to see a notification panel on this screen. This feature will have the following:
  • Reminders about tasks
  • Submission notifications
  • Task assignment notifications
  • Messages notifications when a task is assigned, completed, ready for review.

- How should this notification be accessible? Propose the best UX here.
- For both users, what other actions would be nice to perform and what other information is needed here? Propose your ideas!
- You need to show these two different user scenarios in your design.


3) Task Detail (Requestor and Worker)
Both users should be able to see the details of the task. Think this page as a resume of the task itself where workers can see:
  • Detail of the task
  • Supporting material in any format: PDF, Video, Audio,Images, Slides Deck, etc.
  • Deadline and Status
  • Workers assigned

- Requestor users can also be able to edit the task directly from this page.
- If a task is not completed a Requestor should be able to release the task to pool again and setup the new deadline (Hours and dates).
- Workers should be able to submit their work from this screen, so how the submission features should be accessible? Propose the best UX here.


4) Submit Work (Worker)
Once the work is completed, a worker should be able to easily submit their work using a very simple step by step platform.

Think on a very intuitive page with the following features:
  • Work files
  • Comments
  • Upload confirmation messages
  • File edit: Upload new files, remove old files, etc.

5) Profile Page (Worker)
This page will be visible only for the workers. In this page they should be able to add their skillset (This will affect how many tasks they will see in the listing pool). Think on any feature that matters for a profile page such like:
  • Preferences
  • Alerts and Notifications
  • Profile Picture with description
  • Email / Password settings
  • Tasks historical
  • Overall task performance stats


6) User help page (Requestor and Worker)
This page will be similar to a FAQ page, where Workers and Requestors can find any necessary documentation and information about the usage of this platform. Resources can be published here as well. Keep this screen simple and easy to use.


7) UI Kit Generic
This will be a generic page used for development, so you will need to provide a full set of most commonly used UI elements. For example:
  • Alerts like errors, warning, success etc.
  • Selects and Dropdown boxes
  • Radio and Checkboxes
  • Texts and paragraphs style
  • Forms and Buttons

Form Factors
Please make sure your design supports these form factors:

In-scope
- Desktop Web application: 1280px minimum width and height increased when needed.

Out of scope (DO NOT DESIGN)
- Tablet Design
- Mobile Design

Operating Systems
- Desktop Web Browsers

Branding Guidelines
- Branding guidelines will be posted in the challenge forum.

Final Deliverables
- All original source files.
- Files should be created in Adobe Photoshop and saved as a layered PSD file, Adobe Illustrator or as a layered AI file, Sketch or Adobe XD.

Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please check forum for Marvel requests
- You MUST include your Marvel app URL as a text file in your final submission labeled “MarvelApp URL” (in your marvel app prototype, click on share and then copy the link).

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:

2020 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

  • Layered PSD files created in Adobe Photoshop or similar
  • AI files created in Adobe Illustrator or similar
  • Vector EPS files created in Adobe Illustrator or similar
  • Sketch
  • Adobe XD

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30126376