Challenge Summary
Welcome to "IC - Child Support Payment Apps Wireframe Challenge". We are looking for your help to build an application and service for modernizing child payment infrastructure in the US. In this challenge, we want you to focus on providing the best UX for a mobile application that will help and allow parents to pay their obligation for children support. At the end of this challenge, we are wanting to see intuitive and easy to use (requiring no training) "wireframe concepts" that will help us design and build the UI in the next phase of this project!
Background Overview
We are seeking to build an application and service for modernizing the child payment infrastructure in the US. The initial phase of the application will focus on building out the payer facing mobile application and a lightweight service layer. This build will provide a demo quality application to support ongoing sales and business development efforts. The user of the mobile app will have a full fidelity experience for demonstration purposes and the service tier will be built in a scalable way to allow integration of multiple state, county, or tribe level data sources. A simple data tier will be provided sufficient for demo support with dynamic payment, but limited in it’s ability to serve as a full production tier.
Wireframe Expectations:
- You should create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The application must be very easy to use and intuitive. Keep that in mind when create your solution for the layout and flow information.
- You MUST cover all requirements mentioned in challenge details.
Wireframe Guidelines:
- Create your wireframe for desktop/web and mobile apps.
- Minimum width for desktop is 1280px width, height adjusting accordinglly.
- Minimum width for mobile is 750px width height adjusting accordingly.
Screen Flows
The following screens only for recommendations, if you have a better concepts that will provide better solution for our goals, please feel free to create it.
Parent User (Mobile and Desktop)
01) View Child Support Account
- Display what their $ obligation is on a monthly basis
- Display any backlog or unpaid dues.
- Display a payment history.
02) View Documents
- Court documents leading to child support payments are scanned in by the courts and are loaded onto a fileshare. The application will pull these documents into the app so the user can easily keep track of documents related to their case.
- Display a set of documents related to the user's case
- Allow user to open those documents in the relevant application or download or share.
03) Calendar Integration
- The user will receive in-app alerts when their payments are due.
- Eg: On the user should receive an alert that they owe a payment on the 31st of the month.
- Alerts will happen within the app and also at an OS level; eg: notification popup on iOS and android.
04) Capture data (notes, pictures, etc)
- As part of divorce proceedings, family members are often asked to take notes on their interactions with the other parent for legal purposes. For example, if a divorced couple is exchanging custody of their child and they have a negative interaction with each other, they should take notes on it so they have a form of legal documentation for the courts, if necessary.
- Within the app, users will be able to take notes and pictures so they can easily keep all notes related to their case in one secure location.
- Design a screen that allows users to take notes and pictures.
- Notes should include: name, date, written documentation and optionally, pictures of any relevant information.
- Keep track of those notes by date.
- Users will be able to send notes from within the app to their attorney.
- The interface for sending notes will come in the future. For now, just need a button to suggest that this is possible.
05) Make Payment via Store
- For many people, child support payments are taken directly out of a paycheck.
- However, many others do not receive regular paychecks, are paid in cash, or do not have bank accounts so there is no easy way for the payments to occur automatically.
- Users who will not have payments taken directly must deliver payment to a middle-man who will be able to transfer their cash to a dispersment agency who will then deliver the payment to the recipient.
- In order for a child support payment to be considered valid, the money has to go through the official state system. Directly giving cash or a check to the child care recipient is not valid by law.
Store Owner User (Desktop ONLY)
- The Store owner acts as the middle-man in this application:
- Payer/Parents gives their payment to the store who will act as the middle-man.
- The store logs on to the system.
- The store owner enters the payor’s Unique ID and enters their payment into the system.
- The system gives the user an identifier (Passcode, Barcode, QR Code, etc) for their payment so they can track the payments progress as it processes.
- The payer and the store owner can each track this payment online, as the system takes several days for the money to reach its destination.
- When a store owner logs in; they will be able to:
-- Start a new transfer
-- Check the status of the transfers they are responsible for.
06) Signup as payment taker
- Web client; I'm signing up.
- Account setup / login
- User id / creds, login and show who you are processing payment for
- Amounts that are being sent
- Sent to a store bank account
- But they have to go through ACH
- Goes through direct deposit; or debit card;
- At this stage; getting the money in is the flow we need.
07) Take a payment
- The Store Owner will accept a Payer/Parent's monthly payment.
- Store owner will have a simple interface to accept the payment and deliver a unique identifier to the Payer.
- Interface should include:
-- Payment Amount
-- Payer Name
-- Payer ID number
- When a payment is accepted: the interface should display a success message and display the tracking ID
Attorney (Please provide placeholder screen as part of navigation for Parent User, these is future features):
08) Email Attorney
09) View Attorney billing account
10) View Attorney documents
11) Pay Attorney
- Parent user at this point.
- Getting attorneys in is good.
- Should be in there in the end.
- I (parent) should be able to coorespond through attorney through the app
Learn Axure
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/support
Target Audience
- Parents: User is using the app to make their child support payments and manage information related to their case.
- Store Owners: Store owners act as the middle-man between the child support payor who must pay in cash (eg: no credit cards or bank accounts) and child support recipients. The store owner takes in cash from the payor and enters the payment into a bank account, where it is then sent to the recipient.
Notes: The store owner uses a separate interface for performing cash transfers. A regular user will not see the cash transfer user interface.
Judging Criteria:
- Overall User Experience
- Completeness and accuracy of the wireframe as defined in the challenge spec
- How well your wireframes provide a consistent user flow.
- How well your wireframe captures all the functionality.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client).
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
Wireframes should be built in HTML or Axure or InvisionApp Prototype. The resulting files are not critical in this Challenge. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.
Round 1
Submit your initial wireframe solution for checkpoint feedback
Notes.jpg: Any comments about your solution for the Client.
Round 2
All requirements like stated in challenge details with client feedback applied.
Notes.jpg: Any comments about your design for the Client.
Background Overview
We are seeking to build an application and service for modernizing the child payment infrastructure in the US. The initial phase of the application will focus on building out the payer facing mobile application and a lightweight service layer. This build will provide a demo quality application to support ongoing sales and business development efforts. The user of the mobile app will have a full fidelity experience for demonstration purposes and the service tier will be built in a scalable way to allow integration of multiple state, county, or tribe level data sources. A simple data tier will be provided sufficient for demo support with dynamic payment, but limited in it’s ability to serve as a full production tier.
Wireframe Expectations:
- You should create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The application must be very easy to use and intuitive. Keep that in mind when create your solution for the layout and flow information.
- You MUST cover all requirements mentioned in challenge details.
Wireframe Guidelines:
- Create your wireframe for desktop/web and mobile apps.
- Minimum width for desktop is 1280px width, height adjusting accordinglly.
- Minimum width for mobile is 750px width height adjusting accordingly.
Screen Flows
The following screens only for recommendations, if you have a better concepts that will provide better solution for our goals, please feel free to create it.
Parent User (Mobile and Desktop)
01) View Child Support Account
- Display what their $ obligation is on a monthly basis
- Display any backlog or unpaid dues.
- Display a payment history.
02) View Documents
- Court documents leading to child support payments are scanned in by the courts and are loaded onto a fileshare. The application will pull these documents into the app so the user can easily keep track of documents related to their case.
- Display a set of documents related to the user's case
- Allow user to open those documents in the relevant application or download or share.
03) Calendar Integration
- The user will receive in-app alerts when their payments are due.
- Eg: On the user should receive an alert that they owe a payment on the 31st of the month.
- Alerts will happen within the app and also at an OS level; eg: notification popup on iOS and android.
04) Capture data (notes, pictures, etc)
- As part of divorce proceedings, family members are often asked to take notes on their interactions with the other parent for legal purposes. For example, if a divorced couple is exchanging custody of their child and they have a negative interaction with each other, they should take notes on it so they have a form of legal documentation for the courts, if necessary.
- Within the app, users will be able to take notes and pictures so they can easily keep all notes related to their case in one secure location.
- Design a screen that allows users to take notes and pictures.
- Notes should include: name, date, written documentation and optionally, pictures of any relevant information.
- Keep track of those notes by date.
- Users will be able to send notes from within the app to their attorney.
- The interface for sending notes will come in the future. For now, just need a button to suggest that this is possible.
05) Make Payment via Store
- For many people, child support payments are taken directly out of a paycheck.
- However, many others do not receive regular paychecks, are paid in cash, or do not have bank accounts so there is no easy way for the payments to occur automatically.
- Users who will not have payments taken directly must deliver payment to a middle-man who will be able to transfer their cash to a dispersment agency who will then deliver the payment to the recipient.
- In order for a child support payment to be considered valid, the money has to go through the official state system. Directly giving cash or a check to the child care recipient is not valid by law.
Store Owner User (Desktop ONLY)
- The Store owner acts as the middle-man in this application:
- Payer/Parents gives their payment to the store who will act as the middle-man.
- The store logs on to the system.
- The store owner enters the payor’s Unique ID and enters their payment into the system.
- The system gives the user an identifier (Passcode, Barcode, QR Code, etc) for their payment so they can track the payments progress as it processes.
- The payer and the store owner can each track this payment online, as the system takes several days for the money to reach its destination.
- When a store owner logs in; they will be able to:
-- Start a new transfer
-- Check the status of the transfers they are responsible for.
06) Signup as payment taker
- Web client; I'm signing up.
- Account setup / login
- User id / creds, login and show who you are processing payment for
- Amounts that are being sent
- Sent to a store bank account
- But they have to go through ACH
- Goes through direct deposit; or debit card;
- At this stage; getting the money in is the flow we need.
07) Take a payment
- The Store Owner will accept a Payer/Parent's monthly payment.
- Store owner will have a simple interface to accept the payment and deliver a unique identifier to the Payer.
- Interface should include:
-- Payment Amount
-- Payer Name
-- Payer ID number
- When a payment is accepted: the interface should display a success message and display the tracking ID
Attorney (Please provide placeholder screen as part of navigation for Parent User, these is future features):
08) Email Attorney
09) View Attorney billing account
10) View Attorney documents
11) Pay Attorney
- Parent user at this point.
- Getting attorneys in is good.
- Should be in there in the end.
- I (parent) should be able to coorespond through attorney through the app
Learn Axure
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/support
Target Audience
- Parents: User is using the app to make their child support payments and manage information related to their case.
- Store Owners: Store owners act as the middle-man between the child support payor who must pay in cash (eg: no credit cards or bank accounts) and child support recipients. The store owner takes in cash from the payor and enters the payment into a bank account, where it is then sent to the recipient.
Notes: The store owner uses a separate interface for performing cash transfers. A regular user will not see the cash transfer user interface.
Judging Criteria:
- Overall User Experience
- Completeness and accuracy of the wireframe as defined in the challenge spec
- How well your wireframes provide a consistent user flow.
- How well your wireframe captures all the functionality.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client).
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
Wireframes should be built in HTML or Axure or InvisionApp Prototype. The resulting files are not critical in this Challenge. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
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.