PetQlix is live on iOS and in closed Android testing.
Petqlix didn't start with a framework or a formal plan. It started as an idea I couldn't let go of—an app for pet parents that I kept thinking about for nearly five years before I wrote a single line of code. What changed wasn't the idea—it was me.
I didn't study computer science. I learned by doing. First came Python—then JavaScript, React, SQL. Eventually I landed on React Native through Expo, which felt right for building real mobile apps. There was no curriculum, no certificate, and no formal order—just constant iteration and problem-solving. Most of what I know came from documentation, building things that broke, and figuring out why they broke.
But more than any specific language, I learned how to learn. That's the skill that made everything else possible.
Before going mobile, I built Petqlix as a web app. This version wasn't meant to ship—it was a sandbox. I wanted to understand user flows, authentication, and how backend systems connect to interfaces. It helped me make mistakes early, in a low-stakes environment, so I could move faster later.
Somewhere along the way, I started working with AI tools—not to write code for me, but to move faster. This is what people call "vibe coding." It's not about outsourcing the thinking—it's about removing friction so you can focus on what matters: architecture, UX, system design.
AI tools don't replace understanding. They amplify it. They let you prototype faster, catch edge cases earlier, and iterate more confidently. But you still need to know what you're doing—otherwise you're just debugging someone else's guesses.
This wasn't a weekend project. I built and integrated full production infrastructure—systems that are used in real apps shipping to users today:
- Firebase: Auth, Firestore, Cloud Functions, Storage
- Google Cloud Run: Scalable serverless API hosting
- RevenueCat: Subscription and paywall management
- Google Maps API: Location-based features for local discovery
- Push notifications, deep linking, analytics, and more
Each piece took time to understand—reading docs, debugging edge cases, refactoring when something didn't scale. But every integration taught me something new about how real apps are built.
One of the most underrated parts of building an app is shipping it. Getting through the store review processes taught me more than most tutorials ever did:
- Navigating the Google Play Store submission flow
- Setting up an Apple Developer account and going through TestFlight
- Dealing with privacy policies, app permissions, and metadata requirements
- Understanding why apps get rejected—and how to fix them
- Testing on real devices with real users
Petqlix is now in testing through both Google Play and Apple TestFlight. It's real, and real people are using it.
For me, this app is more than a product. It's proof that:
- Self-teaching works—if you build real things along the way
- Persistence matters more than talent or timing
- You don't need permission to ship—just follow through
- A 5-year-old idea can still become something real
The product is still evolving—and so am I. But the idea that once lived only in my head is now tested, deployed, reviewed, and real.