Building a Wedding Media Sharing SaaS and the Journey

SaaS wedding app development journey

Introduction

I started building WeddedTogether in the later half of 2024. Starting this project was exhilarating. I was full of enthusiasm, ready to dive into the code and build something unique. The concept was clear: create a platform where wedding guests could effortlessly share photos with the couple. The initial stages were smooth, and I quickly laid the groundwork for the app. It felt great to see my ideas taking shape in code.

The Challenge: Anonymous Sign-Ups and Media Uploads

As I progressed, the first big challenge emerged: designing a seamless anonymous sign-up process. My goal was to allow users to scan a QR code at a wedding and instantly start uploading images without a cumbersome registration process. This required linking users to specific storage buckets for media uploads while maintaining anonymity.

I began researching backend solutions to handle this. Supabase initially seemed like a strong choice for managing user authentication and storage. However, as I delved deeper into the implementation, I realised this was more complex than I anticipated. Balancing user experience, security, and ease of integration became a puzzle I needed to solve.

Life Happens: Losing Momentum

Around this time, my personal life got busier, and progress on the app slowed. While I wasn’t actively coding, the project stayed on my mind. I spent time reflecting on the user flow and brainstorming better solutions. For instance, I thought more about how users would interact with the platform and considered alternative ways to handle media uploads efficiently.

Revisiting the Plan: Exploring Upload Services

One aspect I’ve been stuck on is choosing the right upload service. Initially, I leaned towards using Supabase, but I’ve recently started considering UploadThing as an alternative. Each option has its own strengths, and I’ll need to explore which is better suited for this app’s needs. Factors like ease of integration, scalability, and cost will heavily influence this decision.

Leveraging AI: Coding Smarter, Not Harder

During my break from active development, I also began exploring how AI could help me code more effectively. AI tools like ChatGPT and GitHub Copilot have proven to be invaluable for generating boilerplate code, debugging, and even brainstorming features. These tools have reignited my enthusiasm for the project, showing me that I don’t need to tackle every challenge alone.

Setting New Goals for the New Year

As we enter a new year, I’ve set a clear and ambitious goal: to launch this app within Q1 and attract paying customers. I envision this platform as a short-lived solution tailored specifically for wedding events. To align with this vision, I plan to implement a one-time Stripe payment system. Once the event ends, uploads will be stopped after the first week. This ensures a simple and focused experience for users, while also managing storage costs effectively.

This goal has given me renewed focus and motivation. With a launch timeline in mind, I’m streamlining my tasks and prioritising features that are essential for the MVP. My immediate next steps include:

  • Finalising the upload service after thoroughly evaluating Supabase and UploadThing.
  • Implementing the anonymous sign-up flow linked to QR codes.
  • Integrating Stripe for seamless one-time payments.
  • Setting up functionality to stop uploads one week after the event.

Moving Forward: Renewed Focus

Now, with fresh ideas and a clearer understanding of the project’s direction, I’m ready to dive back in. This journey has already taught me a lot about balancing technical challenges with life’s demands. I’m excited to see where this project takes me and how it evolves as I continue to learn and grow.