Recall that Kiva is a non-profit organization that allows individuals to lend money via the internet to low-income entrepreneurs and students in nearly 100 countries. It is Kiva’s goal to bring lenders and borrowers together in order to increase financial access and improve the quality of financial services in underserved communities.
User stories that outline the borrower and lender personas are provided below:
- As a Kiva borrower, I want to access information about Kiva and about borrowing from Kiva with my flip-phone (which is an embedded device), so that I can stay informed, request loans, and track my loan payback process.
- As a Kiva lender, I want to explore borrower requests, analyze my and others’ lending data, and follow borrower loan payments (in a cloud application) so that I can forecast how I will loan funds and plan the recycling of previous paid funds.
You have already thought about the borrowers’ and lenders’ needs and explored the data that Kiva has made available. From this, you were able to determine user data priorities, meaning the most important data that users would want to access from Kiva. Now you will start thinking more about how this data can be reflected in a UI/UX design so users can interact with it in a manner that is clear and helps them achieve their goals. For now, you will be focusing on the borrower user story and their flip-phone embedded device. As you begin to prototype a design, remember to consider what is possible within the embedded system.
Prompt
Specifically, you must address the following rubric criteria:
- Design a UI/UX paper prototype for the main screen of the embedded application. This can be a simple sketch completed by hand on paper, but how you will convey the data priorities you previously identified should still be clear. Include labels for every component, user interaction, and clickable button. You should also take the time to review the design guidelines from previous modules, as these standards continue to be important aspects of quality design. Revisiting these again and again will be common in professional work.
- Explain how users will access the data. Discuss the data decisions you made in the previous milestone and how they are reflected in your design. Be specific about what data users will access in the application and the steps they will follow. Make sure you address every element that is included in your paper prototype.
- Justify why the design is suited for the user. Your justification should be based on the borrower user story and what you have come to understand about the range of individual borrower needs from your explorations in the previous milestone. Address the following in your justification:
- In what order would the user be expected to work through the application?
- What are your reasons for including specific screen elements?
- Why have you brought certain data elements to the forefront?
- Why will this layout of information make sense to a user?
- How would a user complete tasks in the application?
- Discuss how you balance creativity with the code of conduct Kiva provides. Select two list items from the Kiva Code of Conduct, which is linked in this module’s resource section, and explain how you took them into consideration with your design. Think about the responsibility designers have to serve their users and the organizations where their data is held.
Guidelines for Submission
Submit your work, including your written explanation and a photo of your paper prototype, as a two-page, double-spaced Microsoft Word document.
0 comments