When your family thinks you're wasting your money.

Mindset · 6 min read

I've worked with enough first-time app founders to know that the hardest part isn't the design. It's not the budget. It's not even finding a developer. The hardest part is doing all of it while the people closest to you think you're making a mistake.

I had a client who was funding the entire project himself. Significant money. Coming out of his own pocket. He has two kids. One was cautiously supportive. The other thought he was wasting money and reckoned a mate of his could build it cheaper. There was also a business partner he hadn't told — because he knew if the app took off, that dynamic would get complicated.

None of that shows up in a project plan. But it's real. And if you're building your first app, there's a good chance something like it is happening in your life right now.

Why people around you don't get it

They don't get it because they can't see it yet. You've been thinking about this idea for months, maybe years. You've done the research. You've searched the App Store. You've talked to potential users. You've sat with the problem long enough to know it's real. All of that context lives in your head. The people around you see someone writing cheques for something that doesn't exist yet.

It's the same gap that makes it hard to explain your app idea to anyone who hasn't worked in your industry. The subject matter expertise that makes you the right person to build this also makes it harder to explain why it matters. You're so deep in the problem that you forget other people don't see it.

This isn't a communication failure. It's a timing issue. They'll get it when they can tap through the prototype on their phone. They'll get it when they see the first version working. They'll get it when real users start saying "this is exactly what I needed." But right now, in the middle of the build, they just see the money going out.

The kid who thinks he can do it better

This one comes up more than you'd think. A family member who's "good with computers" or studying something tangentially related decides the whole thing is overpriced and they could have done it. I've seen it with kids, partners, mates. Someone who's watched a YouTube tutorial on app development and now thinks five weeks of professional design work is unnecessary.

It's not malicious. Usually it's protective. They don't want you to waste money. They think they're helping. But the gap between knowing how to code and knowing how to design, research, prototype, and prepare a product for real users is enormous. It's the difference between knowing how to hammer a nail and knowing how to build a house.

The client I mentioned? His kid saw the early designs and said it "looks like something from the nineties." A few weeks later, after the prototype was further along, the tone changed completely. The work speaks for itself eventually. You just have to survive the gap between starting and having something to show.

The person you don't tell

This is the one that gets me. The client had a business partner he deliberately kept in the dark. Not because of conflict. Because of success. If the app works, the dynamic changes. Money changes relationships. Ideas change relationships. And some people in your life will react to your success in ways that have nothing to do with the app.

I'm not a therapist. I'm a designer. But I've sat across from enough founders to know that the emotional weight of building something is real, and it's usually carried alone. Partners hear about it at dinner. Kids see the late nights. Friends get the edited version. Nobody gets the full picture because nobody's in the same headspace.

That's part of what the design process can give you, if it's done right. Someone who's in it with you. Who understands the idea, takes it seriously, and doesn't make you feel stupid for caring about it. That's not a soft benefit. For a solo founder spending their own money on something nobody else believes in yet, it's everything.

It gets easier when they can see it

The prototype changes everything. The moment you hand your phone to someone and they can tap through your app — real screens, real flow, real experience — the conversation shifts from "you're spending how much?" to "oh, this is actually good." That shift happened with this client's wife, who became one of the best usability testers we had. It happened with the kid who thought it looked like something from the nineties.

Until then, you're carrying the vision alone. That's not a flaw in the process. It's the nature of building something new. Nobody believed in the thing until the thing existed. That's true for every product, every business, every creative project in history.

So if you're in that gap right now — spending the money, doing the work, and fielding doubts from the people you love — know that it's normal. It doesn't mean you're wrong. It means you're early.

Related blog posts:

Self-funding your app →

The notebook you've been ignoring →

What if nobody downloads it? →