iPhone and iPad, from one codebase
We build iOS in React Native, so the same project ships to Android too. iPad is handled by the same build rather than quoted as a second app — it’s a layout question, not a separate product.
What we build for iOS
Content apps
Your site as an app — articles, media, search, offline reading and push notifications when you publish.
Tool and calculator apps
Interactive tools that work offline, sharing logic with the web version instead of reimplementing it.
Business and internal apps
Apps for staff rather than customers — often where the real return is, and where review is simpler.
Universal iPhone and iPad
One binary, laid out properly for both. Split views and larger layouts on iPad rather than a stretched phone screen.
App Store submission
Certificates, provisioning, builds, listing, privacy nutrition labels, and getting through review.
Taking over an existing app
A stalled app or a departed developer. We audit and say honestly whether to continue it or restart.
App Store review, realistically
Apple’s review is stricter than Google’s and rejects for reasons that have nothing to do with whether your code works:
- Minimum functionality. An app that only wraps a website gets rejected. It has to do something a browser doesn’t.
- In-app purchase rules. Selling digital goods usually means Apple’s payment system and its commission. Physical goods and services don’t.
- Privacy labels and tracking permission. Declared accurately, or it comes back.
- Sign in with Apple. Required if you offer other third-party sign-in options.
We design around these from the start rather than discovering them at submission.
Before you commit
- Apps need continuous maintenance. iOS releases force rebuilds annually whether your app changed or not.
- The developer account is yours and carries an annual fee.
- Review takes time and can take several rounds. Don’t plan a launch date that assumes first-pass approval.
- You may not need an app. If the goal is a good phone experience, a fast responsive site often beats one nobody installs.
Common questions
Is iPad a separate project?
No. It’s the same build with layouts that use the larger screen properly. Anyone quoting iPhone and iPad as two apps is charging you twice for one codebase.
Why React Native rather than native Swift?
Because you get Android from the same work. Native Swift is the right call for graphics-heavy apps or deep platform-hardware integration — we’ll say so rather than take work we’d be learning on your budget.
Do we need a Mac to build it?
We handle builds and submission. You need an Apple Developer account in your own name, and we’ll walk you through setting it up.
What if Apple rejects it?
We handle the response and resubmission as part of the project. Most rejections are policy details rather than fundamental problems.
Tell us what the app is for
Who uses it and what they do with it. We’ll tell you whether it’ll clear review, and whether you need an app at all.