Skip to main content

The behind-the-scenes story of how we chose our tech stack, what went wrong, and why we changed course

The Tech Stack We Chose (And Why We Switched Midway)

The Tech Stack We Chose (And Why We Switched Midway)

By Rexman
Published: 13/06/2025 – Behind the Scenes Series #2

🧠 The Master Plan

Choosing a tech stack was easy. Or so we thought. We had a Notion page comparing Postgres vs Mongo, Firebase vs Supabase, React vs Vue vs SvelteKit. We were acting like we were choosing our life partner — when really, we just needed a stack that wouldn’t break in 3 weeks.

We picked:

  • Frontend: React Native with Expo
  • Backend: Supabase (Postgres + Auth)
  • Storage: Supabase Storage
  • AI integration: Claude (Anthropic)
  • Deployment: Vercel

💥 Reality Bites

Week 1 was smooth. By Week 2, cracks appeared.

  • Supabase’s Postgres was fine… until our expensive queries choked it.
  • React Native was okay, but we hit prop-passing hell fast.
  • Claude integration was awesome… until we realized we needed more dynamic prompt chaining and Claude didn’t support that natively.
“Why is our dropdown breaking again?” — our frontender, twice a day.

🔄 The Course Correction

By Week 3, we knew we had to pivot — but only where it hurt most. We didn’t ditch everything. We changed enough to stay sane:

  • Moved login/email from Supabase to Claude + SendGrid for more flexibility
  • Switched Postgres → PlanetScale (MySQL-based, better handling of concurrent writes)
  • Replaced dropdowns and navigation logic with Radix + Expo Router

The app became 40% faster and way easier to debug.

📚 Lessons Burned into Our Brains

  • Speed > perfection: Don’t overplan the stack — plan for change.
  • Invest in dev experience early: Bad structure compounds pain fast.
  • Optimize for iteration, not architecture.

We still use Supabase in other projects. It just wasn’t right for this one at this stage.

⚖️ What Stayed

Some things did work well and stayed untouched:

  • Vercel + Edge Functions (fast deploys, perfect for MVP)
  • Claude for summaries + analysis (low latency, clean output)
  • Figma for quick UI updates

🎯 The Real Takeaway

“The right stack is the one that helps you ship fast — and makes you want to come back and improve it.”

🔜 Coming Up Next

Next Friday: Debugging Hell: One Bug That Nearly Crashed Our Launch

Labels:

Comments

  1. deanJune 15, 2026 at 11:36 AM

    This article provides an honest and practical look at the challenges of selecting a technology stack for a growing application. The discussion around evaluating tools, encountering real-world limitations, and making strategic mid-project adjustments highlights the importance of flexibility, developer experience, and rapid iteration when building modern software products.

    ReplyDelete
  2. deanJune 15, 2026 at 11:36 AM

    The technologies discussed, including React Native, Supabase, Vercel, and AI integrations, align well with Web Development Projects. Understanding how different frontend, backend, database, and deployment choices impact scalability and maintainability is valuable for students and developers working on full-stack applications.

    ReplyDelete
  3. deanJune 15, 2026 at 11:36 AM

    The article also demonstrates how modern JavaScript-based ecosystems enable rapid development and continuous improvement of digital products. Exploring ReactJS Projects can help students gain practical experience in building responsive user interfaces, managing application state, and developing scalable full-stack solutions.

    ReplyDelete

Post a Comment

Popular posts from this blog

PromptCraft Blog Series #7: Visual Prompt Design for No-Coders – Learn how to build effective AI prompt flows using visual tools in no-code platforms like Lovable, Bubble, and more

PromptCraft Series #7 – Visual Prompt Design for No-Coders ✨ PromptCraft Series #7 "Visual Prompt Design for No-Coders" 🗕️ New post every Monday 🎨 Why Visual Prompt Design Matters Prompt engineering doesn’t have to be text-only or code-heavy. Today, powerful no-code tools allow you to design, trigger, and connect prompts visually using simple blocks, fields, and flows. Drag-and-drop interfaces reduce human error Inputs can be dynamically passed to prompt templates Output logic can be reused across different use cases Non-developers can build intelligent apps visually This blog explores how to do it right — with examples, templates, and real platform walkthroughs. 🔧 Anatomy of a Visual Prompt Block Component Purpose 🔢 Input Field Captures dynamic user input (text, image, number) 🧠 Prompt Template Combines static in...
Post a Comment
Read more

PromptCraft Blog Series #6: Prompt Debugging and Optimization – Learn how to fix and improve AI prompt outputs for more accurate, helpful results.

PromptCraft Series #6 – Prompt Debugging and Optimization "As of May 2025, summarize one real, recent science discovery based on known sources. Add links if available and avoid speculation." ✨ PromptCraft Series #6 "Prompt Debugging and Optimization: Getting the Output You Want" 🗕️ New post every Monday 🔍 Why Prompts Sometimes Fail Even the best models can give you: ❌ Irrelevant answers ❌ Generic or vague responses ❌ Hallucinated facts or made-up data ❌ Wrong tone or misunderstanding of intent Often, it’s not the AI’s fault — it’s the prompt . 🔧 How to Debug a Prompt Start with these questions: Is the role or task clearly defined? Did you give examples or context? Are your constraints too loose or too strict? Did you format the output instructions properly? Then iterate your prompt, one element at...
Post a Comment
Read more