TravelShare

A travel-focused social app which helps travelers connect, plan, build and share their travels.

Comment

IMPORTANT

  • The app is kind of unoptimized as this is the first time I have built a frontend app. Please bear with it a little and refresh if it seems to not be working (I missed adding options to improve Supabase client connection stability and session management due to which you will have to refresh the page after a tab switch, and I cannot patch this fix now after submission deadline). The app works - it is just my lack of experience that is the problem (人 •͈ᴗ•͈)

  • There is no compression or optimizations for posts data transfer so please wait for ~30s for posts to load on a page.

  • For login use any of the following email and password:

  • judge1@email.com, qwerasdf

  • judge2@email.com, asdf9731

  • judge3@email.com, zxcv8609

  • judge4@email.com, poiu4275

  • judge5@email.com, lkjh3164

  • judge6@email.com, vbnm9156

  • This is important as when a user wants to sign up then I have to allow it, so that bad parties do not sign up and spam the app, but you judges will need to login quickly and try out things.

Inspiration

I like travelling so having information from other travelers as well as from travel related product & service providers.

What it does

Users can use this platform for:

  1. Sharing posts about travel experiences.
  2. Get answers from AI that can use the data available on the platform to answer queries (using both text and media).
  3. Attach MCP servers so that AI chat can use their data for replying to user queries (useful for businesses such as malls, restaurants, transportation providers, etc).
  4. Add mini apps so that other users can open them within TravelShare (again useful for businesses).
  5. AI-generated itineraries that can be refined and shared.
  6. Travel Guides which are compilations of posts and itineraries created by users to share with other users.
  7. Heatmap for locations with good number of posts and listing posts in those particular locations.
  8. Listing posts within a radius of distance to find nearby travel experiences.
  9. Direct messages between users.

How I built it

I built it using Bolt, Supabase, Netlify, Gemini API and vanilla html, css, typescript.

Challenges I ran into

Complete lack of experience in frontend app development was the biggest issue and also why I could not optimize it more, or add more features. This is all I could do within my experience, Bolt token, project size and time limits.

Accomplishments that I am proud of

Building an app like this was never possible before because I am bad at frontend development. This is the first time I could build an app like this, thanks to Bolt.

What I learned

I learned about using Supabase, and got some more idea of frontend app development along with the complexity of building such an app which has both a frontend and backend.

What's next for TravelShare

  1. Significant optimizations (maybe moving to a frontend framework like react js).
  2. Building Android and iOS apps.
  3. Adding AI for showing only travel related posts in the app (and other things like memes are filtered out to keep focus on travel).
  4. Group chats where users can discuss travel plans, build communities, share events (such as concerts, festivals, occasions, etc).
  5. Collaborative itineraries for editing by multiple users.
  6. Offline itinerary access.
  7. Better search on Explore page so that users can have better results (suppose when searching for hiking or scuba diving related posts).
  8. Better backend to handle huge amounts of data efficiently.
  9. More-featureful expense tracker with dashboards and analytics for users to track their budgets on a trip.
  10. Bookmarking posts for future reference and making collections.
  11. Easy access to emergency services.
  12. AI-powered packing list generator.
  13. In-app translation between languages.
  14. Mini-apps which can use the user data from TravelShare to provide services so that users don't have sign-up to them separately.
  15. Having only verified users on the platform (unverified users can only view posts at most).
  16. Better heatmaps to show hotspots by content type.
  17. Better MCP integration to filter out any spammers and better integration across data from multiple MCP servers from various providers.
  18. Access to financial services for travelling - getting currencies, insurance, payment methods, etc.
  19. Subscription plans.
  20. Notifications.

Built With

Share this project:

Updates