Inspiration

Trippit was born from a simple observation: first-time travelers often feel overwhelmed by the planning process and miss out on the joy of discovery. Our founders, BooManLag and mynrjad, experienced this firsthand during their early travel adventures.

After one particularly chaotic trip where everything that could go wrong did go wrong, they realized there was a gap in the market. Most travel apps focused on experienced travelers or were too complex for beginners. What if there was an app that combined practical planning tools with fun challenges and real advice from travelers who'd been there before?

That's how Trippit came to be - a lightweight travel companion that makes planning less stressful and the journey more fun, especially for those new to travel.

What it does

At Trippit, we believe that travel should be accessible and enjoyable for everyone, regardless of experience level. Our mission is to reduce the anxiety of travel planning while increasing the joy of discovery.

We do this by:

Simplifying the planning process with intuitive tools Providing real, crowdsourced advice from travelers who've been there Adding elements of fun and gamification to encourage exploration Creating a supportive community where travelers can share experiences Focusing on practical solutions to common travel problems Our goal is to help you create memories that last a lifetime, with less stress and more adventure.

How we built it

We built Trippit using a modern tech stack focused on developer experience and performance:

  1. Frontend: React with TypeScript for type safety, Vite for fast development, and Tailwind CSS for styling
  2. Backend: Supabase for authentication, database, and serverless edge functions
  3. API Integration: Reddit API for sourcing real travel tips from experienced travelers
  4. AI Integration: Google's Gemini API for generating personalized travel itineraries
  5. Deployment: Netlify for hosting with continuous deployment

The application follows a component-based architecture with custom hooks for state management. We implemented real-time features using Supabase's subscription capabilities, allowing for collaborative trip planning.

Challenges we ran into

  1. Reddit API Integration: Working with Reddit's API was challenging due to rate limits and authentication complexities. We had to implement sophisticated caching and fallback mechanisms.

  2. Edge Function Limitations: Supabase edge functions have specific constraints that required careful architecture decisions, especially for the AI-powered itinerary generation.

  3. Trip Sharing Logic: Implementing the invitation system with proper security was complex, requiring careful database design and RLS policies to prevent data leakage.

  4. Badge System: Creating a flexible achievement system that tracks progress across different activities required intricate database relationships and triggers.

  5. Mobile Responsiveness: Ensuring the pixel-art style UI worked well across all device sizes required extensive CSS tweaking and responsive design patterns.

Accomplishments that we're proud of

  1. Seamless Reddit Integration: Successfully pulling relevant travel tips from Reddit and presenting them in a user-friendly way.

  2. Engaging Game Mechanics: Creating a fun "Where'd I Go?" scenario game that actually teaches practical travel skills.

  3. Collaborative Features: Implementing a robust invitation system that allows friends to plan trips together.

  4. Pixel-Perfect Design: Achieving a cohesive pixel-art aesthetic throughout the application while maintaining usability.

  5. Performance Optimization: Building a responsive application that loads quickly even with complex data relationships.

What we learned

  1. Edge Function Architecture: We gained expertise in designing serverless functions that work within platform constraints.

  2. Supabase RLS Policies: We learned how to implement complex row-level security policies for multi-user data access.

  3. React Performance Optimization: We improved our skills in component memoization and state management for smoother UX.

  4. API Integration Patterns: We developed better strategies for working with external APIs, including caching and fallback mechanisms.

  5. Collaborative Development: We enhanced our workflow for parallel development on shared components and features.

What's next for Trippit

  1. Mobile App: Develop native mobile applications for iOS and Android to provide offline access to trip information.

  2. AI Trip Recommendations: Expand AI capabilities to suggest destinations based on user preferences and budget.

  3. Social Features: Add the ability to share completed trips and itineraries with the community.

  4. Integration with Travel Services: Connect with booking APIs to allow users to book flights, accommodations, and activities directly.

  5. Expanded Game Scenarios: Add more location-specific scenarios to the "Where'd I Go?" game for a richer learning experience.

Built With

Share this project:

Updates