How to determine app idea is technically feasible as a non-technical founder?

I had a call last week with a non-technical founder who pitched me a “digital allowance” app for kids. Ten minutes in it became clear the core question wasn’t funding, design, or even hiring — it was whether the thing could exist inside Apple’s walled garden. If that sounds familiar, you’re in the right place (and yes, I’ve been down this rabbit hole more than once).

Before you touch a line of code or book a discovery workshop, back up and interrogate the problem itself. Talk to a group of parents who struggle with screen-time battles. Ask what they do today, what hurts, and what would make them reach for their wallet. I’m not entirely sure preselling is always possible — some parents want to see a working app before paying — but getting three of them to say “I’ll pay when you ship” is worth more than any agency quote.

Once the pain is confirmed, bring in professional skeptics. A short, free consultation with two or three mobile agencies gives you a sanity check on both feasibility and cost. Don’t settle for “Sure, that’s doable.” Ask for the ugly bits: Which APIs are off-limits? How did their last app that touched Screen Time land with App Review? You’ll notice answers diverge; that’s the signal you need deeper digging.

Platform constraints are the real boss level. On iOS you can’t just read global usage stats unless the user hands over the keys through Apple’s FamilyControls framework — and even then you’re boxed into predefined categories. Android is looser but still clamps down starting with Android 13’s new privacy buckets. I could be wrong, but as of November 2023 there’s no public API that lets a third-party app silently tally screen minutes across every other app. Know those limits early or you’ll spend months chasing ghosts.

The cheapest proof is a throwaway prototype. Consult with an iOS expert to discuss the feasibility of detecting TikTok usage for Child A and logging it in real time. No fancy UI, no onboarding — just hard evidence the API answers the call. If they circle back saying it can’t be done without Device Management profiles, believe them and pivot. I’ve watched teams ship a clickable Figma, raise seed money, then discover in week one of coding that Apple simply says “No.” Don’t be that headline.

Posting a POC gig on Upwork works too, with one caveat: filter for devs who explain why something won’t work, not just how they’ll do it. More than once I’ve seen founders burn three months on a cheap contractor, end up with a Franken-app, then start over. My rule of thumb: if three independent freelancers point at the same roadblock, assume it’s real until proven otherwise.

The non-technical shortcut everyone forgets is talking to customers again — this time with evidence. A 30-second screen recording of your shaky prototype running on TestFlight beats a 20-page pitch deck. Some parents will still wait for the App Store link (credibility matters), but you’ll quickly learn whether the carrot-and-stick reward system has legs or if they’re happy with Apple’s built-in Screen Time controls.

My current take: full, automatic screen-time tracking plus rewards is probably impossible on iOS without leaning on Apple’s parental-control ecosystem, and even then you’ll hit privacy prompts that nuke the UX. Could that change next WWDC? Maybe. Until then, pressure-test the idea with users, build the tiniest on-device demo you can, and keep a healthy skepticism when an agency says “sure, no problem.”