Medication Tracker
A medication app for patients and caregivers. Schedules, reminders and refill tracking, built in Swift.
Ship It: take your AI-built app to production and the App Store
You have a prototype that works. We get it ready for real users and real money, then into the App Store and Play Store. It starts with a 3-day audit and ends with your app live, on accounts you own.
Sound familiar?
Works in preview, breaks in production
Real users, real data and real traffic find what the preview never did.
What the sprint fixesUsers can see each other’s data
The most common problem we find in AI-built apps, and the easiest to miss.
The security auditKeys or secrets in the app
If a secret key ships in the browser or the app, assume someone already has it.
The security auditRejected by Apple under guideline 4.2
Apple says the app is just a website. The fix is native features, not a resubmission.
App Store rejection helpFix one thing, break another
After hundreds of prompts, nobody knows why the code works. The audit says whether to fix or rebuild.
What the audit checks
This is for you if
- You built your app with Lovable, Bolt, Cursor, Claude Code, Replit, v0 or something similar.
- It works for you, but you're not sure it's safe for strangers.
- You want it in the App Store or Play Store, or Apple has already said no.
- You're about to take payments, or you already are.
- The builder platform holds your database and domain, and you want them in your own name.
- A developer or agency built it and you can't get changes made. See taking over from another team.
- It is a web app, such as a SaaS, and you don't need the app stores at all. See web apps.
This is not for you if
- You don't have anything built yet. Start with our MVP page instead.
- You want someone to keep adding features with no review. We can do that later, but not before the basics are safe.
The audit: 3 days, $490
A senior engineer reviews your app from the outside, like an attacker or a store reviewer would, and from the inside, by reading the code and the database rules.
What we check
| Area | What we look at |
|---|---|
| Accounts and sessions | Sign-up, login, logout, password reset. Does logging out really end the session? |
| Data access | We log in as one user and try to read and change another user’s data. We check every table’s access rules (for Supabase, the RLS policies). |
| Secrets | Which keys are in the frontend, in the repo, or in old commits. Which ones need rotating. |
| Payments | Stripe or other provider setup, webhook signature checks, what happens when a payment fails or is refunded. |
| Hosting and ownership | Who owns the database, domain, deploys and email sending. What it takes to move them into your name. |
| Reliability | Backups (and whether one can be restored), error monitoring, a basic load check. |
| Store readiness | What Apple and Google are likely to reject: minimum functionality (4.2), account deletion and privacy (5.1.1), login options (4.8), in-app purchase rules (3.1.1), metadata (2.3.7). |
| Code health | How hard the code will be to change. Whether to fix or rebuild. |
What you get
- A written report, ranked by risk, in plain English with the technical detail underneath.
- A 45-minute call to walk through it.
- A fixed price and timeline for the sprint. Or a clear recommendation to rebuild, with reasons.
- The report is yours to keep, whether or not you work with us.
What we need from you
- Read-only access to the code (GitHub, or an export from your builder).
- A test account on the app, or two if it has user roles.
- 20 minutes on a call to tell us what the app does and who it is for.
The audit fee is credited in full against the sprint.
The sprint: 2 to 3 weeks, from $3,900
The price is fixed after the audit and depends on what the audit finds. Typical sprints are between $3,900 and $6,900.
No mobile app needed? The same audit covers a web app. For a web app, the sprint covers sign-in, payments, hosting, speed and security instead of store submission, and the fixed price comes with the audit report.
What a sprint usually includes (the exact list comes from your audit):
Security
- Secrets moved to the server side and rotated.
- Database access rules written and tested as the wrong user.
- Server-side checks on every action that changes data.
- Payment webhooks verified.
Ownership and hosting
- Your app moved to accounts in your name: database (for example your own Supabase project), hosting, domain and email.
- For Lovable apps, a move off Lovable Cloud when needed.
Reliability
- A staging copy of the app for testing changes.
- Daily backups, with one test restore.
- Error monitoring with alerts.
Mobile apps
- iOS and Android apps built from your code, usually with Capacitor. When the app needs more than a wrapper can give, we write the native parts in Swift and Kotlin.
- Native features that make it a real app and not a wrapped website: push notifications, native navigation, offline states, Sign in with Apple, camera or biometrics where they fit.
- In-app purchases or subscriptions through Apple and Google where the rules require them, usually with RevenueCat.
Store submission
- App Store and Play Store listings, screenshots guidance, privacy answers and review notes.
- Test builds through TestFlight and Play internal testing.
- For new Google Play personal accounts, the 12-tester, 14-day closed test, planned from the first week.
After launch
- 30 days of support for bugs in the work we did.
How we work during the sprint
- A short written update each working day.
- New test builds every few days, so you see progress on your own phone.
- One shared channel. No account managers between you and the engineers.
Taking over from another team
If a developer or agency built your app and changes have stopped, or nobody answers, we start the same way as for any app: an audit, so you know what you have before you commit to more. Choose "A developer or agency built it" when you book.
First, make sure the code and the accounts are in your name: the repository, domain, hosting, database, Stripe, and the App Store and Play Store accounts. Use our checklist to get your app back. It works whether or not you hire us.
Store review: about 1 to 2 weeks
Apple and Google set the review time, not us. Most reviews take a few days. A first submission with questions can take longer. We answer reviewer messages for you and, if the rejection is about our scope, fix it and resubmit at no extra cost.
Care plan: optional, from $750 a month
What it covers
- Updates for new iOS and Android versions and new store rules.
- Security patches and dependency updates.
- Error monitoring and a monthly health note.
- A set number of hours each month for small changes.
- Store listing updates and resubmissions.
Terms: month to month. Cancel any month. If you leave, we hand over everything and you keep running without us.
Pricing summary
| Audit | Sprint | Care | |
|---|---|---|---|
| Price | $490 | from $3,900, fixed after audit | from $750 a month |
| Time | 3 working days | 2 to 3 weeks + store review | monthly |
| You get | Written report, call, fixed quote | Fixes, your own accounts, iOS and Android apps, store submission, 30 days support | Updates, patches, monitoring, small changes |
| Commitment | None beyond the audit | Fixed scope from the audit | Cancel any month |
Built with Replit or v0?
We work on these too.
- Replit can now build Expo apps and send iOS builds to App Store Connect. That still leaves the review itself, Google Play, and the security work.
- v0 builds Next.js frontends, often with little or no backend behind them. The audit tells you how much is missing before you commit.
Your accounts, your code.
Accounts stay in your name
Your GitHub, hosting, Supabase or Firebase, Stripe, and App Store and Play Store accounts stay yours. We are invited as collaborators.
No passwords or admin keys
You never send us passwords or admin keys. You add us to each account, and you can remove us at any time.
You keep the code
The code lives in your repository, not ours. If you stop working with us, there is nothing to hand back.
NDA first, if you want one
We are happy to sign your NDA before the audit.
Apps we have built and shipped
More case studies
Veripoint
An inspection app for equipment teams. Works offline in the field, then syncs photos, video and reports.
Bricks R Us
A fundraising platform moved from desktop to mobile, with payments, orders and campaign tools for US organisations.
Recruit Genie
An HR platform with identity checks, role-based access and training schedules, for a UK client.
What clients say
“We hired them to make updates to an already functioning app, and they exceeded expectations. The work was completed quickly, professionally, and with a strong attention to detail.”
Amanda P.Product Owner, Consumer App Brand “We brought iMobile Designs in to improve and refine an existing web application, and they handled everything efficiently. Communication was clear, turnaround was fast, and the final implementation was exactly what we needed.”
Sarah T.Product Manager, SaaS Company “Immersive Mobile Designs has strong native mobile development expertise. Their team understood our requirements immediately, communicated well, and delivered a polished product that matched our expectations.”
Chris W.Founder, App-Based Business “Immersive Mobile Designs helped us move quickly on our MVP and brought structure to a project that was still evolving. They delivered solid work, stayed flexible when requirements changed, and gave us confidence as we moved toward launch.”
Emily K.Founder, HealthTech App
Questions founders ask
Do I need to know how to code?
No. The report is in plain English, and we explain every decision before we make it.
What if the audit finds more than expected?
Then the sprint price says so before you agree to anything. You can also choose to fix only the critical items first and leave the rest for later.
Will my app still work in the builder after you change it?
Usually yes for Lovable and Bolt, if we agree on that up front. Some fixes, like moving to your own database, mean the builder's preview needs to point at the new setup. We tell you in the audit which changes affect your workflow.
Can I keep building with AI after you're done?
Yes. We leave notes on how the app is put together and which rules to keep, so your next prompts don't undo the security work. The care plan can include a review of changes before they go live.
Capacitor or native?
For most AI-built apps, Capacitor with real native features gets through review and costs far less. If your app needs heavy native work, like background location, complex camera use or offline sync, we write those parts natively. The audit says which one fits.
Do I need a Mac or my own developer accounts?
You don't need a Mac. You need your own Apple developer account (US$99 a year) and Google Play developer account (US$25 one time), so the apps are in your name. We help you set them up.
What happens if Apple rejects the app?
We read the rejection, fix what is in our scope, reply to the reviewer and resubmit.
My app is a web app (for example a SaaS). Do I need the App Store part?
No. The same audit covers a web app with no app store involved. For a web app, the sprint covers sign-in, payments, hosting, speed and security instead of store submission. You get a fixed price for it with the audit report.
Taking over from another team: what we need from you, and what you keep
We start with an audit, the same as for any app, so you know what you have before you commit to more. We need access to the code (the repository, or a full export), and to the hosting, database, domain, payment and store accounts, or your help getting them back into your name. You keep the code and every account: we are added as collaborators and work inside your accounts. If the previous team still controls some of them, start with our checklist for getting your app back.
Send us the link to your app.
We'll reply within one working day to confirm the audit and the start date.