Balancing Parenting and iOS App Development Challenges

I want to tell you something that most "developer journey" posts leave out.

There are nights I close my MacBook at 11pm having written maybe 20 lines of Swift. Nights where I spent more time debugging a layout issue in SwiftUI than actually building a feature. Nights where I questioned whether I started this too late, whether I'm too busy, whether DayOffPlanner will ever actually ship.

And then my son taps me on the shoulder before school and asks if we're training Taekwondo tonight. And everything resets.

That's the real story of balancing parenting and iOS development. Not a productivity hack. Not a perfect schedule. A constant, deliberate negotiation between who you're building for and who you're building with.

A comfortable home workspace that accommodates both parenting and app development.

I STARTED LATE — AND THAT'S OKAY

I began my iOS development journey in June 2024. I was already a husband, a dad, a full-time Product Owner, and a Taekwondo practitioner. There was no "good time" to start. I just started.

The developer community online can feel intimidating when you're new. Everyone seems to have been coding since they were 12. GitHub profiles with years of commits. Portfolios full of shipped apps.

I had none of that. What I had was a problem I wanted to solve — people struggling to reclaim their days with clarity and calm — and a stubborn belief that I could build the solution.

If you're reading this as someone who started late, or is thinking about starting: do it. The best time was years ago. The second best time is right now.

DAYOFFPLANNER: BUILDING THE THING YOU PERSONALLY NEED

DayOffPlanner came from a real place. As a Product Owner by day, I'm constantly managing backlogs, priorities, and other people's roadmaps. But my own days? They were chaos.

I wanted a simple tool — not another feature-packed productivity monster — just something that helped me look at my day and feel calm about it. Clear priorities. A realistic plan. Permission to rest when the important things were done.

So I'm building it myself. In Swift. Learning as I go.

There's something uniquely motivating about building your own product versus building someone else's. Every bug I fix, every screen I design, every SwiftUI component I finally understand — it goes directly into something I care about. That's fuel when the late nights get hard.

HOW I ACTUALLY MAKE TIME FOR BOTH

I'm not going to pretend I have a perfect system. But here's what genuinely works for me:

Taekwondo with my son is non-negotiable. This isn't "family time I fit in between coding sessions." This is the anchor of my week. Training together teaches us both discipline, focus, and how to get back up when you fall. Those lessons apply directly to development and parenting equally.

I use my Product Owner skills on my own life. I maintain a personal backlog. Seriously. Features for DayOffPlanner, tasks for the family, work deliverables — they all live in a prioritized list. I know what's in sprint and what can wait. This mental model reduces the overwhelm of juggling everything.

I protect small pockets of deep work. I don't need 4-hour coding blocks. I need 60-90 focused minutes where I'm not half-present. After my family is asleep, before they wake up, or during lunch — those pockets add up faster than you think.

I communicate openly with my wife. She's my partner in all of this. When I need a focused evening to push through a hard problem, I say so. When she needs me fully present, I close the laptop without resentment. That mutual respect is what makes the whole system work.

WHAT MY SON IS TEACHING ME ABOUT BUILDING

Kids are brutally honest feedback loops.

My son doesn't care about my code quality or my sprint velocity. He cares whether I showed up to training. Whether I watched his form. Whether I celebrated when he got a technique right.

That's good product thinking, honestly. Users don't care about your architecture. They care whether the thing works and whether you were there for them.

Parenting and building apps are more similar than they seem. Both require patience, consistency, a willingness to start over when something isn't working, and the humility to know you don't have all the answers yet.

CONCLUSION

I don't have it all balanced perfectly. Some weeks the app gets more attention than it should. Some weeks the family gets everything and the code sits untouched.

But I keep coming back to both. That's what being at your prime means to me — not peak performance in every area simultaneously, but showing up consistently for the things that matter most.

DayOffPlanner will ship. My son will keep growing. And I'll keep writing about the messy, real, worthwhile journey in between.

Thanks for being here for it.

— Wendell, Dellprime LLC