Why I Chose to Build My Own Apps Instead of Taking a Traditional Job (for now)

Recently, a friend suggested that I should get a traditional full-time job at a big company, work on my side projects in my spare time, and play it safe. While their advice was well-meaning, after thinking it through, I realized that this path doesn’t align with where I want to be right now.

Instead, I’ve decided to focus on building and launching my own apps. This choice is rooted in my years of experience as a Laravel developer and my desire to create something meaningful that’s entirely mine.

The Importance of Building My Own Apps

For years, I’ve worked hard developing apps for other people. While that was valuable, I’m now ready to channel that energy into my own ideas. Building apps for myself isn’t just about creating income—it’s about mastering the skills required to build a successful business, which is a much bigger win in the long run.

Laravel plays a huge role in enabling this journey. Its creator, Taylor Otwell, famously designed Laravel with the philosophy of building a framework that could help solo developers succeed. Laravel’s "batteries included" approach means it comes with powerful built-in features—authentication, routing, queues, and more—that allow me to focus on the big picture rather than getting bogged down in repetitive, low-level tasks.

For a solo developer like me, this philosophy resonates deeply. It empowers me to work efficiently and build ambitious projects on my own without relying on a team. It’s one of the reasons I love Laravel and continue to use it as the backbone for my apps.

The Lessons From Failed Projects

This isn’t my first time building personal projects. I’ve started and failed at several side projects in the past, and each one has taught me valuable lessons. For example, I recently decided to take one of my projects offline because I realized I didn’t care about it anymore. While building it, I learned a lot about development, hosting, and launching apps. But in the end, it wasn’t something I was passionate about, and it wasn’t generating income.

As developers, it’s completely normal to build many apps and example projects, including things that never get released. These projects are part of the learning process. They’re opportunities to try new tools, test ideas, and gain experience—even if they don’t lead to a finished product.

What I’ve learned is that starting and failing is part of the process. Much like exercising, it’s not always about the end result—it’s about the act of doing it and the growth that comes with it. Every failed project sharpens my skills and prepares me for the next one. In that sense, no project is truly a failure.

Build What You Care About

One of the most important lessons I’ve learned from working on my own projects is the importance of alignment. If you don’t genuinely care about what you’re building, it’s hard to stay motivated, especially when you hit roadblocks. Building something you’re passionate about makes it easier to push through the hard stuff, solve tricky problems, and see the project through to completion.

That alignment between what you want and what you’re working on is what keeps the process enjoyable. If you care about your app, every task—no matter how challenging—feels purposeful, and the reward of seeing it live is so much greater.

The Importance of CI/CD Early On

Another lesson I’ve picked up recently is the value of setting up Continuous Integration and Continuous Deployment (CI/CD) early in the development lifecycle. I heard this advice in a YouTube video, and it really clicked with me.

Having a CI/CD pipeline in place ensures that as soon as your app is ready, you can deploy it with confidence. It streamlines the process and allows you to focus on refining and improving your app without worrying about the technicalities of going live. Early setup of CI/CD is one of those things that might take a bit of time initially, but it pays off massively when you’re ready to launch.

Why Now Is the Right Time

I’m fortunate to have some savings and a casual job to support myself, giving me the flexibility to pursue this. While job opportunities are always out there, sometimes it’s best to take a chance on your own ideas and see where they lead.

Of course, I’d love for one of my apps to make money—that’s always the dream. But what’s even more valuable is the education I’m gaining by doing this. Building apps teaches me not just technical skills, but also how to manage projects, market ideas, and solve real-world problems. Education and self-learning have always been important to me, and I believe focusing on personal growth is just as rewarding as financial success.

This is about investing in myself and gaining the skills to create opportunities in the future, whether they come through my own ventures or other career paths.

Open to Opportunities, Especially Contract Work

That’s not to say I’m completely closed off to other opportunities. I really enjoy contract work as a developer—it allows me to stay sharp, work on exciting projects, and connect with other businesses while still leaving room for my personal pursuits.

If the right contract or even full-time role came along—something exciting and aligned with my goals—I’d absolutely consider it. But for now, my main focus is on my own projects and working casually or part-time in roles that suit me.

Check Out My Projects

If you’re curious about what I’m working on, check out my Projects Page. I regularly update it with new ideas, apps in progress, and tools I’ve built. It’s an evolving showcase of the work I’m passionate about, and I’m excited to share it with others.

What’s Your Dream?

I want to close with an important question inspired by Simon Squibb, an entrepreneur who challenges people to think deeply about their purpose and whose book, What's Your Dream?: Find Your Passion. Love Your Work. Build a Richer Life. is set to release on February 16, 2025: What’s your dream? What do you want to build or create in this world?

For me, my dream is clear: I love to create. The thrill of taking an idea from my head and turning it into something real—whether it’s an app, a tool, or a solution to a problem—is what keeps me motivated. Building something that didn’t exist before is deeply rewarding, not just because of the end result, but because of the process itself.

Simon Squibb emphasizes that when your work aligns with your passion, even the hard parts feel worthwhile. That’s a lesson I’ve learned firsthand. When you care about what you’re building, it’s easier to tackle tough challenges, stay consistent, and see the project through to completion.

So, what’s your dream? Whether it’s launching a product, learning a new skill, or pursuing an entirely different path, the key is taking action. Start small, build consistently, and enjoy the process—because building something you care about is always worth it.