Reflecting User Needs Data in the UI/UX design


            As noted, the user needs on Kiva- which is a non-profit organization that connects borrowers to lenders vary depending on the category of the user (Kiva, 2021). Users on the platform can be borrowers or they can be lenders. The data needs for borrowers include finding lenders within the locality, accessing the conditions of the loan in terms of loan length, the repayment schedule, whether it is monthly or bimonthly, and the nature of the funding model. Furthermore, they also need data on whether the partner in the host country covers currency loss and any special considerations of the loan. On the other hand, the data requirements for lenders include data on borrower interests, analysis of other lenders’ data, data on borrower loan payments in a cloud application so that the lender can plan for the recycling of previously paid funds. Based on the data requirements for borrowers and lenders, the interface that is possible with the limited resources of an embedded system is the suitable user interface would be the embedded user interface which is characterized by the ease and accuracy of use (Larry, n.d).

UI/UX Design

            Based on the borrower data, the data that I would display on the UI/UX wireframe includes the name, gender, the reason for the loan, how the loan will benefit, and payment status. In an embedded user interface, a few icons will be used to support different functions. However, the nature of the icons and the functions assigned to each icon will be influenced by the ability of the borrower to display his or her name, display the reason for the loan, the gender, loan payment status, and how the loan will benefit his or her. On the other hand, the lender should be able to display the name, the location, the amount of loan that can be awarded, the interest rate, and the loan payment schedule.

Accessing the Data

ux design

             In order to access the data, the user will open the flip phone, click the Kiva app. The Kiva app will have the login details. The user has to log in to the details. Upon logging in; there will be two options, at the menu bar, lender and borrower. In this case, the user selects the option that suits him or her. When the user selects the borrower option, blank spaces that he has to key in his information is displayed, these include, the name, the age, the location, contacts, the amount requested, the nature of the project, how the project will benefit him or her and the user profile photo. The information is saved in the app database, which is cloud-based.

            On the other hand, when the user selects lender option, a blank space for lender profile information is opened; the lender keys in the name, the contact, the preferred nature of projects funded, the interest rate, the maximum amount that the lender can lend to a borrower, and the payment schedule. The information will be stored in a cloud-based database. The lender can click access borrowers based on projects, based on locations, or based on amounts. In this case, the lender can access the profile of the borrower online. Furthermore, the lender can also access the profile of other lenders. That means a registered lender will log in the system, click next, which is the profile information, click next, which gives the option for borrower profile and lender profile, based on what information the lender is seeking, he may click borrower profile, in which there will be options on the preference on what would be displayed. In this case, he sees the profiles of all borrowers’ requests, and in case of any loan that is already approved, he also sees the borrowers’ outstanding loan. On the other hand, in case he or she clicks the lender profile, the lender can access the profile information of other lenders on the platform.

            Justification of the Design

            The design is meant to serve the users and the lenders, the lenders are in the business of lending, while the borrowers seek the financial services; therefore, there are two different data requirements. In the app, the lender seeks information from borrowers and lenders, while the borrower displays the information that the lender requires. The lender can connect with the borrower, in which case, the borrower can access the profile of the lender that helps him or her make an informed decision based on the conditions of the lender.

             The UI design as noted above is an embedded user interface It has advantages such as having minimal human interference, it is has a compressed size, and is easy to use (Banger, 2020). As an embedded user interface, it is designed to serve specific functions, which are enabling the visualization of the borrower profile, enabling the visualization of the lender profile, connecting the borrower and the lender. As an embedded system, it is task-specific and would carry out the same tasks continuously throughout its lifetime (Banger, 2020). Based on the borrower stories, the user will be expected to work through the application by first

  • Login, -select on the menu option either lender or borrower- profile
  • In case of the borrower, clicks next to accept connection with the lender, in which case, which will view the lender’s profile.
  • In case, it is a lender, he can connect to the borrower and view the borrower profile or may connect with other lenders to view their profile.

             The specific screen elements that would be included are aimed at easing the usability of the application. Certain data elements such as lender and borrower are at the forefront. Furthermore, on the borrower profile data elements such as location, nature of project amount are at the forefront because the lenders have different preferences; they may choose to finance the project based on type, amount, or location. The users would complete the tasks by making the necessary selections based on their interests.

Balancing Creativity with Code of Conduct   

  Among Kiva’s code of conduct is to respect users and their dignity, and be nice to API servers. In line with respecting users and their dignity, the lenders and the users focus on poverty reduction engagements, therefore the development of the app should respect the dignity of both. As such, part of the creative approaches that would be incorporated in the app is to avoid entry of demonizing information.

Similar Posts

Leave a Reply

Your email address will not be published.