The Librum app aims to minimize frustration, to allow users to feel they are getting good deals on books, and to feel comfortable doing so.
My Roles and Responsibilities
User Flow and Personas
Ideation, Brainstorming, and Sketching
Wireframing and Prototyping
August 21- November 21
Team - 3 members
System Concept Statement
Librum is an app which connects users who want to buy/sell and give away/receive books in their local area. Librum addresses four primary problems.
A. Have books they want to sell or give away.
B. Want to buy specific books and browse locally available books.
C. Want to read reviews for books before they buy.
D. Need to be able to ask for specific books that are not easy-to-find or cheaply available.
UX Road Map
Identified target audience, conducted interviews and work affinity diagram
Requirements and modelling
Created usage research data models to better understand user needs and requirements.
With all the data collected, created user persona to have a clear user image with different needs
Started Designing the app with ideation, sketching and storyboarding
Wireframing and Prototype
Created wireframes, Lo-fi and Hi-fi prototype inculcating all the data collected from user and usage research
Conducted Pilot testing iteratively to evaluate the improvements and added them to make better user experience.
Test and Evaluate
After contextual inquiry and analysis, we conducted interviews with 11users. The interview method was moderated type held both remotely and in-person. Interview was based on short questionnaire.
Data collected after interview
Work Activity Affinity Diagram
The insights received from research is summarized in work activity affinity diagram. FigJam tool was used to develop WAAD. Initially, rough"pile"grouping was done and later sorted into categories such as such as “User Preferences,” which was then split into “Most Used Apps,” “Book Type Preference,” and “User preferences/motivations” (which was used to keep track of more general user feelings/tendencies). “Wanted/Concerns” became the separate categories of “Concerns,” focusing on what users were apprehensive or negative about, and “Features,” listing specific desired features that users mentioned they wanted to see.
Requirements and Modelling
The data model was created based on the data collected from user interview. The models were categories under user model, usage model and task structure model.These models helped to understand user class, usage scenario and user roles. This further helped to decide task interaction model based on which, a proper understanding of user need, user tasks and interaction on the system was possible.
Work Role Model
Task Structure model(Hierarchical Task Inventory)
HTI for buyer
HTI for seller
On collecting all the data, drawing insights from them and analyzing the persona, we ideate by categorizing the requirements, listing pain points and defining future scope.The iterative process helps us to better understand the concept and assists in decision making.
Storyboarding helps us to under how our screen will look like after prototyped. We realized the problem and worked to solve it here. It provides the idea of "Parent-child" transition, "sibling" transition.
These are selection of sketches generated during the ideation process. The rough ideas developed in them were fleshed out more in discussion before refinement and inclusion in our storyboard and wireframes. It helps to get visual idea about our design.
To ensure consistency in design and support branding, we discussed on set of color palette. Later which create a color palette and consider primary and secondary color as per our branding attributes.
After deciding the style guide, we worked on wireframes of our application. The wireframing helps with clear idea of layout, features, interfaces, transition, user flow, cognitive walkthrough and various functionality.
The wireframes are a selection from our early wireframe work, based on the scenario
shown in our storyboard.Sample wireframe help to analyzed the flow between the screen, layout interaction, feature interaction and transitional relationship.
After wireframing, we used Figma to design High fidelity wireframe. We decided the major task roles and created prototypic flow for each.
Performing Filter Search
User can perform filter to search for the book they want. This feature make the search process simple by allowing users to save their time and find the exact book they looking for. Various search options are available
Posting a request to buy a book
User can post a request for a book they want to buy. The post is seen in feed page where all the users including buyer and seller can see it. This task is mainly for buyers.
Posting a request to sale
User can post about the book they want to sale or giveaway with its description, cost and condition. The post can be viewed in feed page. The role is entirely for seller.
Connect to the seller
This task allow to connect buyer with seller. It can be conducted only once buyer confirms to buy a book from any particular seller. The buyer can chat with the seller through the application itself.
After designing prototype, we conducted pilot testing with 3 users. Based on there feedbacks we made design changes, added features and improved the overall experience of design.
Here are some of the feedbacks from pilot testing:
Additional background detail
Absent intuitive features/present unintuitive features
The complete process of collecting data through user interview, analyzing them, creating problem statements and postulating solution for the problems.
In-depth understanding of design thinking process.
Patience to iterate process several time unless a suitable and more user friendly solution is not found.
Importance of user feedback.
Importance of uniformity in design
Learned to run my project remotely in sprint basis.
Team work and team collaboration.
Leadership, Empathy and unbias.