Challenge Summary
What is a RUX Challenge?
The RUX (Rapid User Experience) challenge uses the same format as our famous LUX Challenge except it is not "Live" at an event. The RUX Challenge Series provides you with an opportunity to show digital leaders from some of the largest companies in the world just how good your concepting and user experience (UI/UX) design skills are.
RUX (Rapid User Experience) challenges are fast, fun, and have more chances for you to capture prize money!
Note: You do not need to have RUX challenge experience to join this challenge - Just jump in and give it a try! Make sure to follow the challenge details, the challenge forum and ask questions.
The goal of this challenge is to take the provided design problem, analyze the user experience and provide design concepts and visual ideas on how the application might look and work!
Design Problem
We are looking for a web application interface and a set of screens to track ships and vessels over time. We want to detect anomalies or inaccuracies in a ship's coordinates, speed, direction, etc. We also need the ability to send AIS (text) messages to a single and/ or multiple ships at once. We are looking for fresh concepts and ideas on the UI/UX interactions for this application experience.
RUX Challenge Timeline and Rolling Checkpoint
Submission Start: 02/15/2017 at 12:00 PM EDT
Rolling Checkpoint Start: 02/17/2017 at 12:00 PM EDT
Submission End: 02/18/2017 at 12:00 PM EDT
We are offering 5 Prizes Placements
1) 1st Placement: $2000
2) 2nd Placement: $1500
3) 3rd Placement: $1000
4) 4th Placement: $750
5) 5th Placement: $500
- Plus 8 placements for Rolling Checkpoint prizes @ $50 each!
Note: Important Rolling Checkpoint Details
- Customer, adroc and tgerring will be available for early submissions and Rolling Feedback!
- We will answer questions and provide Rolling Feedback as fast as possible.
- You must watch the Forum for your feedback!
*All initial qualifying checkpoint submissions will win $50 (8 Placements)
Design Consideration
- Clean and streamlined design and user flow
- Easy to monitor and view data
- AIS messaging system should be simple to use but robust enough that the user can use the functionality in multiple ways and for different scenarios
- Show us concepts and ideas for how things could be designed and function. Maybe it is one screen (dashboard) with overlays and flyout windows. Maybe it is multiple screens and panels for different kinds of functionality and tasks. We are open and looking for your ideas and solutions.
General Requirements
- This application is going to be developed as a Desktop Web Application
- Screen Sizes:
-- Desktop Standard (1366px by 768px - Landscape)
Branding
- Branding is completely open
- This should be a serious/useful designed application
- We are looking for concepts and ideas
Downloads
- See challenge forum
Required Screens/ Functionality
1) Dashboard Concepts
- Default screen that user will see in the application
- This screen will have several functions:
a. Ability to drag ships onto a map (google maps or mapbox fine)
-- The focus here is on the ocean, not land���
-- The user should be able to name a ship
-- Show its starting point (where it's placed on the map)
-- Set its trajectory (direction) and speed
-- There could be a minimum of 1 ship, but as many as 100
-- The goal is to show chaos, lots of ships with crossing paths, different speeds, different size ships (aircraft carrier vs. freight ship vs. small transport boat)
-- Ability to name and show different kinds of ships (aircraft carrier, freight ship, pilot vessel, tugs etc.)
-- Visually represent these different kinds of ships somehow.
b. Timeline scrubber/ view
-- The user should be able to see a timeline of all of the activity of the ships on the map
-- Think of this like a video editing software timeline
-- The user should be able to move the timeline scrubber 6 hours into the future and see where all their ships are, what their paths are, any conflicts, issues or inaccuracies
-- Changes in a ship's position, trajectory, speed, etc. could be indicated as a "keyframe" or signifier on the timeline. This is a visual cue for the user that something about that ship has changed or need to be changed/ correct
-- Timeline should include Play and Stop buttons
c. Show Inaccuracies
-- An inaccuracy could be something like "a ship is now suddenly in the middle of New York City instead of in the Pacific Ocean"
-- This could indicate that the ship's command software has been hacked.
d. Send and receive AIS Messages
-- There are 26 different types of AIS messages
-- AIS messages are basically just a specially formatted text message
-- And AIS message can include a regular message along with the ship's coordinates
-- The user should have the ability to send a single message to a single ship. OR a single message to multiple ships at once. OR different messages to different ships
2) Any Additional Functionality or Screens
- Show us concepts and ideas for how things could be designed and function.
- Maybe it's one screen with overlays and fly out windows?
- Maybe it's multiple screens and panels for different kinds of functionality and tasks?
- Could the AIS messaging system be a separate screen that allows the user to craft multiple messages at once?
- We are open and looking for your ideas and UX solutions. You do not have to stay with just the "dashboard" idea if you think there is a better solution.
3) UI/UX Interaction(s)
- Make sure you are showing us how things work
- What happens when a user clicks a button, where do they go
- How does the user interact with the timeline to view future states of the ships
- Make sure you are thinking through these interactions and show us your ideas for how they work.
4) Marvel Prototype
- We need you to upload your file into Marvel App.
- We want to use Marvel App to provide direct and fast feedback! We can also track your design updates and screen versions within Marvel App!
- No additional functionality is required! Just make sure your screen(s) are in the correct viewing order (number them 00, 01, 02, 03, etc.)
- If you do not have access to the Topcoder Marvel App Account please contact adroc@topcoder.com or fajar.mln@gmail.com
- You must include your Topcoder Marvel App URL within your .Notes file
5) Presentation Screen - 1920x1080 (16:9 Ratio)
- In a RUX challenge, this screen is the way to showcase your concept so keep it simple and make it look good!
- If you were walking into a meeting and needed to sell your idea - use this screen to showcase your concept.
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- Overall design and user experience
- Cleanliness of screen design and user flow
Target Audience
- Command center employees
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
Submit JPG/PNG for your submission files.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as a layered PSD file, or Adobe Illustrator as a layered AI file 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. We may ask you to update your design or graphics based on checkpoint feedback.
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.