Kiva Design

docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

319

Subject

Computer Science

Date

Feb 20, 2024

Type

docx

Pages

6

Uploaded by SargentSnake1088

Report
Caio Mauro CS319 11/30/2023 Kiva Flip Phone Paper Prototype The limitations of an embedded system can vary when talking about flip phones. However, there are a few assumptions that we can make to determine how users will access and interact with Kira’s data. To begin, we have a limited amount of “pixel real estate.” Flip phones are small, and their screens are even smaller. Any data being displayed to the user will have to be compact and concise to account for its limited size. We can also assume that navigation will be limited to an arrow-based touch pad, next and back buttons. Previously we said that the borrowers will need to see a few key elements from the data like their loan balance, status, term length and some others. This is all displayed in a single screen under the users “My Loan Status” page. All they must do is select the My Loans button from the main page to view that important data. It is presented in an easy-to-understand labeled-list with a loading bar to graphically depict their payment process. Aside from this, most of the other data being displayed is universal, meaning all users view the same data. Things like the quick links, Kiva’s about section, and the FAQ are all universal. The design I went for is directly influenced by the borrower user story. It covers all their needs while being responsive for a flip phone device. The goal is for the system to function like a long website while having separate pages to increase load speeds. I would expect the user to begin at the home page then assuming they have a loan to display, the user would navigate to the loan status page through the downward navigation button. If they do not have a loan to display, the request loan page would be loaded through the same method of navigation. If the user passed both pages and did not interact with either of the pages, I would expect them to be looking for some sort of help. The support page would be next. Lastly, Kiva’s about page would be displayed at the end since it is of the least priority to the user. The application follows the order of priority I previously mentioned. Borrowers are there to either apply for a loan or view/manage their existing loan. If they have trouble with either of these the user would then be looking for support which is why it is shown next. The code of conduct is very clear on Kiva, such as respecting lenders and borrowers and treating each other with dignity as well as more basic things like following the terms of service. The design makes following this easy by allowing users to navigate to the support page with a link to the code of conduct. The design also allows users to easily get loans and manage them. The goal is to give the user the opportunity to find success with the platform. The design provides the borrowers with all the information they could need to manage their loan and make use of it in a responsible manner. The goal of Kiva is to combat poverty through micro-financing and by creating an enjoyable user experience we expand Kiva’s reach and impact.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help