Vibe coding iOS App [Day 30]

Vibe coding an AI-powered quotes app using a bunch of AI tools in 30 days—because why not let AI do the heavy lifting?

This blog is my 30-day adventure, from idea to launch, proving just how much faster things get when you have AI as your coding buddy.

---

Day 30: Not Shipped, Not Even Close, But Still Alive

Well, here we are—Day 30. The grand finale. The big reveal. The moment where I proudly announce, “The app is live!”

Except… it’s not.

Not even close. The app is nowhere near done. Features are missing, the landing page is still in pieces, and my brain? Currently in debug mode. This whole project is a beautiful mess, but hey, progress is progress, right?

What Went Wrong? (A Long List)

So, what’s been eating up all my time? Let’s break it down:

1. React Native Tabs – My Personal Nightmare
   Early on, I wasted a few days (more like an eternity) trying to integrate react-native-tabs, which, in theory, should have been a plug-and-play solution. But in reality? It was a complete disaster. No matter what I tried, it refused to work properly.

After enough frustration to power a small sun, I gave up and just built my own version from scratch. Because when AI-generated solutions fail, good old manual coding still saves the day.

2. Reinventing Components – Because Why Not?
   While working on the UI, I realized there were a bunch of repeated elements—buttons, input fields, text blocks—stuff that kept showing up on multiple screens. So instead of copy-pasting like an amateur, I took a step back and built reusable components to save time in the long run. 😬

Did it actually save time? Not really, because I still spent hours tweaking them. But future me will thank past me for this, so let’s call it a win.

Finally, Some Real Progress: The Core Feature

One major milestone—one complete app flow is done! 🎉

With that out of the way, I moved on to the core feature that makes this app special: the text-behind-image effect.

In the meanwhile i managed to get logos done for the app, which looks good. Atleast something to chear about. 🤓

Text-Behind-Image Feature: A Never-Ending Struggle

I thought this would be a fun challenge to tackle in React Native. Turns out, it was a terrible idea.

• Issue #1: Couldn’t even get a local version up and running.
• Issue #2: Handling images and text positioning in React Native? An absolute nightmare.
• Issue #3: My MacBook, still bitter from Day 15, started throwing tantrums again.

So, after fighting React Native for days, I made the executive decision to move everything to the backend using Python and image processing libraries. Suddenly, things started working.

Some of the visuals from the last night text-Behind-Image coding sessions. Still far from being complete from developing the actual algo. 🤓

What’s Next?

The text-behind-image feature should (hopefully) be wrapped up soon. Once that’s done, I can finally stop feature development and focus on getting this thing out the door.

Will I finish in the next few days? Unlikely.
Will I keep going until it’s shipped? Absolutely.

So while Day 30 may not be launch day, it’s not failure—just a slightly extended timeline. Welcome to software development, where “It’ll be done in a month” is the biggest joke of all. 😅