Challenge Summary
Welcome to Renesas - Vehicle Market Mobile App Concept Design Challenge.
Recently we ran an ideation challenge to explore possible solutions for building an application that uses a failure prediction technology (owned by the client). The winning idea proposes to enable an online vehicle market over blockchain. Users must engage this innovative environment seamlessly introducing concepts of market (buy/sell), failure prediction and suggestions systems. We need your help to bring this idea to life through a mobile app!
Best of luck.
1. Dashboard
3. Vehicle Details
4. Failure Prediction Report
6. Offer Details
- Please provide a MarvelApp Presentation (see details below).
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
1. Dashboard
2. Vehicles
3. Vehicle Details
4. Failure Prediction Report
5. Offers
6. Offer Details
7. Insurance
- Please provide a MarvelApp Presentation (see details below).
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
The goal of this competition is to come up with the look and feel of a mobile hybrid application for the automobile industry supported by Blockchain behind the scenes. The application should work and look well on both iOS and Android system. You are provided with user stories and existing mockups to follow as rough reference.
Concept Design Goals
Most persons face some uncertainty problem when buying an used car. Legit history of the vehicle is barely available. Determining when to sale a vehicle might be also an issue for users, since it’s hard to estimate the “perfect” timing considering the value of the vehicle at certain period of time from now. The solution (see Idea doc) relies on the support of blockchain technology to solve these main issues, among others.
The application will serve features such as market comparisons, buy/sell management, improvements system, prediction system and others to provide the user with useful information in order to make decisions.
The most important features you need to keep in mind:
- Failure Prediction Report. The reasons lay down in the fact that the Failure Prediction Report is based on the information of Parts Details; as well as it affects the related services such as "Insurance" recommendation.
Solution Considerations:
- Page hierarchy must not be deep.
- Application must not be complicated (e.g. navigation, discoverability, affordances).
- DO NOT use lorem ipsum for content/descriptions (parts, history, accidents, alerts, etc). Please research and use realistic information, as much as possible. This will help you get into the top. HOWEVER, there is an exception with the realistic information: DO NOT use real brand neither car model names. For example, instead of “Kia Rio” brand-name: real (DON’T), you can use something fake such as “Kobra Phoenix” brand-name: fake (DO).
- Remove brand and model from the photos you plan to use. Vehicles shouldn’t display any reference to real branding. Blur them out or hide them somewhere.
- Mockups are just a rough reference. Please improve the features, add new features, rethink the mockups.
We expect the final design will be unique, like no other, alongside with a modern style, sophisticated. Designs which not follow a simple reskin/copy of the provided mockups will have advantage during the judging process, so DO NOT just copy the mockups, think out of the box. Keep in mind we definitely do not want to see over data-crowded designs, childish/cartoonish looking.
Supporting Documentation
- Solution background: ideation challenge winner.
- Mockups: rough reference and initial state of the flow proposal (to be improved by you).
Screens Requirements
Overall
- Please suggest how to organize this content and group them into screens, we are looking forward to see your unique proposals, be bold. The following screens and mockups are just initial suggestions but we think content could be organized in a different way, go for it!
1. Dashboard
User has an high summary view of the system. Initially, we propose to display overall amounts and charts that provide a quick summary, alongside with links to other sections. We are open to ideas about how to group and display this information and overall navigation.
The dashboard must support the following features:
- Ability to toggle sale availability of “my vehicle”. If user clicks this toggle (open for sale) the car would become available and vice versa. The status should change on every toggle.
- Navigation to all the sections of the application.
2. Vehicles
User can see a list/set of available vehicles in the market. User can perform search/filter to narrow down results.
See Vehicle Details section to find information about the items to display (e.g. brand, model, etc). Use it for the listing and search parameters.
3. Vehicle Details
User can see detailed information about a specific vehicle.
A vehicle features the following information (open to suggestions):
- Brand * the application supports any type of car e.g. sedan, SUV, etc.
- Model
- Year
- Price
- Travel (elapsed distance)
- Photos
- Description
- Status: system prediction insights.
- Parts repair and accidents history (could be separate pages).
Parts, Repair History & Accident History
These sections basically display a thumbnail/icon of the item plus description. Parts the car has historically possessed or changed. Repair or upgrades the car has gone through. And finally, accidents log. Feel free to research about what information could be displayed here to make it realistic.
My Vehicle
It is basically the same page as a vehicle details page but it doesn’t have the “offer” action. Please provide this screen.
4. Failure Prediction Report
This page displays two analysis section. User can see the chart view and also deep details about the information the charts are displaying.
Value Decrease Parts Analysis
- This will show a decrease in value due to damage of each part.
- It represents the value that was reduced to each part, through vertical bars.
- There are three of the vertical bars (the present value, the value after six months, the value after 1 year) on each part.
- It is sorted by present value.
All Parts Health Analysis
- This lists up the health diagnosis result of all of the parts.
- Each part represents the diagnosis result in the alphabet from A to F.
- It has a full description for each of the parts.
- It displays the whole of diagnostic results to the top of the list.
Future Price Analysis
- This represents the value of the vehicle in chronological order.
- The horizontal axis of the graph is the time (3 month intervals).
- The vertical axis of the graph is the value (dollars).
Alert List
- This will display an alert for the parts that need to be fixed immediately.
5. Offers
User can see a list/set of available offers in the market.
See Offer Details section to find information about the items to display (e.g. author, price, etc). Use it for the listing and search parameters.
6. Offer Details
User can see detailed information about a specific offer.
An offer features the following information (open to suggestions):
- Creation date
- Author (owner)
- Offer Price
- Open for negotiation (yes/no)
- Available time
The page should support the following flow and operations:
- User (buyer and seller) can negotiate the car (if available).
- Once buyer enters into negotiation mode, he/she can enter a new price.
- The seller receives a notification to create awareness of the update.
- The seller can decide to accept/deny the price or to set a new price.
- This cycle ends when the seller accepts or deny the final offer.
- We’d like to see this flow presented through screens.
7. Insurance
This page shows a list of insurance companies available that best match a deal situation according to the vehicle state. In other words, the system matches insurance companies to vehicles, offering discounts and special deals according to the state (thanks for the prediction and history system).
List view should feature:
- Company logo.
- Company name.
- Insurance plan name.
- Insurance fee.
- Brief.
Branding Guidelines
- Branding is open to suggestions, colors and typography. Keep it serious, professional and modern.
- Keep things consistent. This means all graphic styles should work together.
Screen Specifications
- Mobile: 750px width. Height as much as needed.
- Make sure your work is in a vector format, for retina scaling and high fidelity.
MarvelApp Presentation
- Request a MarvelApp prototype from me (mahestro@copilots.topcoder.com).
- Do not use the forums to request for MarvelApp.
- Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.
- Provide the MarvelApp shareable link in your notes during submission upload.
Stock Artwork (Illustrations, Icons, Photography)
- Stock artwork is allowed for this challenge.
- Make sure to declare all your assets properly or you might fail screening.
Target User
Vehicle owners, vehicle sellers (individuals, not companies), insurance providers. Generally, individuals with such an acquisition capability, willing to buy or sell a vehicle, to stay informed about the status and benefit of the suggestions systems. Typically above 25 years old.
Judging Criteria
- Does the app generates a trust worth feeling. (30 %)
- Interpretation of the user experience. (10 %)
- Is the application visually appealing. (20 %)
- Is the application easy to use. (20 %)
- Are mobile-first considerations appropriately applied to the design concept. (10 %)
- Cleanliness of your graphics and design. (10 %)
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, Illustrator or Sketch. Layers should be named and well organized.
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.
Recently we ran an ideation challenge to explore possible solutions for building an application that uses a failure prediction technology (owned by the client). The winning idea proposes to enable an online vehicle market over blockchain. Users must engage this innovative environment seamlessly introducing concepts of market (buy/sell), failure prediction and suggestions systems. We need your help to bring this idea to life through a mobile app!
Best of luck.
Round 1
Submit your design for a checkpoint feedback.1. Dashboard
3. Vehicle Details
4. Failure Prediction Report
6. Offer Details
- Please provide a MarvelApp Presentation (see details below).
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
Round 2
Submit your final design plus checkpoint feedback.1. Dashboard
2. Vehicles
3. Vehicle Details
4. Failure Prediction Report
5. Offers
6. Offer Details
7. Insurance
- Please provide a MarvelApp Presentation (see details below).
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
The goal of this competition is to come up with the look and feel of a mobile hybrid application for the automobile industry supported by Blockchain behind the scenes. The application should work and look well on both iOS and Android system. You are provided with user stories and existing mockups to follow as rough reference.
Concept Design Goals
Most persons face some uncertainty problem when buying an used car. Legit history of the vehicle is barely available. Determining when to sale a vehicle might be also an issue for users, since it’s hard to estimate the “perfect” timing considering the value of the vehicle at certain period of time from now. The solution (see Idea doc) relies on the support of blockchain technology to solve these main issues, among others.
The application will serve features such as market comparisons, buy/sell management, improvements system, prediction system and others to provide the user with useful information in order to make decisions.
The most important features you need to keep in mind:
- Failure Prediction Report. The reasons lay down in the fact that the Failure Prediction Report is based on the information of Parts Details; as well as it affects the related services such as "Insurance" recommendation.
Solution Considerations:
- Page hierarchy must not be deep.
- Application must not be complicated (e.g. navigation, discoverability, affordances).
- DO NOT use lorem ipsum for content/descriptions (parts, history, accidents, alerts, etc). Please research and use realistic information, as much as possible. This will help you get into the top. HOWEVER, there is an exception with the realistic information: DO NOT use real brand neither car model names. For example, instead of “Kia Rio” brand-name: real (DON’T), you can use something fake such as “Kobra Phoenix” brand-name: fake (DO).
- Remove brand and model from the photos you plan to use. Vehicles shouldn’t display any reference to real branding. Blur them out or hide them somewhere.
- Mockups are just a rough reference. Please improve the features, add new features, rethink the mockups.
We expect the final design will be unique, like no other, alongside with a modern style, sophisticated. Designs which not follow a simple reskin/copy of the provided mockups will have advantage during the judging process, so DO NOT just copy the mockups, think out of the box. Keep in mind we definitely do not want to see over data-crowded designs, childish/cartoonish looking.
Supporting Documentation
- Solution background: ideation challenge winner.
- Mockups: rough reference and initial state of the flow proposal (to be improved by you).
Screens Requirements
Overall
- Please suggest how to organize this content and group them into screens, we are looking forward to see your unique proposals, be bold. The following screens and mockups are just initial suggestions but we think content could be organized in a different way, go for it!
1. Dashboard
User has an high summary view of the system. Initially, we propose to display overall amounts and charts that provide a quick summary, alongside with links to other sections. We are open to ideas about how to group and display this information and overall navigation.
The dashboard must support the following features:
- Ability to toggle sale availability of “my vehicle”. If user clicks this toggle (open for sale) the car would become available and vice versa. The status should change on every toggle.
- Navigation to all the sections of the application.
2. Vehicles
User can see a list/set of available vehicles in the market. User can perform search/filter to narrow down results.
See Vehicle Details section to find information about the items to display (e.g. brand, model, etc). Use it for the listing and search parameters.
3. Vehicle Details
User can see detailed information about a specific vehicle.
A vehicle features the following information (open to suggestions):
- Brand * the application supports any type of car e.g. sedan, SUV, etc.
- Model
- Year
- Price
- Travel (elapsed distance)
- Photos
- Description
- Status: system prediction insights.
- Parts repair and accidents history (could be separate pages).
Parts, Repair History & Accident History
These sections basically display a thumbnail/icon of the item plus description. Parts the car has historically possessed or changed. Repair or upgrades the car has gone through. And finally, accidents log. Feel free to research about what information could be displayed here to make it realistic.
My Vehicle
It is basically the same page as a vehicle details page but it doesn’t have the “offer” action. Please provide this screen.
4. Failure Prediction Report
This page displays two analysis section. User can see the chart view and also deep details about the information the charts are displaying.
Value Decrease Parts Analysis
- This will show a decrease in value due to damage of each part.
- It represents the value that was reduced to each part, through vertical bars.
- There are three of the vertical bars (the present value, the value after six months, the value after 1 year) on each part.
- It is sorted by present value.
All Parts Health Analysis
- This lists up the health diagnosis result of all of the parts.
- Each part represents the diagnosis result in the alphabet from A to F.
- It has a full description for each of the parts.
- It displays the whole of diagnostic results to the top of the list.
Future Price Analysis
- This represents the value of the vehicle in chronological order.
- The horizontal axis of the graph is the time (3 month intervals).
- The vertical axis of the graph is the value (dollars).
Alert List
- This will display an alert for the parts that need to be fixed immediately.
5. Offers
User can see a list/set of available offers in the market.
See Offer Details section to find information about the items to display (e.g. author, price, etc). Use it for the listing and search parameters.
6. Offer Details
User can see detailed information about a specific offer.
An offer features the following information (open to suggestions):
- Creation date
- Author (owner)
- Offer Price
- Open for negotiation (yes/no)
- Available time
The page should support the following flow and operations:
- User (buyer and seller) can negotiate the car (if available).
- Once buyer enters into negotiation mode, he/she can enter a new price.
- The seller receives a notification to create awareness of the update.
- The seller can decide to accept/deny the price or to set a new price.
- This cycle ends when the seller accepts or deny the final offer.
- We’d like to see this flow presented through screens.
7. Insurance
This page shows a list of insurance companies available that best match a deal situation according to the vehicle state. In other words, the system matches insurance companies to vehicles, offering discounts and special deals according to the state (thanks for the prediction and history system).
List view should feature:
- Company logo.
- Company name.
- Insurance plan name.
- Insurance fee.
- Brief.
Branding Guidelines
- Branding is open to suggestions, colors and typography. Keep it serious, professional and modern.
- Keep things consistent. This means all graphic styles should work together.
Screen Specifications
- Mobile: 750px width. Height as much as needed.
- Make sure your work is in a vector format, for retina scaling and high fidelity.
MarvelApp Presentation
- Request a MarvelApp prototype from me (mahestro@copilots.topcoder.com).
- Do not use the forums to request for MarvelApp.
- Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.
- Provide the MarvelApp shareable link in your notes during submission upload.
Stock Artwork (Illustrations, Icons, Photography)
- Stock artwork is allowed for this challenge.
- Make sure to declare all your assets properly or you might fail screening.
Target User
Vehicle owners, vehicle sellers (individuals, not companies), insurance providers. Generally, individuals with such an acquisition capability, willing to buy or sell a vehicle, to stay informed about the status and benefit of the suggestions systems. Typically above 25 years old.
Judging Criteria
- Does the app generates a trust worth feeling. (30 %)
- Interpretation of the user experience. (10 %)
- Is the application visually appealing. (20 %)
- Is the application easy to use. (20 %)
- Are mobile-first considerations appropriately applied to the design concept. (10 %)
- Cleanliness of your graphics and design. (10 %)
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, Illustrator or Sketch. Layers should be named and well organized.
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.