i.Library
"Happy Reading"
Role - UX/UI & Research
Duration - Sep - Oct 2021 (8weeks)
Tools - Figma, Adobe Photoshop, InVision.
The Product
i.Library is a mobile app that helps people to read or listen any book of their choice without spending much. This is the perfect app for all the bookworms out there.
"No not another bustling app,
But a peaceful app."
Problem
I started the project with a hypothesis that bookworms love to read books. don’t have a user-friendly way to evaluate their favorite books and people who have busy schedules, it is difficult for some people to buy such expensive books.
Solution
i.library solves this by providing an on-the-go library app that leverages people with busy working schedules who have no time to go to the library and those who don’t want to spend lots of money on books can use the i.library app to read or listen to books online.
Understanding the goal
Business goal
Will make money when users will buy the subscription(yearly or monthly)
User’s goal
Will get to read or listen to their favorite books at any time and at a reasonable cost.
Design Process
.png)
Research
I conducted a mix of primary and secondary research. The primary research surveyed 10+ potential users on the biggest pain points they face when it comes to reading books.
In secondary research, I tried to understand more about people who love to read books.
More than 80% of the users prefer mobile over laptop.
More than 75% of the users like to listen to books rather than reading.
More than 60% of the users prefer to read books online.
Competitive Analysis.
Meet the User's
.png)
Information architecture.
.png)
Big picture & Close up Picture
Low - Fidelity
I started the design stage and sketched out low-fidelity with just pen and paper while keeping in mind the user's tasks and pain points I have collected so far.
Wire flow
I created a wire flow to get vital information that would help direct the flow of the app and fluidity going from screen to screen.
.png)
“Here I focused on visual appearance and transaction fluency.”
It took me a month to ideate, iterate, and finalize the design. I evaluated the design and detail each time by considering users’ needs and behavior, also conducted user testing to testify the learnability and usability of the interface with the target audience, whose feedback was adopted in the future iteration.
User Testing
I tested the live version of the interfaces by sharing links and some of the suggestions to fix some minor usability issues. I collected all the feedback and integrated it into the current design.
A/B Testing
UI A
UI B
User's Found UI B more interesting and fun to use.
Challenge 1
What if a user is tired and has no energy to read the book.
- I thought of having the option of an auto reader.
Challenge 2
Based on usability studies, it is possible that users only want to read a particular chapter of the book.
​
- So, I added a screen of chapter-wise selection.
Challenge 3
According to some users they only wanted to read books that are trending.
​
- So I added a section of trending books.
“ The app made it easy and fun to read the book”
1 of the participant
Final product
Accessibility Consideration.
Style Guide
Button
#9B6B43
Takeaway
Next Step
Provide a Screen reader option for people with low vision.
Used icons to help make navigation easier.
Provided mode night option for users.
Using warm feeling and comfortable colors helped to convey the feeling of comfort to users, shades of browns give the feeling of joy and comfort. I used a Sans-Serif typeface that would bode well with edges.
#EFCEAD
#744C24
i.library made me realize just how interesting it can be to produce an application like this. All the research helped me to connect more with users and I understand how little details can matter a lot. All the feedback helps me to make changes for good. This made me realize how important it is to explore and learn more about design systems.
If had more time I would conducted user testing again and improved i.library more.