An open API service indexing awesome lists of open source software.

https://github.com/jaismeen777/tripsy

Tripsy — A Jetpack Compose-based Android app that helps users plan trips based on mood, energy, and interests. Enables seamless planning, real-time itinerary adjustments, and collaborative trip planning. Technologies: Kotlin, Jetpack Compose, Firebase (Authentication & Firestore), REST APIs.
https://github.com/jaismeen777/tripsy

android firebase full-stack jetpack-compose kotlin mobile-app

Last synced: 2 months ago
JSON representation

Tripsy — A Jetpack Compose-based Android app that helps users plan trips based on mood, energy, and interests. Enables seamless planning, real-time itinerary adjustments, and collaborative trip planning. Technologies: Kotlin, Jetpack Compose, Firebase (Authentication & Firestore), REST APIs.

Awesome Lists containing this project

README

          

Tripsy – Smart Travel Planner
Tripsy is an intelligent, user-centric travel planning app that recommends personalized itineraries based on mood, energy, budget, and travel goals. It is designed to bridge the gap between traditional logistics-focused trip planning and emotional, experience-driven travel.

# Introduction
Tripsy aims to revolutionize the travel experience by focusing not only on the destination but also on the user’s emotional state, energy, and personal interests. From Pre-Trip planning to Ongoing Trip support and Post-Trip reflection, Tripsy ensures a seamless, personalized experience every step of the way.

# Problem Statement
Most existing travel apps focus only on logistics like flights, hotels, and tickets. They fail to consider:
*User mood or energy levels.

*Dynamic changes (e.g., weather, traffic).

*Group trip collaboration.

*Reflection and memory-keeping.

Tripsy aims to fill this gap, making travel an adaptive, emotional, and intelligent experience.

# Target Audience
*Individuals (18–50 years) seeking personalized, stress-free trips.

*Small groups, families, and solo travelers.

*Primarily urban users in developed countries.

# Value Proposition
*Save time and reduce decision fatigue with personalized suggestions.

*Discover unique, offbeat locations aligned with energy and interests.

*Enjoy an emotional travel companion, not just a checklist app.

# Salient Features
A. Pre-Trip Planner

*Calendar-Based Date Selection: Sync trip planning with your personal schedule.

*Mood & Energy Inputs: Get recommendations based on your vibe.

*Budget Optimization: Smart sliders + priority tags (e.g., splurge vs save) to manage budget spent on hotels,food,travel and shopping.

*Future Scope: Integrate weather, traffic, and venue availability.

B. Ongoing Trip Support

*Live Adjustment Engine: Alter itinerary based on weather, traffic, and user energy.

*Smart Notifications: Get alerts about delays, closures, or nearby alternatives.

*Firestore Integration: Enables group planning and live itinerary edits.

C. Post-Trip Reflection

*Mood-to-Memory Mapping: Reflect on trips using journaling prompts.

*Photo & Media Timeline: Build a visually rich timeline of trips.

# System Architecture & Tech Stack

-> Frontend

*Android Studio + Kotlin

*Jetpack Compose: Declarative, dynamic UI

-> User Authentication

*Firebase Authentication: Email, password, and third‑party sign-in.

-> Backend & Database

*Firebase Firestore: Real‑time database for trips, preferences, and collaborative planning.

-> Date & Time

*Integrated Calendar and Clock for selecting trip dates and time.

# Future Extensions

*Smart Conflict Resolver using weather, traffic, and venue data.

*AI‑Driven Trip Suggestions based on prior behavior.

*Integrated Social Features: User‑shared, mood‑based itineraries.

*Multi‑language AI Chatbot for global rollout.

# Conclusion
Tripsy goes beyond traditional travel planning. By focusing on mood, energy, and interests, it turns trips into memorable stories — making it not just a planner, but an emotional travel companion.

![image](https://github.com/user-attachments/assets/59b822b2-50ac-4993-acb2-8871399156fb)
![image](https://github.com/user-attachments/assets/7987072f-bba1-4412-a97e-63c58cd19ce3)

![image](https://github.com/user-attachments/assets/a48896ae-3556-4fc1-9e31-036a119333bf)
![image](https://github.com/user-attachments/assets/c8556b73-c77c-489d-b350-e7f50137d6d3)
![image](https://github.com/user-attachments/assets/013ba189-e69d-4c8a-b11e-116293d205b3)
![image](https://github.com/user-attachments/assets/6fcf1bd3-613e-42b3-948f-0304518c5358)
![image](https://github.com/user-attachments/assets/ada56586-1fae-4275-8d93-4faf6d32073b)

Although the project was developed earlier, the code was uploaded to GitHub at a later date due to security and confidentiality reasons. The commit timestamps do not reflect the actual development timeline, which took place months prior. This approach was taken to ensure sensitive information was properly secured before making the code publicly availables.