GBCORP BLOG · IT SERVICES
Custom iOS App: Built for iPhone Without Building Twice
A custom iOS app should feel like an iPhone app and cost like one app, not two. GBCORP builds it from one codebase that ships iOS and Android from the same release, and passes App Store review because its own apps do.
A custom iOS app is an app built around one business’s process and shipped to the App Store under the business’s name. GBCORP builds it from a single codebase that produces iOS, Android and the web from the same release, so the iPhone app is native in feel, reaches Android customers at no second build, and updates everywhere at once. The work runs as a scoping week and fixed-price releases, with the App Store developer account, the cloud project and the code in the business’s name.
What iPhone users expect
| Expectation | What it means | Where it comes from |
|---|---|---|
| Navigation | Back gestures, tab bars, sheets that behave like the system’s | Native components |
| Sign-in | Sign in with Apple beside e-mail and phone, required when other social sign-ins exist | Engine |
| Payments | In-app purchase for digital goods; the business’s own gateway for physical goods and services | Engine |
| Notifications | Permission asked at the right moment, not at first open | Engine |
| Wallet | Passes for cards, tickets and loyalty in the phone’s wallet | Engine |
| Privacy | Tracking permission, privacy labels, account deletion in the app | Engine |
One codebase, two stores
The screens are written once and rendered with each platform’s conventions. The business logic, the backend and the console are shared. A release is tested on both platforms and submitted to both stores the same day. The cost of Android is the cost of testing it, not of building it again.
App Store review
Submissions fail for predictable reasons: a sign-in that offers a social provider without Apple’s, digital goods sold outside in-app purchase, no way to delete an account, generated content without moderation, a demo account missing for the reviewer. GBCORP’s engine handles each, and its own apps pass review on every release, which is the only guarantee that means anything.
What is custom and what is not
Sign-in, payments, notifications, wallet, consoles and store compliance come from the engine. The business’s own process, its screens, its rules and its integrations are built for it, in fixed-price releases every two weeks. The first release does the core process from start to finish; the settings screen and the second language come later.
Checklist before commissioning an iOS app
- The process the app runs, in ten lines.
- Whether it sells digital goods, physical goods or services, because the payment route differs.
- Apple developer account in the business’s name, or authority for GBCORP to open it.
- Brand assets and the app name, checked in the store.
- Whether Android and web are needed now or later.
- The number the app should move.
The numbers to expect
Scoping in one week. A first release in eight to twelve weeks at a fixed price, submitted to the App Store and, if wanted, to the Play Store the same day. Releases every two weeks. Support at a known monthly figure. Customised or more complex functionality is quoted separately before any work starts.
A worked example
A private members’ club wants an iPhone app for bookings, events and a digital membership card, and most of its members carry iPhones. GBCORP configures the booking and membership engine, adds two custom releases for the club’s reciprocal-club rule and its guest-approval flow, and ships to the App Store under the club’s name in six weeks. The membership card sits in the phone’s wallet. Six months later, the club asks for Android for staff and a few members; it is produced from the same release in a week of testing.
Apple sign-in, in-app purchase and the rules around them
If an app offers any third-party sign-in, it must offer Apple’s. If it sells digital goods, memberships to digital content or features inside the app, it must use in-app purchase and cannot link out to pay elsewhere. Physical goods and services use the business’s own gateway. The engine implements each route and hides the CTA that would break the rule on the platform where it would break it, so one release passes both stores.
Testing on real devices
Every release is tested on real iPhones across the sizes and versions in use, on slow connections, with notifications, wallet passes and payments exercised. A test build reaches the client’s phone every two weeks through the platform’s own test channel. Crashes and slow screens are measured in production after launch, and the numbers appear in the support report.
Multilingual and multi-market
The app ships in the languages the business serves, with right-to-left layouts as a setting, and the App Store listing is localised per market. Currency, tax and payment provider are configured per market, and the store listing shows the business as publisher in each.
After launch
A support plan with monitoring, patches, operating-system and App Store rule updates, hours for small changes and response times by severity. Crash-free sessions and slow screens are measured in production and reported. A quarterly review of the number the app was built to move.
Ownership terms
Code in a repository the business controls, documented with every release. Apple developer account, cloud project, domain and payment account in the business’s name. Data exportable at any time. No commission on sales, and no credentials retained after a hand-over unless a support contract requires them.
Questions we hear first
Is a shared codebase really native?
The screens use native components and conventions; users cannot tell, and neither can the review team.
Can we ship iOS only?
Yes. Android and web are produced from the same release when the business wants them.
Who owns the App Store listing?
The business: the developer account is in its name and it appears as publisher.
What about updates when Apple changes the rules?
Under the support plan, rule changes are handled in the next release, as they are for GBCORP’s own apps.
Where to start
The GBCORP Custom App Development product is the priced starting point; the GBCORP mobile app development hub sets out the method. For the other platform, read the custom Android app explained.
GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Premium Business, and EV's & Solutions.
