HK Driver Mobile App Design Direction Challenge

Welcome to HK Driver Mobile App Design Direction Challenge.

The goal of this challenge is to quickly create design direction and inputs for a follow-up UI design challenge. We are looking for you to look over the requirements and proposed features and put together high-level information and visual direction that will become input into the UI challenge. What is NOT the goal? To create high-fidelity designs BUT to focus in on thinking through the problem and proposing a direction for the project. Design Direction is a little bit of Information Architecture, a little bit of UI/UX design work to help inspire the customer and to inspire a future designer of the idea, product, or app.

Important Rule Change for the Design Direction Challenge
You are allowed to submit your designs at any time during this challenge. You are allowed to submit to the final phase even if you did not submit to the checkpoint phase. All submissions will be accepted (that pass screening). 

Round 1

Submit design direction documentation for the checkpoint deadline:

• Throw all your initial ideas here!
• Focus on showing meaningful concept pages/wireframes to receive feedback, NOT the fonts/ colors, icons style (these are secondary to the goals)

Round 2

Submit your updated and final design direction documentation for the final deadline and improved based on the checkpoint feedback:

• All your design direction material!

Challenge Objectives

• Focus on what you think is important in the customer's project and provide design direction back to them on where you think the project should go.
• Create wireframes, sketches or simple designs to convey your design direction.
• Provide guidance on your idea, color palettes, typography, shapes, etc.

Project Background

• This challenge is meant to serve as a precursor to a regular UI design challenge. You can think of it as a “FAST Wireframe Challenge", however, we are not looking for full-fledged wireframes.
• We are also looking for suggestions on Color Palette, Typography & Icons style, and overall notes about the look and feel of the application.
• We’d like to see how you think the application could work, potential workflows and interactions.
• Think of this as a low-fidelity design concepts challenges.

Application Overview

• This mobile application will be used by car owners in Hong Kong and it provides various functionalities including 
  • Traffic alerts
  • Real-time info about traffic
  • Finding spaces and information relating to parking
  • Finding fuel (prices, location, availability)
  • Useful information such as offense points
    • May include fines and penalties
  • Car maintenance and repair services (mechanics, oil, types, m.o.t) 
  • Emergency and recovery services (roadside assistance)
  • Promotions targeting drivers (services relevant to car owners or services applicable whilst driving)
  • Vehicles license status (part of the user profile)
  • etc.
• The major goal of the application is to make the car owner’s life easier at managing all the different aspects.
• The reason behind building this app is becoming first in the market to meet customer-specific needs, tying available existing services to consistent needs drivers have - these features can all already be accessed but not in a   manner / or with an easy tool; specifically maintenance and emergency services. Secondary but not less important, to be able to learn more about the customers we insure, the drivers; to understand them and their needs to be better placed to serve them in the future.
• See the attached PPT Design Workshop asset.

Screens/Features

• The application will cover a considerable big set of features, the whole set of elements related to car driving, sales, service, and maintenance, such as Parking Assistant, Traffic alert, Aftersales service,  Services/promotions, Driving rewards (gamification) and more. What’s the best way to deliver all this information in a fashion that makes sense while keeping it simple (avoid overwhelming the user).
• This is NOT an app to use ONLY while driving, more of an app that helps improve the driving experience by providing the driver with enough information and flexibility.
• Integration vision: no need to design or come up with concepts for each of the mentioned modules in the provided workshop file but your solution should cover the big picture, the vision of how all these modules will be at least displayed/navigated.
• Scope: in terms of required modules, we would like you to explore concepts for Emergency services, Garage/Mechanic services and a third of your choice from the mentioned above.

Deliverables

• We want to make this challenge easy and fast, therefore we are not setting strict requirements on the format of the deliverables you produce. We are recommending you think of how it is presented. So a complete PDF of your design direction or Axure wireframes or a MarvelApp would make sense. Anything that showcases your ideas the best (and makes it easy to follow). 
• These items could include but are not limited to: user flow diagrams, sitemaps, quick wireframes of specific or potentially complex screens, UX research and best practices documentation, and user profiles.
• Make sure to provide all source files as usual created in Adobe PS, AI, XD, Sketch, etc. and all submission files
• If you decide to use Marvel Prototype     
  • Request a MarvelApp prototype from me using this link: https://tc-marvel-app.herokuapp.com/challenge/30098240
  • 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).
• The target device is mobile.

Design Assets

• Folder: https://drive.google.com/open?id=1_R6enGzaWp-hfIrkNCdE7gccibz-py22 
• Design Workshop.ppt: design workshop artifacts and general vision of the application.
• Deliverables Examples: previous ran design direction challenges outcomes for reference.

Target Audience

• Car drivers in Hong Kong. We're targeting the driving population so accessibility is something that will weight heavy. It's important for a broad variety of users to be able to navigate the app with ease.

Judging Criteria

• Execution of your deliverables.
• The usefulness of the deliverables as it relates to the requirements and UI challenge.
• The thoughtfulness of execution of the process for each feature - making a pleasant intuitive user experience.

Stock Artwork (Illustrations, Icons, Photography)

• Stock artwork is allowed for this challenge.
• Stock Wireframe kits (copyright free/free usage) are allowed in this challenge.
• Make sure to declare all your assets properly or you might fail screening.
• You don’t want to fail screening? Read this.