Latest / The Founder's Journey with Fexingo: First-Time Entrepreneurs, Failures, and Lessons Learned / The Founder Who Built an App After Being Rejected by App Store
Transcript
- Lucas: When Apple rejected Sarah Chen's app for the seventh time, she didn't get angry. She got curious. And that curiosity built a twenty-eight-million-dollar business. Luna: Seventh time — I have to ask, what kind of app was she trying to get into the store? Lucas: It was a project management tool aimed at small construction crews. Think Trello, but built for workers who are often on-site, not at a desk. The core idea was solid, but Apple kept flagging it for guideline violations — specifically around how it handled user-generated content and file sharing. Luna: Right, the infamous section 4.2 and 5.2 rules. I've heard developers say those are the vaguest guidelines in the entire App Store Review book. Lucas: Exactly. And Sarah, who was a solo founder at the time — she had no legal team, no developer relations contact at Apple — she had to interpret each rejection herself. The first one was about metadata. The second was about incomplete UI. But by the fourth and fifth, they were deeper: Apple felt the app could be used to distribute copyrighted blueprints or share sensitive project files outside a controlled environment. Luna: Which is a legitimate concern, but also a massive grey area. So instead of fighting it, she built a web app first. Lucas: She launched a web-only version called TaskBridge in early 2022. No iOS app. No Android app. Just a responsive web app that worked perfectly on a phone browser. And within six months, she had twelve thousand teams signed up. Construction crews in Texas, landscapers in Oregon, even a small architecture firm in Dublin. Luna: So the rejection actually forced her to validate demand without the App Store's distribution engine. That's a hard way to start, but it also means you know people really want your product. Lucas: Exactly. If she'd gotten approved on the first try, she might have spent a year iterating on features nobody needed. Instead, she spent that year talking to users who found her through web search and word of mouth. By the time she finally went back to Apple — with a much more mature product — she had leverage. Luna: Did they approve it the eighth time? Lucas: They did. But by then, the web app had already generated over two million dollars in revenue. The iOS version became an add-on, not the core. And two years later, TaskBridge is at twenty-eight million in annual recurring revenue, about 70 percent from web users, 30 percent from mobile. Luna: That's such a counterintuitive story for anyone who thinks you need to be in the App Store to succeed as a consumer-facing app. Lucas: It really is. And it speaks to a broader pattern we've seen on this show — rejection that redirects you toward a better path. But what I find most interesting is the specific mechanism here: the App Store guidelines forced Sarah to think about data security and content moderation much earlier than most founders do. Luna: Because Apple's feedback, even if frustrating, pointed to real risks. Sharing construction blueprints is actually a liability issue if they leak. Lucas: Right. So she built encryption, role-based access, and audit logs into version one. That turned into a competitive advantage when TaskBridge started winning contracts with larger firms that required those features for compliance. Luna: It's like the rejection was a free security audit. Lucas: Absolutely. And you know, this is the kind of thing that makes me appreciate the listeners who support the show. A handful of folks chip in monthly through buy me a coffee dot com slash fexingo, and that's what lets us keep digging into stories like this without any ads. It's a small group, but it genuinely makes a difference. Luna: Yeah, and we're grateful. It means we can spend time on these deeper dives instead of rushing to a sponsor read. Lucas: So back to Sarah — the interesting part is that she didn't abandon the mobile dream. She just deprioritized it. And when she did launch on iOS, the app had a 4.8 star rating because it was mature and well-tested. Luna: I want to know more about the specific rejection letters. Was there one that really changed her thinking? Lucas: The big one was rejection number five. Apple's review team said the app's file-sharing feature could allow users to share 'objectionable content,' which is a catch-all phrase in their guidelines. Sarah realized they were right — she hadn't built any content flagging system. So she spent three months building a machine learning model that could detect inappropriate file types and flag them for review. Luna: That is a huge engineering investment for a solo founder. Lucas: Huge. But it also became a core selling point. When TaskBridge eventually went after enterprise clients, they loved the built-in moderation. Competitors like Basecamp and Asana didn't have that kind of granular control at the time. Luna: So the rejection literally gave her a product moat. Lucas: Exactly. And I think that's the deeper lesson here — not just that rejection can be redirection, but that the specific terms of the rejection can reveal a gap in your thinking that your competitors haven't addressed. Luna: Did she ever consider just giving up on the idea entirely after the seventh rejection? Lucas: She says she came close. She had about six months of runway left in her savings, and she was starting to wonder if the market really wanted a construction-specific project management tool. But the web launch proved there was demand. She told me that the seventh rejection was actually a relief — it forced her to commit to the web-first strategy without second-guessing. Luna: That's such a founder mindset: treat every 'no' as data, not as final judgment. Lucas: Right. And now TaskBridge has over four hundred thousand registered users. They've expanded beyond construction into field services, logistics, and even event planning. The common thread is that these are industries where workers are mobile, not desk-bound. Luna: I'm curious — did she ever go back and re-read the early rejection letters? Like, as a victory lap? Lucas: She did. She framed the seventh rejection letter and hung it in her office. It's next to a photo of the first hundred users — all of whom came from the web app, not the App Store. Luna: That's a great visual. For founders listening who are stuck on a rejection right now — what's the one tactical takeaway from Sarah's story? Lucas: I'd say this: don't read rejection as a verdict on your idea. Read it as a specific piece of feedback about your execution. Sarah's idea was fine. The execution — the security model, the content moderation — needed work. The rejection told her exactly where to improve. And she did. Luna: Also, maybe consider going web-first if you're a solo founder. The distribution is harder, but the iteration cycle is faster. Lucas: That's exactly right. And it's worth noting that TaskBridge still doesn't have an Android app. They built for the platform that made the most sense for their users, not the one with the most hype. Luna: So the story is really about focus. Focus on the problem, not the platform. Lucas: Exactly. And I think that's a good note to end on. Sarah Chen turned seven rejections into a twenty-eight-million-dollar business by listening to what the rejection was actually telling her. Thanks for listening, everyone.