TripBuddy – About the Project

🌍 Inspiration

The idea for TripBuddy came from noticing how stressful and time-consuming travel planning can be. People often spend hours switching between websites, checking reviews, searching for attractions, and trying to fit everything into a realistic schedule. I wanted to create a tool that would act like a personal travel assistant; one that understands a user’s interests and automatically builds a full, organized itinerary.

As someone interested in AI and real-world applications, this project felt like the perfect way to combine problem-solving, creativity, and technology into something practical and impactful.

What I Learned

This project taught me that building an AI-powered application is not just about writing code, but about designing systems that work together smoothly. Some key things I learned include:

How to integrate APIs to retrieve and structure real-world data
The importance of version control (Git) and resolving merge conflicts
How to balance frontend design with backend logic
How AI can transform user preferences into actionable recommendations

🛠️ How I Built TripBuddy

TripBuddy was built as an AI-powered travel assistant that generates a full vacation itinerary based on user preferences.

The process included:

Collecting user input such as interests, travel style, and destination
Processing preferences to determine which activities best match the user
Using APIs to gather travel-related data like attractions and activities
Structuring the itinerary by assigning times and organizing activities per day
Designing the interface so users can easily select options and view their plans

⚡ Challenges Faced

One of the biggest challenges was working with Git and collaboration. I encountered merge conflicts, diverged branches, and environment issues that slowed progress. However, these challenges helped me understand how real-world development teams operate and how important clean workflows are.

Another challenge was making the itinerary realistic. It wasn’t enough to just list activities, but the schedule had to make sense in terms of: