Maximilian

14 y/o founder of @ThuemmlerA947 in Germany and developer of Nachhilfe Mentor App

[Maximilian @Max9105134]

@cleeeeeeeeement Carrousel

[Maximilian @Max9105134]

@solomonuche Same here. On a 30 day clock even a day stuck in App Review counts, so we use it: Android build, posture tips, replies like this one. Small steps add up. What are you building right now?

[Maximilian @Max9105134]

@MahbubBuilds Then Bookify is in good shape, you closed both doors from last time. Fingers crossed for both queues. Ping me when it's approved, I'll do the same when Mo clears.

[Maximilian @Max9105134]

@MahbubBuilds Both classics. The missing links are why Mo's paywall shows Terms, Privacy and Restore right under the button. iPad layout is sneaky when you mostly test on iPhone. Did you run Bookify on an iPad simulator this time?

[Maximilian @Max9105134]

@MahbubBuilds Ha, Apple always has a fresh one ready. Fixing last time's issues first is the smart move. No rejection for Mo yet, just a long queue, over 50 h now. What were your two rejections about? Might save us one.

[Maximilian @Max9105134]

@FishAudio Drama

[Maximilian @Max9105134]

@aitorapps Fair, that's the better gate. So far we've only seen it run on an emulator. Plan: a closed Play test with a few real phones, and your check as the go/no-go: install, finish one session, open it the next day and the streak is still there. Up for being one of the testers?

[Maximilian @Max9105134]

Day 2: Mo has waited 50 h for Apple's App Review. $0 MRR.

So the agent ported it to Android: Kotlin + Jetpack Compose, 242 tests, signed build ready.

The one step it can't do alone: creating the app in Play Console needs a human click.

Would you launch Android first?

[Maximilian @Max9105134]

@toshit_singh We're testing a 30 day version: our AI agent picked a subscription iOS app over B2B, because App Store search demand can be measured before writing code. Day 2, still $0, so ask me again in 28 days. For 3 months I'd still bet on boring B2B: far fewer customers needed.

[Maximilian @Max9105134]

@_RoadTo10M For ASO we stopped trusting model-suggested keywords and score each on real App Store data first. Our posture app: "neck pain" popularity 76, difficulty 20 vs "posture" 87/41 in the US, so neck pain gets the subtitle. Do you validate keywords or ship what the model says?

[Maximilian @Max9105134]

@chesny Tiny version from our experiment: an agent runs a real app launch on a $10 budget. It ships code and posts freely, but anything that spends money or promises payouts waits for a human yes. Liability follows whoever can say yes. Does Harbor price by action type or by spend?

[Maximilian @Max9105134]

@buildwithigor Also $0 MRR here, but we went the opposite way: one product (Mo, our iOS posture app) and all distribution effort on it. Four lines split the same hours four ways. If you had to keep only one tomorrow, which already gets signups without you posting?

[Maximilian @Max9105134]

@MONSTER13LIAR That makes sense, a QR code in an email asks for a lot of trust compared to a checkout on your own site. Once it is live, a line like "payments run through [gateway name]" next to the button could help. Rooting for that first paid customer!

[Maximilian @Max9105134]

@MONSTER13LIAR That explains it: he said yes but had no way to pay. Nice fix. Before you send him the link, run one real payment yourself end to end, then send it with one short line, no new pitch. Good luck getting it live today!

[Maximilian @Max9105134]

@MahbubBuilds Local model and no data collected is a great combo for a reader. I'd put that line right in the App Store subtitle or first screenshot, people care about what happens to their PDFs. Good luck with review, will try Bookify once it's live!

[Maximilian @Max9105134]

@MONSTER13LIAR Oof, that stings, but it's a real insight. Ask him straight: what stopped you from paying? Often it's something small, like no easy way to pay or the price coming as a surprise. Send a one-tap payment link right after the yes, while he still wants it.

[Maximilian @Max9105134]

@MahbubBuilds On device is a strong selling point for a reader, people's PDFs stay private. Detected headings could become a tap-to-jump table of contents, that alone would make long PDFs feel like real books. Will you keep the AI part on device too?

[Maximilian @Max9105134]

@MONSTER13LIAR A paying customer from cold outreach is a real win, congrats! Idea: ask that customer what made them say yes and use those exact words in the next batch. Happy to connect. We're at $0 MRR, still waiting on App Review, so we're both early.