Infosys Internship · iOS App
BibloFi —
Where Convenience
Meets Curiosity
Redesigning the library experience for digital-first students — from browsing to booking, everything just a tap away.
Project Overview
A library app built
for how students actually live.
BibloFi is a mobile app designed to simplify how library members access books and services. From browsing by genre to scanning for availability, issuing books, and booking seats — everything is just a tap away.
This project was developed in one month during my internship at Infosys. I led the design of the entire member experience, focusing on creating an interface that feels effortless, modern, and human.
My team
Project goal
"Create a seamless, feature-rich library app that empowers members to discover, reserve, and borrow books efficiently while reducing friction."
Design Process
The Double Diamond
framework in practice.
Phase 1
Discover
Research, interviews, observation
Phase 2
Define
Personas, problem statements, insights
Phase 3
Develop
Brainstorming, wireframes, iterations
Phase 4
Deliver
Hi-fi designs, design system, testing
Discover — Research
Understanding how students
actually use libraries.
I conducted surveys, contextual interviews, and observation sessions to capture real-life experiences of both library members and librarians. The goal: understand the recurring frustrations that disrupt the library experience.
Key finding: the friction wasn't in the library itself — it was in the invisible overhead. Not knowing if a book was available before visiting. Not being able to reserve a seat. No reminders for due dates. Digital tools existed, but none were designed with student workflows in mind.
20
Usability test participants
90%
Task completion rate
10.95:1
Colour contrast ratio (WCAG AAA)
4
Weeks to design & ship
Define — Personas
Two students, two stories,
one shared frustration.
Based on real research insights, I created two fictional personas representing the core user archetypes. These guided every design decision from information architecture to feature prioritisation.
"Despite living in a digital-first world, library visits remain stuck in the past — long queues, no way to check book availability, and zero flexibility in planning. The result? A frustrating, disconnected experience that fails modern users."
Riya Sharma
Goals
Pain Points
Arjun Mehta
Goals
Pain Points
Develop — Wireframes
From rough sketches
to structured flows.
The brainstorming started in WhatsApp chats and rough sketches — raw ideas that I then translated into structured lo-fi wireframes in FigJam. From there, I built out 7 complete user flows covering every core feature.
7 complete user flows designed: Onboarding · Sign In · Browse by Genre · Search by Author · Scan & Search · Notifications & Profile · Seat Booking
Deliver — Key Features
Five features that make
library visits optional.
01
Smart Book Discovery
Find any book before you even leave home.
Students were wasting time visiting the library only to find the book they needed was already issued. The search system lets users browse by genre, search by author, or scan a barcode — and see real-time availability status before making the trip.
18 out of 20 usability test participants successfully found and located a book on their first attempt.
📚 90% search success rate in testing02
Study Seat Booking
Reserve your spot before you arrive.
Seat unavailability during exam season was one of the top pain points identified in research. The seat booking feature lets students view the study hall layout in real time, select an available seat, and receive a confirmation — all before leaving home.
17 out of 20 participants successfully booked a seat in usability testing. The 3 who struggled found the confirmation step slightly unclear — which we improved in the final iteration.
📚 85% seat booking success rate03
Issue & Return Tracking
No more queues. No more forgotten due dates.
The issue and return flow is the heart of the app. Students can request a book digitally, track its status, and receive push notifications when due dates approach. The fine tracker shows exactly what's owed and why — no surprises at the counter.
A personal reading history log also lets students track books they've previously borrowed — solving a pain point both personas mentioned during research.
📚 Automated reminders reduce fines04
Scan & Search
Point your camera. Find the book instantly.
Students standing in the physical library can scan a book's barcode or ISBN to instantly see its availability status, location in the library, and whether similar books are available. It bridges the physical and digital library experience seamlessly.
This was particularly well-received by tech-savvy users like Arjun's persona — the speed of scanning eliminated the need to ask librarians for basic information.
📚 Eliminates dependency on librariansDeliver — Final Designs
The finished product —
every screen, polished.
From onboarding to book discovery, seat booking to fine tracking — here are the final high-fidelity screens delivered to the Infosys engineering team.
Accessibility & Inclusivity
Designed for
everyone to use.
BibloFi was designed to be inclusive and accessible for all users — from day one, not as an afterthought.
Colour Contrast
Text and background colours tested using WebAIM Contrast Checker. Achieved a contrast ratio of 10.95:1 — well above WCAG AAA standards for readability.
WCAG AAA — 10.95:1Text Scalability
Typography uses relative units and flexible layouts, ensuring readability across devices and font sizes, aligning with WCAG 2.1 guidelines.
WCAG 2.1 compliantScreen Reader Ready
Interactive elements, headings, and buttons are clearly labelled in the design to support VoiceOver and other screen readers on iOS.
VoiceOver compatibleTouch Targets
All buttons and tappable areas meet Apple's minimum size guidelines (44×44pt) for easy, accurate interaction on all iPhone models.
Apple HIG compliantDesign system built on iOS 18 UI Kit (Figma Community) and Apple's Human Interface Guidelines — ensuring the app felt native and familiar to iOS users.
Usability Testing
20 real users.
Three core tasks.
I conducted usability testing with 20 participants to validate the design before final delivery. Each participant attempted three core tasks without any guidance — mimicking real-world use.
Task 1 — Search a book
18/20
completed successfully
2 participants hesitated with filter options before needing guidance.
Task 2 — Book a seat
17/20
completed successfully
3 found the confirmation step slightly unclear — improved in final iteration.
Task 3 — Check notifications
19/20
completed successfully
1 participant missed the icon placement initially.
90%
Overall task completion rate across all 3 tasks · 20 participants
Key improvement from testing: secondary navigation was unclear in early iterations. We restructured the tab bar and improved labelling — which was reflected positively in final feedback sessions.
The Details
Meet Oreo — the character
that made BibloFi, BibloFi.
A mascot with personality
Every great app has a soul. Oreo is the character we created to give BibloFi a unique theme and personality — a small detail that made the experience feel warm, playful, and human. Good UX isn't just about flows and components. It's about the moments that make users smile.
What I Learned
Growing as a designer
and a leader.
01
Abstract ideas need structure to become real
Starting from WhatsApp brainstorms and rough sketches, I learned how to translate messy, scattered ideas into structured, testable flows. The discipline of information architecture saved the team weeks of rework.
02
User feedback early saves time late
Getting real users into the testing process before the design was "perfect" led to better decisions. The confirmation step issue in seat booking would have shipped if we hadn't tested. That one finding alone justified the entire testing phase.
03
Leading a team of 10 is a design challenge
Communicating design decisions to 10 developers — each with their own mental model of the product — taught me that documentation and clear handoff specs are as important as the design itself. Good collaboration is a UX problem too.
04
Clarity over perfection under time pressure
Four weeks is not a lot of time. I learned to make principled trade-offs — choosing clarity and usability over aesthetic polish when the deadline demanded it. Shipping something good beats perfecting something that never ships.