iOS app development
You need an iPhone app, and the first decision is how to build it, because that sets the budget. We reach the App Store in two ways: React Native, as on a UK garage-booking product, and web apps wrapped as native builds, as on a Belgian wearable QR product delivered in three months. We have no Swift-only app in our published work, and this page explains what that means for your project.
Three products, and how each one was built.
Garage booking, in React Native
Car owners book a slot, pay, receive invoices and get reminders on their iPhone, with the same product on Android and a Next.js web app, all on one Laravel API.
Wearable QR owner app, wrapped
T-shirt owners log in, upload media, write their message, preview and publish what their shirt's unique QR code shows. Scanning itself needs no app, because a fast mobile page handles it.
Geo-survey lookup, wrapped
In 2015, a Texas client's customers used a wrapped web app on iOS and Android to look up wells and survey results in the field, through a keyed Laravel API he resold.
From Apple's developer news and App Review guidelines. Check them again before you submit, as they change.
Build tools
Since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK or later. An app that has not been rebuilt recently may need work before its next update can go out.
Minimum target
Since 9 September 2026, iOS and iPadOS uploads must target iOS 13 or later, so very old deployment targets have to be raised, which can also affect your dependencies.
Repackaged websites
App Review guideline 4.2 asks for features, content and interface that lift an app beyond a repackaged website. A wrapped app therefore needs a real reason to exist: login, publishing and app-like flows, not just your site in a frame.
Parts of the iOS process run on Apple's timetable, so they go into the plan early.
We list what really needs the phone, such as notifications, camera or offline use. That list decides between React Native, a wrapper and a native specialist.
The Apple Developer account, signing and TestFlight access are arranged early and kept in your company's name, because enrolment can take time you did not plan for.
You install test builds through TestFlight and review them in demos, weekly on most projects, so problems with real devices surface well before submission.
We prepare the build and answer questions from App Review. Rejections are normal enough that time for them belongs in the launch plan.
Time and budget follow from the route you choose.
The wearable QR product took three months including the backend and scan pages. The garage-booking product took about a year because it was a full SaaS. Most iOS apps also need Android, so we usually scope both together; see React Native development.
Work is quoted as a project, or charged hourly from $20/h in USD, invoiced in USD, GBP, EUR or INR. We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment.
Most of our work is delivered under NDA, so many projects cannot be named.
UK garage-booking SaaS: car owners book, pay, receive invoices and reminders from their phone; garages manage services and slots. Laravel API, Next.js web app, React Native iOS/Android apps. About one year.
Backend, scan pages and iOS/Android apps behind a t-shirt with a unique QR code its owner controls — text, photo or video, changeable any time, scannable with no app. Laravel. Delivered to both app stores in three months for a Belgian fashion brand.
Texas oil-well location and geo-survey data structured into a database, served through a keyed Laravel API and a mobile app the client resold to his own customers. 2015.
Starting with the one we would ask in your position.
Tell us what it must do on the device and whether you also need Android. We will recommend a route, including when that route is another team.
We reply within one business day (IST).