u/Careful-Lie6719

Hey everyone,

I’m currently in the final stages of building out my app (a travel-focused brand called Letters To Somewhere) and I’ve realized my current database setup might not be the most sustainable once I actually go live on the App Store.

The Context: The app features travel planning tools, social writing features, and potentially a sensory journal component. Right now, I’m using a no-code/low-code backend (Base44), but I’m looking to migrate to something more robust and industry-standard that can handle growth without breaking the bank or my UI.

What I need to handle:

• Social Features: User profiles, following, and content sharing.
• Media: Storing and retrieving photos/travel content efficiently.
• Authentication: I’m already using Google Sign-In/OAuth.
• Scalability: I want to move now so I don't have to do a massive migration mid-growth.

The Ask:

1. For those who have migrated from a "starter" database to a production-grade one (like PostgreSQL, Supabase, or Firebase), what was your biggest "I wish I knew this before" moment?
2. Since I’m essentially a solo founder, should I lean toward a BaaS (Backend-as-a-Service) like Supabase for the ease of use, or go straight to a managed SQL database?
3. Any specific tips for mapping data during the migration to ensure I don’t lose the work I've already done on the front end?

I'm currently based in Canada and trying to keep the tech stack manageable while I focus on the product side. Would love any insights or "lessons learned" from your own migrations!

Thanks in advance!

Hey everyone,

I’m currently in the final stages of building out my app (a travel-focused brand called Letters To Somewhere) and I’ve realized my current database setup might not be the most sustainable once I actually go live on the App Store.

The Context: The app features travel planning tools, social writing features, and potentially a sensory journal component. Right now, I’m using a no-code/low-code backend (Base44), but I’m looking to migrate to something more robust and industry-standard that can handle growth without breaking the bank or my UI.

What I need to handle:

• Social Features: User profiles, following, and content sharing.
• Media: Storing and retrieving photos/travel content efficiently.
• Authentication: I’m already using Google Sign-In/OAuth.
• Scalability: I want to move now so I don't have to do a massive migration mid-growth.

The Ask:

1. For those who have migrated from a "starter" database to a production-grade one (like PostgreSQL, Supabase, or Firebase), what was your biggest "I wish I knew this before" moment?
2. Since I’m essentially a solo founder, should I lean toward a BaaS (Backend-as-a-Service) like Supabase for the ease of use, or go straight to a managed SQL database?
3. Any specific tips for mapping data during the migration to ensure I don’t lose the work I've already done on the front end?

I'm currently based in Canada and trying to keep the tech stack manageable while I focus on the product side. Would love any insights or "lessons learned" from your own migrations!

Thanks in advance!

Hi everyone,

I’ve been vibe-coding a project called Letters To Somewhere over the last month. It’s a travel themed digital journaling app combined with my stationary brand. I’ve been using Base44 to orchestrate the build.

I finally got site indexed on Google (huge win!) but as I’m moving out of the “honeymoon phase” of the build and into actual beta testing, I’m hitting a few snags where I’d love some perspective from the community.

I’ve been using a Sunday-prompt automation for weekly journal emails, but I’m finding that as I add more features, the AI generated logic is starting to feel a bit jumbled. How are you guys managing state/context when your app moves beyond a simple CRUD setup? Are you using DONT_DO.md files or version pinning to keep AI from breaking older features?

I also just cleared a major hurdle with robots.txt that got my URO searchable on Google. For those of you who have launched vibe coded apps, what’s your next move for SEO? Are you letting AI handle the metadata or are you manually tweaking the headers to ensure the “vibe” translates to search results?

My goal is for this to become a go to platform for digital travellers. If you’re a traveller, a journaler, or just someone who likes building cool stuff with LLMs, I’d love for you to poke around and tell me where the vibe feels off or where the tech could be tightened.

Tech Stack: Base44, google search console, Canva for assets, Printify for physical products.

Cheers 📝✨

I’m a designer and business owner based in Ontario. For the past few months, I’ve been building Letters to Somewhere, a digital vault for travelers.
The core idea is to bridge the gap between digital convenience and the tactile feel of old-school travel. Today, I finally finished the Passport Export feature. Instead of a standard spreadsheet or list, it generates a vintage-style PDF that tallies countries and cities visited, city counts, and correspondence status (like "Open When" letters).

The Goal:
I wanted to create something that feels like a "Certified Transcript of Migration" rather than just a data dump. I'm also a stationery designer on Etsy, so I’m really focused on making the digital UI feel as "ink-and-parchment" as my physical journals.
Looking for feedback on:

1. The "Passport" aesthetic—does it feel like a travel artifact?
2. The utility of "Open When" letters for long-term travel.

I’m inviting people slowly to the beta right now to fine-tune the experience. If you’re a traveler or a journaler, I’d love your thoughts!