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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the Autopilot - Navigation Mobile AR App Design Concepts Challenge. In this challenge, we are looking to create a Mobile AR (Augmented Reality) App that will be used for assisted navigation for the indoor and the outdoor environments and there will be very little or no reliance on GPS

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!

Challenge Objectives
• Mobile Application
• 5 (or more) unique screen views
• Concept Design

Round 1

Submit your initial designs for the checkpoint review. Feel free to add any screens which are necessary to explain your concept:
01 Onboarding Users
02 Search Hotspots
03 Navigation

- 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 your final designs plus checkpoint feedback implemented for the final round. Feel free to add any screens which are necessary to explain your concept:
01 Onboarding Users
02 Search Hotspots
03 Navigation
04 World in Miniature
05 Elevator Mode
06 Destination Reached

- 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.)


APPLICATION OVERVIEW
What is Autopilot?
AR technology has been improving in the last few years. Since modern AR Software scans the physical environment in real-time and keeps track of the position and rotation of the equipment within the scanned environment, it can also be used to keep track of where the user is located and oriented in the physical space. Data can then be used to help guide or visualize the information needed for a user to navigate that space.

Autopilot is a proof of concept mobile app to explore how AR can be used for assisted navigation (indoor and outdoor) while relying heavily on computer vision libraries like ARKIT/ ARCORE and with very little or almost no reliance on GPS.

Autopilot shall be developed primarily for iOS. Development can happen either natively (preferred) or on a game engine like Unity3D

AUDIENCE
Target Audience are the employees of Autopilot and this will be used by people who are not familiar with navigating in the facility - this app will help them navigate

DESIGN GOALS & PRINCIPLES
Below are some of the goals:

  • This will be a native app, should be designed specifically for the iOS platform

  • We have provided wireframes to help you get started, this is just for reference - please do NOT copy.

  • Elegant, clean, simple, user-centered look and feel with a modern aesthetics

  • The overall design and user experience

  • Engaging and easy-to-navigate UI

  • How well does your design align with the objectives of the challenge

EXPLORATION SCORE
In terms of expectations, we would like to measure the concept against the following in the one to ten scales (ask the client to rate each of the parameters):

  • Creativity: 8

    • 1: barely new ideas

    • 10: a utopic product with features not proven to be able to be fully implemented

  • Aesthetics: 10

    • 1: low-fidelity design, wireframe or plain sketch

    • 10: top-notch finished looking visual design

  • Exploration: 8

    • 1: strictly follow an existing reference or production guideline

    • 10: open to alternative workflows/features not listed here that would help the overall application

  • Branding: 7

    • 1: don’t care at all about the branding just functionality

    • 10: without a properly branded product there is no success


REQUIRED FEATURES

  • Prescan - Map Creation: Scan Location to create a digital twin of the location (’see’) and save it in the cloud (‘memorize’). Also create points of interest during the scan (User-generated).
  • Initiation (Localizing & Listing Points of Interests): Localize the user in the pre-scanned digital twin. Automatically show a list of points of interest (fire extinguisher, emergency exits, main power switch, main water tap) around the user to be picked as a destination.
  • Navigation - Turn by Turn experience: Provide Augmented turn-by-turn navigation to the chosen destination. There might be possibilities of taking stairs, Elevators, and Escalators on the route
  • Nearby Points of Interests (Nice to have - optional): While navigating to your chosen destination, App will show other important Points of Interest on the way, when you pass them by. Each Point of Interest Label can have a description and an icon.
  • Warnings (Nice to have - optional): Show Instructions of Warning/ Caution. (Do not enter/ Work in progress etc.)
  • ���Show Time/ Distance to Destination (Nice to have - optional)
  • The world in Miniature (WIM) (Nice to have - optional): Life-sized real or virtual objects represented in a miniature digital twin. Show Live update of where the user is located in building visualized in this miniature digital twin.
  • Elevator Mode: App uses this mode when navigation within the building/route demands the use of an elevator to reach the destination.

SCREEN REQUIREMENTS
For this challenge, we are looking for the below screens to be created in your submission. The functionality details listed below need to be included in your solution:

Navigation
01 Onboarding Users
Reference: Page 7 in Autopilot Wireframe.pdf

  • Show animation to teach how to scan the space and look around.
  • Show anchor points as dots, to give feedback for scanning in progress
  • Once Localized, show the name of the location (for ex: J.H.H Pediatric Cardiology) and also allow the user to search for a hotspot within that location.

02 Search Hotspots
Reference: Page 8 in Autopilot Wireframe.pdf

  • When the Search Field is tapped, Show nearby hotspots in the dropdown, open up the keyboard for input.
  • Show us how the user will initiate the search and how we need to display the search results
  • Please do not copy the wireframes provided it is just for reference

03 Navigation:
Reference: Page 9 in Autopilot Wireframe.pdf

  • Top Bar shows selected destination, Distance left, Time to reach and stop the navigation button
  • Other Hotspots on the way to their destination are depicted.
  • Floating directions signs at each major turn
  • We thought of a couple of ways on how the navigation can be shown:
    • Maybe we can draw the Navigation route as a line. Have a shader drop the opacity of the line as it goes farther away.
    • (OR)
    • Show the Navigation path as a series of dots. Nearest Dot becomes an arrow.
    • (OR)
    • If you have better ideas for navigation, feel free to show them.
  • Either way, we would like to have floating directions signs at each major turn.
  • Include a world in the miniature map showing the user’s present location on the route

04 World in Miniature
Reference: Page 10 in Autopilot Wireframe.pdf

  • When the World in Miniature (WIM- Orthographic representation of Scanned Data) is tapped, show a bigger version of the WIM.
  • Tap on the top part of the WIM to minimize it back.

05 Elevator Mode
Reference: Page 11 in Autopilot Wireframe.pdf

  • When the route demands the use of an elevator to reach the destination then:
  • Navigate the user to the nearest elevator, ask him to take the Elevator to the required floor.
  • When there is a drop/increase in height in the AR Session, Show a Card to get off at the required floor.

06 Destination Reached
Reference: Page 12 in Autopilot Wireframe.pdf

  • Once the user reaches the destination - show a different colored dot, and also a floating Hotspot of the Destination.
  • Remove the Time and Distance parameter from Top navigation bar, and replace with the word “Arrived”
  • Use Haptics and Sound to denote the success alert

IMPORTANT

  • Keep things consistent. This means all graphics styles should work together

  • All of the graphics should have a similar feel and general aesthetic appearance

BRANDING GUIDELINES

  • There are no branding guidelines, it is open to the designers.

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)

TARGET DEVICE

  • iPhone X/iPhone 11 Pro: 1125px x 2436px

SUBMISSION AND SOURCE FILES
Submission File

  • Submit all JPG/PNG image files based on Challenge submission requirements stated above

Source File

  • All source files of all graphics created in either Adobe Photoshop, Illustrator or XD or Sketch or Figma and saved as an editable layer

Declaration File  

  • Declaration files document contains the following information:

    • Stock Photos Name and Source Links from an allowed sources

    • Stock Art/Icons Name and Source Links from an allowed sources

    • Fonts Name and Source Links source from an allowed source

    • MarvelApp share link for review 

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.

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
  • Sketch
  • Adobe XD
  • Figma

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30126888