Challenge Summary
Welcome to the “Juno Claims Reporting Tool IOS Mobile Design Application”. In this challenge we are looking for you creativity to design an application to report claims or find more information about the existing claims. The web version already exists and we are looking to translate that into an iOS native application. This project is a Proof of Concept, so the entire application will be larger than what we are designing here and this is the reason we are not going to show all the user flows.
1.Splash Page
2.Login
4.Claims Landing Page
5.Report a Claim – Existing User
6.Report a Claim – Fill Information
7.Claim Status and Handler
8.Claim Dashboard
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask in the Forum for a MarvelApp prototype link. You will receive 1 MarvelApp prototype for Desktop.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
1.Splash Page
2.Login
3.Registration
4.Claims Landing Page
5.Report a Claim – Existing User
6.Report a Claim – Fill Information
7.Claim Status and Handler
8.Claim Dashboard
9.Claim Details
10.Claim Follow Up
11.Chat
12.Products
13.Risk Engineering
Background Information
This is a banking application used by brokers, customers and employees to report a claim or see details about the submitted claims. For this particular project, there is a special user flow, as the claim is not associated to a username/insured employee name, but to the company’s policy, so the claim has to be searched by number and date of loss all the time (any improvements/suggestions on the flow should be based on this).
User Story
Hank is a customer who has just downloaded this application and wants to report a claim. Once he enters the application he sees several options where he could go such as Products, Risk Engineering, Claims, About Us, Contact Us, Chat and Login. He goes to claims section and he sees the Claims Landing Page where he has the option to Report a Claim. From there he is asked if he has an account to login or just wants to go directly to report the claim. He goes with the last option. Now he can report a claim and fill all the details of it. As he is not registered yet, he will complete more detailed information about him so the system will also make him an account once he submits the claims.
The claim is submitted and he is now redirected to Claims Landing Page. He wants to see its status and who’s the handler, so he will go to Claim Status & Handler page, where he will input the date of loss and claim number. If he wants to see all the filled information in his claim, he goes to the Claim Details. He now remembers that he forgot to add some notes and photos so he presses the Claim Follow-Up button to do that. On this page he can upload any text PDF or additional photos needed.
The system is throwing an error when submitting the additional information so he goes needs help and he goes to chat. There he finds a chat bot which turns useful in solving the problem and the new data is successfully added.
Key Items to Focus On
- This application must look and feel modern, clean and professional.
- Easy and intuitive user experience for tech and non tech users.
- It’s important to follow the customer’s branding guideline in terms of fonts, colors, etc.
- Keep in mind this is an iOS application to design with specific features
- Make your design stand out on a first view!
Screen Requirements
For this challenge, we are looking for the below pages to be designed/considered in your concepts. Do not allow the suggestions below to impact the creativity of design. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
1. Splash Page
This is the first page the user first sees when he opens the application. It contains the following items:
-Products
-Risk Engineering
-Claims
-About Us
-Contact Us
-Chat
-Login (if user is logged in, he can see his profile photo/user ID and an option to logout).
Feel free to represent the above items as cards or with photos or icons, whatever you think looks best.
2. Login
If the user has an account he can login from this page that has:
-Sample logo (create a simple logo)
-Username
-Password
-Login button
-Option to register
Once the user logs in he will be taken to the splash page with logged in information.
3. Registration
The user can create an account for Juno application here. The page should include:
-Sample logo
-Username
-Password
-Name
-Email
-Phone
-Type of user: broker, customer, other
-Register button
4. Claims Landing Page
From the Splash page, the user chooses to go to Claims. On this page he sees some active links (which are developed in this application) and inactive links which will be developed at a later stage in the future (not in scope of application).
This page acts as a portal to reporting a claim or finding out more information on an ongoing claim. Customers may also access and view entries of submitted claims, or add new information to the claim.
Active Links:
- Report a Claim (automobile claim)
- View My Claim Status and Handler
- Claims Details
- Run a loss report
Inactive Links:
- Recent Searches
- Analytics and reporting
- Customer care center
- Legal services
- Vehicle owners claim
5. Report a Claim – Existing User
When the user clicks to report a claim he will be taken to a page where he will be asked if he has an account and be able to see 2 options:
- Yes, take me to Login
- No, go and report the claim
6. Report a Claim – Fill Information
For this flow we assume that the user doesn’t have an account so he will go to this page to complete the fields to report the claim. These are the same fields a logged in user would see, the only difference is that for the non-registered user in Reported by section, he will see the following:
- Name
- Phone number (should show next to it the message: “We will be sending you a 6 digit code to validate your phone number”)
- Email
- User ID
- Password
- Type of user: broker, customer, other
We'd like to display all the above fields on this page.
Once the user completes these and the rest of the claim details, the system will register the claim and will make an account for him.
7. Claim Status and Handler
If the user wants to see the claim status and the handler of his claim, without seeing all the details he can search for the claim here by filling the next fields:
- Date of Loss
- Claim Number
Then user will be then taken to the claim dashboard.
8. Claim Dashboard
On this page the user will see the following:
- Claim handler
- Claim status
- Required actions from the claims team for the user to complete: like adding information that's not been received or upload a photo or supporting document, like an ID.
- We need a section for the user to perform complete new information that is required by the handler like for example: show the option to upload a document.
- Link to Claim Follow-Up page
- Link to Claim Details page
Claim handler will include:
- name
- email
- phone number
Claim Status:
Should display the states a claim has gone through so far, what is active now(in progress) and what is coming up next. This can be represented as a breadcrumb timeline with the following states:
- The claim has been received (completed)
- We assigned a claim handler (completed)
- The claim is investigated by John Doe (in progress)
- We’ll get back to you (upcoming)
- We mailed a check to you (upcoming)
9. Claim Details
For the user to get to this page he will have to search again by the date of loss and claim number (similar to Claim Status and Handler page). Here the user can see all the information he submitted on the Report a Claim page, in a non-editable form. In addition, the page will also show:
- claim number
- date of loss
- claim status
- claim handler data
- option to follow up (provide additional new information)
10. Claim Follow Up
If the user has more details to add to the insurance after he submitting he has the option to do that here as he will be displayed with a:
- Free form text area
- Option to upload pictures or documents
- Submit button
Note: the user cannot edit the existing information due to insurance rules, he can only add new one.
11. Chat
When a person needs help with the claim, they can reach the chat easy and fast. Here we have a chatbot in place which has different options as in the screenshot.
12. Products
The products page is accessed from Splash page and should have a gallery of existing products like here. Each product will have a photo, name and a short description. You can use the information from the example (photo+text). From this page, there is no need to show a product details page.
13. Risk Engineering
This page is accessed from Splash page should have a gallery of existing risk management solutions like here. Each product will have a photo, name and a short description. You can use the information from the example(photo+text). From this page, there is no need to go into the details page.
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to (keyla.blue1@gmail.com)
- 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).
Branding Guidelines
Please use this branding document and follow the provided guidelines for colors, icons, fonts, image usage, etc. but don’t let them limit your creativity
Target Devices
We are targeting for Mobile application (iPhone only)
Screen size: 750 x 1334 px
Target Audience
Brokers, employees, insurance persons
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
- Overall design and user experience
- Cleanliness of screen design and user flow
- Ease of use
Screening Scorecard
IMPORTANT: The screener will be evaluating the submissions coming based on this scorecard. Make sure to follow the guidelines there closely.
Stock Photography
Stock photography is allowed in this challenge. See this page for more details.
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 image files based on Challenge submission requirements stated above
-MarvelApp link for review and to provide feedback
Source Files
All source files of all graphics created in either Adobe Photoshop, Sketch, AI, XD and saved as editable layer.
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colours) or modify overall colours.
Round 1
Submit your initial designs for checkpoint review.1.Splash Page
2.Login
4.Claims Landing Page
5.Report a Claim – Existing User
6.Report a Claim – Fill Information
7.Claim Status and Handler
8.Claim Dashboard
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask in the Forum for a MarvelApp prototype link. You will receive 1 MarvelApp prototype for Desktop.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
Round 2
Submit your final designs plus checkpoint feedback implemented1.Splash Page
2.Login
3.Registration
4.Claims Landing Page
5.Report a Claim – Existing User
6.Report a Claim – Fill Information
7.Claim Status and Handler
8.Claim Dashboard
9.Claim Details
10.Claim Follow Up
11.Chat
12.Products
13.Risk Engineering
Background Information
This is a banking application used by brokers, customers and employees to report a claim or see details about the submitted claims. For this particular project, there is a special user flow, as the claim is not associated to a username/insured employee name, but to the company’s policy, so the claim has to be searched by number and date of loss all the time (any improvements/suggestions on the flow should be based on this).
User Story
Hank is a customer who has just downloaded this application and wants to report a claim. Once he enters the application he sees several options where he could go such as Products, Risk Engineering, Claims, About Us, Contact Us, Chat and Login. He goes to claims section and he sees the Claims Landing Page where he has the option to Report a Claim. From there he is asked if he has an account to login or just wants to go directly to report the claim. He goes with the last option. Now he can report a claim and fill all the details of it. As he is not registered yet, he will complete more detailed information about him so the system will also make him an account once he submits the claims.
The claim is submitted and he is now redirected to Claims Landing Page. He wants to see its status and who’s the handler, so he will go to Claim Status & Handler page, where he will input the date of loss and claim number. If he wants to see all the filled information in his claim, he goes to the Claim Details. He now remembers that he forgot to add some notes and photos so he presses the Claim Follow-Up button to do that. On this page he can upload any text PDF or additional photos needed.
The system is throwing an error when submitting the additional information so he goes needs help and he goes to chat. There he finds a chat bot which turns useful in solving the problem and the new data is successfully added.
Key Items to Focus On
- This application must look and feel modern, clean and professional.
- Easy and intuitive user experience for tech and non tech users.
- It’s important to follow the customer’s branding guideline in terms of fonts, colors, etc.
- Keep in mind this is an iOS application to design with specific features
- Make your design stand out on a first view!
Screen Requirements
For this challenge, we are looking for the below pages to be designed/considered in your concepts. Do not allow the suggestions below to impact the creativity of design. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
1. Splash Page
This is the first page the user first sees when he opens the application. It contains the following items:
-Products
-Risk Engineering
-Claims
-About Us
-Contact Us
-Chat
-Login (if user is logged in, he can see his profile photo/user ID and an option to logout).
Feel free to represent the above items as cards or with photos or icons, whatever you think looks best.
2. Login
If the user has an account he can login from this page that has:
-Sample logo (create a simple logo)
-Username
-Password
-Login button
-Option to register
Once the user logs in he will be taken to the splash page with logged in information.
3. Registration
The user can create an account for Juno application here. The page should include:
-Sample logo
-Username
-Password
-Name
-Phone
-Type of user: broker, customer, other
-Register button
4. Claims Landing Page
From the Splash page, the user chooses to go to Claims. On this page he sees some active links (which are developed in this application) and inactive links which will be developed at a later stage in the future (not in scope of application).
This page acts as a portal to reporting a claim or finding out more information on an ongoing claim. Customers may also access and view entries of submitted claims, or add new information to the claim.
Active Links:
- Report a Claim (automobile claim)
- View My Claim Status and Handler
- Claims Details
- Run a loss report
Inactive Links:
- Recent Searches
- Analytics and reporting
- Customer care center
- Legal services
- Vehicle owners claim
5. Report a Claim – Existing User
When the user clicks to report a claim he will be taken to a page where he will be asked if he has an account and be able to see 2 options:
- Yes, take me to Login
- No, go and report the claim
6. Report a Claim – Fill Information
For this flow we assume that the user doesn’t have an account so he will go to this page to complete the fields to report the claim. These are the same fields a logged in user would see, the only difference is that for the non-registered user in Reported by section, he will see the following:
- Name
- Phone number (should show next to it the message: “We will be sending you a 6 digit code to validate your phone number”)
- User ID
- Password
- Type of user: broker, customer, other
We'd like to display all the above fields on this page.
Once the user completes these and the rest of the claim details, the system will register the claim and will make an account for him.
7. Claim Status and Handler
If the user wants to see the claim status and the handler of his claim, without seeing all the details he can search for the claim here by filling the next fields:
- Date of Loss
- Claim Number
Then user will be then taken to the claim dashboard.
8. Claim Dashboard
On this page the user will see the following:
- Claim handler
- Claim status
- Required actions from the claims team for the user to complete: like adding information that's not been received or upload a photo or supporting document, like an ID.
- We need a section for the user to perform complete new information that is required by the handler like for example: show the option to upload a document.
- Link to Claim Follow-Up page
- Link to Claim Details page
Claim handler will include:
- name
- phone number
Claim Status:
Should display the states a claim has gone through so far, what is active now(in progress) and what is coming up next. This can be represented as a breadcrumb timeline with the following states:
- The claim has been received (completed)
- We assigned a claim handler (completed)
- The claim is investigated by John Doe (in progress)
- We’ll get back to you (upcoming)
- We mailed a check to you (upcoming)
9. Claim Details
For the user to get to this page he will have to search again by the date of loss and claim number (similar to Claim Status and Handler page). Here the user can see all the information he submitted on the Report a Claim page, in a non-editable form. In addition, the page will also show:
- claim number
- date of loss
- claim status
- claim handler data
- option to follow up (provide additional new information)
10. Claim Follow Up
If the user has more details to add to the insurance after he submitting he has the option to do that here as he will be displayed with a:
- Free form text area
- Option to upload pictures or documents
- Submit button
Note: the user cannot edit the existing information due to insurance rules, he can only add new one.
11. Chat
When a person needs help with the claim, they can reach the chat easy and fast. Here we have a chatbot in place which has different options as in the screenshot.
12. Products
The products page is accessed from Splash page and should have a gallery of existing products like here. Each product will have a photo, name and a short description. You can use the information from the example (photo+text). From this page, there is no need to show a product details page.
13. Risk Engineering
This page is accessed from Splash page should have a gallery of existing risk management solutions like here. Each product will have a photo, name and a short description. You can use the information from the example(photo+text). From this page, there is no need to go into the details page.
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to (keyla.blue1@gmail.com)
- 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).
Branding Guidelines
Please use this branding document and follow the provided guidelines for colors, icons, fonts, image usage, etc. but don’t let them limit your creativity
Target Devices
We are targeting for Mobile application (iPhone only)
Screen size: 750 x 1334 px
Target Audience
Brokers, employees, insurance persons
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
- Overall design and user experience
- Cleanliness of screen design and user flow
- Ease of use
Screening Scorecard
IMPORTANT: The screener will be evaluating the submissions coming based on this scorecard. Make sure to follow the guidelines there closely.
Stock Photography
Stock photography is allowed in this challenge. See this page for more details.
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 image files based on Challenge submission requirements stated above
-MarvelApp link for review and to provide feedback
Source Files
All source files of all graphics created in either Adobe Photoshop, Sketch, AI, XD and saved as editable layer.
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colours) or modify overall colours.
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.