App Design
Web Development
Personal Project
FlexiFly
Inspired by my own travel frustrations, I designed a flight booking app that lets users search within date ranges to find the best deals. A streamlined UI and visual pricing calendar reduced booking time by 40%.
Year :
2024 - 2025
Role :
● UX Designer
● Web Developer
Team :
Only me!
Skills :
● Product Strategy
● UX Research
● Web Development
● Prototyping
The Problem :
As an international student flying between India and the U.S., I was constantly juggling open-ended travel plans, holidays, internships, semester breaks. The problem? Most flight booking tools weren’t built for flexibility.
They forced me to enter exact dates even when I didn’t know them. Searching for affordable flights meant running dozens of date combinations manually, copying results into spreadsheets, and trying to spot patterns.
It was tedious, time-consuming, and honestly kind of broken. So I decided to design a better way.
The Idea :
What if flight search started with your flexibility, not your fixed plans?
I imagined a tool where you could enter a range of departure dates and a range of return dates, and instantly see the best trip combinations, with prices and trip lengths visible in one view.
That became the core interaction that drove every design decision in FlexiFly.
I designed FlexiFly to rethink flight search around flexibility, visibility, and control.
Research :
I interviewed 7 budget-conscious travelers, mostly international students like me. Every one of them had the same pain: they had flexibility but no way to use it effectively.
Some used Google Flights’ calendar view, others manually checked different combos. Most gave up after a few searches. They were either overwhelmed or just didn’t trust the system to show them the best option.
So I mapped out what a flexible flight search should actually do:
• Let users explore a wide range of dates
• Make price trends obvious, not buried
• Show trip length up front (because 5 days vs. 11 days matters)
Prototyping :
I started in Figma with low-fidelity wireframes, then built up a system around three key design pillars:
Rigid search flows :
Users select flexible departure and return date windows. FlexiFly then analyzes all viable combinations, like Oct 10–12 out, Oct 18–20 back, and surfaces the cheapest options with trip durations calculated.
Color-Coded Grid View :
An interactive grid visualizes every possible trip combo. Each cell shows price and trip length. Cheaper trips appear in green, making standout options easy to spot in seconds.
Smart Filtering and Suggestions:
Users can filter by trip length, toggle between “Best Price” and “Best Time,” and get suggestions for nearby airports or cheaper date shifts.
Key Insight: People don’t mind flexibility, but they need tools that help them see the tradeoffs. Price, time, and trip duration should be surfaced, not buried.
Testing & Iteration :
I tested with students planning winter break trips. They loved the clarity, but a few things stood out:
• Users needed clearer legends for price colors
• Some wanted to filter trips by exact duration (e.g. 7–10 days)
• Others struggled with small-screen date selection
I responded by adding tooltips, slider filters for trip length, and mobile-friendly drag-to-select date pickers. Each iteration cut down on friction and helped users find answers faster.
The Build :
To prototype the frontend, I used generative AI tools like Replit and Claude to build interactive components and logic for the date grid. This cut my development time by 35%, letting me test and refine designs faster.
Two ways to book :
Outcomes :
By the end of the semester, FlexiFly had :
65%
improvement in flight deal discovery resulted from introducing flexible date range selection.
40%
faster booking process was achieved through optimized search and filtering experiences.
35%
Increase in feature engagement through clear, visual pricing tools
What I Learned :
I had some reflections by the end of this project :
Designing for uncertainty creates real user value, if you surface the right signals
Visual thinking (grids, colors, durations) beats filters and dropdowns
The best UX sometimes comes from rethinking defaults, not adding more features
More Projects
App Design
Web Development
Personal Project
FlexiFly
Inspired by my own travel frustrations, I designed a flight booking app that lets users search within date ranges to find the best deals. A streamlined UI and visual pricing calendar reduced booking time by 40%.
Year :
2024 - 2025
Role :
● UX Designer
● Web Developer
Team :
Only me!
Skills :
● Product Strategy
● UX Research
● Web Development
● Prototyping
The Problem :
As an international student flying between India and the U.S., I was constantly juggling open-ended travel plans, holidays, internships, semester breaks. The problem? Most flight booking tools weren’t built for flexibility.
They forced me to enter exact dates even when I didn’t know them. Searching for affordable flights meant running dozens of date combinations manually, copying results into spreadsheets, and trying to spot patterns.
It was tedious, time-consuming, and honestly kind of broken. So I decided to design a better way.
The Idea :
What if flight search started with your flexibility, not your fixed plans?
I imagined a tool where you could enter a range of departure dates and a range of return dates, and instantly see the best trip combinations, with prices and trip lengths visible in one view.
That became the core interaction that drove every design decision in FlexiFly.
I designed FlexiFly to rethink flight search around flexibility, visibility, and control.
Research :
I interviewed 7 budget-conscious travelers, mostly international students like me. Every one of them had the same pain: they had flexibility but no way to use it effectively.
Some used Google Flights’ calendar view, others manually checked different combos. Most gave up after a few searches. They were either overwhelmed or just didn’t trust the system to show them the best option.
So I mapped out what a flexible flight search should actually do:
• Let users explore a wide range of dates
• Make price trends obvious, not buried
• Show trip length up front (because 5 days vs. 11 days matters)
Prototyping :
I started in Figma with low-fidelity wireframes, then built up a system around three key design pillars:
Rigid search flows :
Users select flexible departure and return date windows. FlexiFly then analyzes all viable combinations, like Oct 10–12 out, Oct 18–20 back, and surfaces the cheapest options with trip durations calculated.
Color-Coded Grid View :
An interactive grid visualizes every possible trip combo. Each cell shows price and trip length. Cheaper trips appear in green, making standout options easy to spot in seconds.
Smart Filtering and Suggestions:
Users can filter by trip length, toggle between “Best Price” and “Best Time,” and get suggestions for nearby airports or cheaper date shifts.
Key Insight: People don’t mind flexibility, but they need tools that help them see the tradeoffs. Price, time, and trip duration should be surfaced, not buried.
Testing & Iteration :
I tested with students planning winter break trips. They loved the clarity, but a few things stood out:
• Users needed clearer legends for price colors
• Some wanted to filter trips by exact duration (e.g. 7–10 days)
• Others struggled with small-screen date selection
I responded by adding tooltips, slider filters for trip length, and mobile-friendly drag-to-select date pickers. Each iteration cut down on friction and helped users find answers faster.
The Build :
To prototype the frontend, I used generative AI tools like Replit and Claude to build interactive components and logic for the date grid. This cut my development time by 35%, letting me test and refine designs faster.
Two ways to book :
Outcomes :
By the end of the semester, FlexiFly had :
65%
improvement in flight deal discovery resulted from introducing flexible date range selection.
40%
faster booking process was achieved through optimized search and filtering experiences.
35%
Increase in feature engagement through clear, visual pricing tools
What I Learned :
I had some reflections by the end of this project :
Designing for uncertainty creates real user value, if you surface the right signals
Visual thinking (grids, colors, durations) beats filters and dropdowns
The best UX sometimes comes from rethinking defaults, not adding more features
More Projects
App Design
Web Development
Personal Project
FlexiFly
Inspired by my own travel frustrations, I designed a flight booking app that lets users search within date ranges to find the best deals. A streamlined UI and visual pricing calendar reduced booking time by 40%.
Year :
2024 - 2025
Role :
● UX Designer
● Web Developer
Team :
Only me!
Skills :
● Product Strategy
● UX Research
● Web Development
● Prototyping
The Problem :
As an international student flying between India and the U.S., I was constantly juggling open-ended travel plans, holidays, internships, semester breaks. The problem? Most flight booking tools weren’t built for flexibility.
They forced me to enter exact dates even when I didn’t know them. Searching for affordable flights meant running dozens of date combinations manually, copying results into spreadsheets, and trying to spot patterns.
It was tedious, time-consuming, and honestly kind of broken. So I decided to design a better way.
The Idea :
What if flight search started with your flexibility, not your fixed plans?
I imagined a tool where you could enter a range of departure dates and a range of return dates, and instantly see the best trip combinations, with prices and trip lengths visible in one view.
That became the core interaction that drove every design decision in FlexiFly.
I designed FlexiFly to rethink flight search around flexibility, visibility, and control.
Research :
I interviewed 7 budget-conscious travelers, mostly international students like me. Every one of them had the same pain: they had flexibility but no way to use it effectively.
Some used Google Flights’ calendar view, others manually checked different combos. Most gave up after a few searches. They were either overwhelmed or just didn’t trust the system to show them the best option.
So I mapped out what a flexible flight search should actually do:
• Let users explore a wide range of dates
• Make price trends obvious, not buried
• Show trip length up front (because 5 days vs. 11 days matters)
Prototyping :
I started in Figma with low-fidelity wireframes, then built up a system around three key design pillars:
Rigid search flows :
Users select flexible departure and return date windows. FlexiFly then analyzes all viable combinations, like Oct 10–12 out, Oct 18–20 back, and surfaces the cheapest options with trip durations calculated.
Color-Coded Grid View :
An interactive grid visualizes every possible trip combo. Each cell shows price and trip length. Cheaper trips appear in green, making standout options easy to spot in seconds.
Smart Filtering and Suggestions:
Users can filter by trip length, toggle between “Best Price” and “Best Time,” and get suggestions for nearby airports or cheaper date shifts.
Key Insight: People don’t mind flexibility, but they need tools that help them see the tradeoffs. Price, time, and trip duration should be surfaced, not buried.
Testing & Iteration :
I tested with students planning winter break trips. They loved the clarity, but a few things stood out:
• Users needed clearer legends for price colors
• Some wanted to filter trips by exact duration (e.g. 7–10 days)
• Others struggled with small-screen date selection
I responded by adding tooltips, slider filters for trip length, and mobile-friendly drag-to-select date pickers. Each iteration cut down on friction and helped users find answers faster.
The Build :
To prototype the frontend, I used generative AI tools like Replit and Claude to build interactive components and logic for the date grid. This cut my development time by 35%, letting me test and refine designs faster.
Two ways to book :
Outcomes :
By the end of the semester, FlexiFly had :
65%
improvement in flight deal discovery resulted from introducing flexible date range selection.
40%
faster booking process was achieved through optimized search and filtering experiences.
35%
Increase in feature engagement through clear, visual pricing tools
What I Learned :
I had some reflections by the end of this project :
Designing for uncertainty creates real user value, if you surface the right signals
Visual thinking (grids, colors, durations) beats filters and dropdowns
The best UX sometimes comes from rethinking defaults, not adding more features