u/ConstantContext

App got approved after 5 rejections in 2 weeks. 25 minutes on a phone call with apple finally broke the loop
▲ 0 r/iosdev

App got approved after 5 rejections in 2 weeks. 25 minutes on a phone call with apple finally broke the loop

we've been building whip for the past 5 months. submitted to apple for review on april 29 after a few months on testflight. then watched it get rejected 5 times over the next 2 weeks.

for the first 4 rejections we kept doing the obvious thing. read the rejection, fix the cited issue, reply to apple via app store connect explaining what we'd changed. each round took 3 to 5 days. and the rejections started getting weird. apple would say things like "we couldn't find this in your privacy policy" when the thing was right there in section 18 with screenshots. they'd flag in-app controls that were exactly where we said they were. by rejection 4, every reply we wrote was longer than the last because we kept anticipating more misunderstandings.

eventually it clicked. the issue wasn't that we'd missed something technical. apple's reviewers weren't understanding what whip actually does, and email replies weren't fixing that.

here's what whip is:
you open the app, scroll a feed, and every post is a tiny playable mini-experience someone made. a trivia game for their friends. a countdown for an event. a wheel that picks who buys lunch among 4 specific people. you tap, you swipe, you play. if you like one, you can remix it. if you want to publish your own, you describe it in plain english and whip builds it right on your phone, in the app, in 2 minutes. no data collected, every post made for fun or some small personal utility.

what worried us was that apple seemed to be bucketing us with vibe-coding tools that help you build native ios apps. whip is not that. we don't help people ship apps to the store. it's a social feed of mini-experiences that live inside the whip app. if apple's reviewer had us in the wrong category in their head, every guideline they applied to us was going to be the wrong one, and no email reply was going to fix that.

so after rejection 5 we scheduled an app review call. apple offers them tuesdays and thursdays. there's a link to request one buried at the bottom of every rejection email and we'd ignored it for 4 rounds. on the call we walked them through what whip actually does. mini-experiences. playable. fun. no data collected. social feed, not native-app-builder. they understood within a few minutes and approved our app right on the call itself.

if you're stuck in a similar loop where apple keeps citing the same kind of misunderstanding, stop replying by email. schedule the call. for us it was the difference between another 2 weeks of guesses and 25 minutes of actually being heard.

ios app: https://apps.apple.com/us/app/whip-feed-for-ai-creations/id6758931714

for anyone here who's also done the app review appointment thing, was the call the unlock for you too?

u/ConstantContext — 7 days ago
▲ 1 r/nocode

is half of what people on this sub make actually non-saas, but we don't talk about it because there's no upvote for it

scrolled r/nocode this week. "finished 30+ vibe coded saas builds, same mistakes." "got my first 4 paid users." "i did my first app and it has been dead." most of what surfaces here is some version of "did the saas thing, here's where it landed."

what i don't see anywhere: posts from people building software that was never going to be a saas in the first place. a wheel that picks who buys lunch for four specific friends. a daily quiz a dad built for his 7-year-old son this morning (real example). a guy who scans his own toilet to turn off his alarms (again real example). these exist and they outnumber the saas attempts, probably by a lot, we just don't post about them here.

i think we collectively have a saas-shaped lens for what counts as a real "build." everything else gets quietly demoted to "weekend toy." but the weekend toy is actual software with actual users (4 friends, 1 kid, your group chat) and someone spent a saturday on it because it mattered.

a small group of us are explicitly operating in the "this is not a saas" mode. about 60 of us. tool-agnostic. claude, cursor, lovable, replit, whip, whatever. (i help build whip, full disclosure, which is how i ended up thinking about this.) weekly live co-builds. zero "what's the monetization path" pressure. if you've shipped a thing whose entire user base is your friends or your kid or yourself and you love it: https://discord.gg/5rZsC2sE

honest question for this sub: when someone here asks "what should i build first," do you push them toward market research, or toward "the silliest thing you and your four friends would actually use this week"?

reddit.com
u/ConstantContext — 11 days ago

quick buildinpublic post. running a small community for people making software as self-expression - the kind of thing made for 4 friends, not for a market. we're at 50 members. inviting more people in. weekly live co-build streams are coming, no schedule yet - figuring that out now.

context for why this exists: every builder community i'm in defaults to "but does it scale" or "what's the business model." that question is fine if you're trying to start a saas. but it's the wrong question for the chunk of us using ai to make personal-expression software. there wasn't a venue for that. so i started one.

what's worked so far:

  • tool-agnostic from day 1. members use claude, cursor, lovable, replit, bolt, whatever. we don't have a "stack."
  • intro thread asks one question: "what's the silliest non-saas thing you've shipped." filters audience instantly.
  • no roadmap, no rules doc, no founder pitch. lowers the seriousness baseline.

who joins: people who use ai the way someone else might make zines or memes - for the joke, for friends, for the thing they wished existed. not founders, not stealth-mode-builders, not "b2b saas after demo day" people. what's in it: live co-builds with peers (once we lock the schedule), a small audience that gets the work, zero pressure to monetize anything you ship.

if you've grown a community for makers (not saas builders, makers) i'd love to know what you'd do differently. and if you build this kind of stuff and want in: https://discord.gg/386JuYrA

reddit.com
u/ConstantContext — 15 days ago

in 5 years the average person ships more mini-apps per month than they currently ship instagram stories.

  1. every creative medium has gone through the same arc.
  2. video was tv studios, then youtube.
  3. photos were professional photographers, then instagram.
  4. writing was journalists, then twitter and substack.

mass participation never just expanded the old format. it unlocked new ones. tv didn't invent vlogs. magazines didn't invent stories.

software is next. mini-apps specifically. tiny weird hyper-personal things. a quiz only your friend group gets. a wheel that picks who buys lunch. an alarm that won't turn off until you do 10 pushups. tools like lovable, whip, replit are already at the early-youtube stage. anyone can describe an app and have it built in 20 minutes.

what gets unlocked isn't "saas" or "indie apps." it's the software equivalent of a meme. something made for 4 people, shared in a group chat.

crazy enough or already too obvious?

reddit.com
u/ConstantContext — 21 days ago
▲ 11 r/SomebodyMakeThis+1 crossposts

scrolled three "what should i build first" threads here this week. the answers are always the same five. find a problem, scratch your own itch, validate before you code, ship fast.

the advice is fine but it's startup-shaped. for a chunk of people in this sub (non-coders, hobbyists) the real answer isn't "find a market." it's "build the silly thing you and four friends would actually use."

most-used app i've ever made is a 5-square thing on my phone for tracking when i finish something. nobody else needs it. i use it daily.

tools like lovable, whip, replit have basically dropped the friction to zero for these audience-of-one apps. so the build skill comes from making 20 tiny things, not from picking the perfect first idea.

when someone here says "i don't know what to build," do you push them toward market-research advice, or toward "build the thing you'd use this week with your friends"? what's worked?

u/ConstantContext — 22 days ago