App Store Launch
Apps I’ve Shipped
How Beles and EBT Finder reached the App Store, and the release checks those launches shaped.
Cases
From a Lovable project to the App Store
Two apps of my own, both live.
Beles
Built in Lovable. First iOS build to App Store release in ten days.
Sign in with Apple · Report and block · iPhone-only
The release lessons now inform my pre-submission checks: sign-in on a real iPhone, reporting and blocking, and screenshots that match the supported devices.
Release history and lessons
Released September 20, 2026, with availability in 175 countries. This describes distribution coverage, not adoption.
Sign-in broke inside the app, not on the web
The first build called a web address that redirects. Browsers follow that quietly; the native app didn't, so sign-in failed. The fix was pointing the app at the final production host, shipped in build 2.
A missing iPad screenshot can block submission
App Store Connect won't submit a universal app without 13-inch iPad screenshots, and Beles had no iPad layout. Shipping it as iPhone-only was the honest fix, not stretched screenshots.
Dating apps live under Apple's user-generated content rules
Apple expects reporting, blocking and moderation in any app where people post content. I built an admin panel for reports, member suspension and events before submitting.
Release closes the version
Once 1.0 went live, App Store Connect rejected every further 1.0 build. Updates needed a new version number, so the next release went out as 1.0.1.
Sign in with Apple needs native wiring
The web flow doesn't carry over by itself; the iOS project has to register the native plugin. I caught it after launch and fixed it in the 1.0.1 update. On client apps I test it on a real device before submitting.
EBT Finder
Rejected by App Review, approved without a new build. Version 1.0.4 is live.
Reviewer couldn't sign up · 264,000+ locations
The reviewer could not create an account. I repaired the backend trigger, tested signup on a physical device against the same build, and explained the cause and fix to App Review.
What changed in my release checks
Backend signup checks and an audit at phone dimensions now come before submission: safe areas, tap targets, navigation and inline refresh.
Apple rejected the build for a bug that wasn't in the build
App Review reported that account creation failed. The cause was a database trigger referencing a column I had removed: every new sign-up returned a 500, which the app surfaced as the error the reviewer saw. Fixed the trigger server-side, reproduced the sign-up on a physical device against the same build, and replied to the Resolution Center with the root cause and evidence. No new binary was needed.
Thirteen TestFlight builds to a clean release
The 1.0.2 redesign found its native-UX bugs on the phone, after upload: a sticky header that never stuck, dead-tap card images, a login screen with a manufactured scroll region, GPS refresh that navigated away instead of updating inline. Turned every bug class into a written rule and a pre-archive audit at phone dimensions (safe areas owned by one component each, 44pt targets, one tap target per card, inline refresh with skeletons). Later releases audit before they archive.
Your app could be next.
Send the link or the rejection. Get the real cause and a fixed price.
Free diagnosis
Get a free app fit assessment.
Send the link and where it is stuck. Within one business day, I will assess the fit, recommend a package and outline next steps, or explain what else I need to review. The detailed $250 Readiness Check is separate; submitting this form does not book paid work.
- No Apple ID password, ever
- App Manager access to one app, revoked at handover
- Your code and backend stay where they are
The App Store launch service is provided by Appfinity Labs LLC, Los Angeles, California. Not affiliated with or endorsed by Apple or Lovable. App Store is a service mark of Apple Inc.