Challenge Summary
Welcome to the TopCoder Direct Notification Wireframe Contest. This contest is focused on creating a new pages/flow specifically related new features about system notification of TopCoder Direct Web Application.
In this contest we're interested to see some ideas/flow to design how the TopCoder Direct should created. Read more details information below.
Round 1
Your submitted solution for client review.
1). Need a way to display of a message to the user In-Cockpit Notifications.
2) Need an inbox showing messages received.
3) Need a "toaster" for showing shorter messages or parts of messages, letting the user know that a status has changed, but something that will fade away.
4) Need user interface for sending the manual notifications.
Round 2
Final Wireframe Design
1). Need a way to display of a message to the user In-Cockpit Notifications.
2) Need an inbox showing messages received.
3) Need a "toaster" for showing shorter messages or parts of messages, letting the user know that a status has changed, but something that will fade away.
4) Need user interface for sending the manual notifications.
Contest Details
TopCoder has recently introduced the TopCoder Cockpit Direct Application, which allows Customers, as well as Staff, Copilots, etc., to directly engage with the TopCoder processes and Community. This time, we want build system notification for Cockpit Direct.
For this contest, we need your help share ideas/design of this following tasks. fyi: we're welcoming any ideas improve this Cockpit Notification
1) Need a way to display of a message to the user In-Cockpit Notifications.
- Notifications delivered by the system to the user inside Cockpit, if the user preferences delivery method is set to “receive in-cockpit notifications”.
- They are shown to the users their preferences allow to, and might take different forms:
-- A pop up GUI;
-- A visual indication of unread notifications;
-- Via the Cockpit user inbox.
2) Need an inbox showing messages received.
- It could be tagged/filtered potentially. But a way to navigate, read, mark as read and perform some bulk operations without being too cumbersome.
- Need separate inbox page. How this page should looks?
- Users will have the ability to customize the way they would receive or send system or manual notifications.
- Delivery methods are In-Cockpit notifications, email, SMS, etc.
3) Need a "toaster" for showing shorter messages or parts of messages, letting the user know that a status has changed, but something that will fade away.
- This is slightly different than the System Update but could be tied in to task #1.
- The following events illustrate events of notifications need displayed:
- Unanswered contest question older than X hours;
- Unanswered project question older than X hours;
- Unsatisfied contest question older than X hours;
- Unsatisfied project question older than X hours;
- Member complaint about prize;
- Member complaint about deadline;
- Extension request;
- Prize increase request;
- Member complaint about complexity
- Member complaint about technology
- Member complaint about documentation/support
- Member complaint about contest forum support
- Re-appeals.
- Etc. (this category applies to all the events that involve a user post, complaint, request, appeal, etc.).
4) Need user interface for sending the manual notifications.
- Manual notifications are used when the client or copilot needs to be notified about all project events that still need manual intervention by the PM or copilot.
- The start of "Manual Notification" can placed on inbox page
- Content templates will be adopted and used for all notifications.
- Example: this is a standard template:
To Copilot:
Dear [COPILOT FIRST NAME],
Please direct your attention to contest [LINKED CONTEST NAME]. This contest requires your intervention because [REASON].
Your prompt response is appreciated!
Sincerely,
[PLATFORM SPECIALIST NAME]
Target Audience
Topcoder Customer Executive User.
Topcoder Customer Employees.
Topcoder Executives.
Topcoder PM.
Judging Criteria
- How well you create/suggest solutions for Cockpit Notifications.
- Cleanliness of your layout.
- User Experience & Usability.
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
Wireframes should be built in HTML, Axure, MS Visio or OmniGraffle. The resulting files are not critical in this contest. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files (.rp file) out from this submission folder.
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.
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.