iOS services
iPhone apps built the way Apple expects.
iOS users notice when an app was clearly built for Android first. We write Swift, use the platform properly, and get through App Store review without a fortnight of back-and-forth.
Doffo's iPhone app is ours, built in Swift and maintained since launch.
Overview
iOS, the way we do it
Apple has strong opinions about how an app should behave, and users have absorbed them without being able to name them. Gestures that do not feel right, a navigation stack that fights the system, text that ignores the size the user chose. None of it appears in a bug report; it appears in the rating.
We build in Swift against the platform rather than around it, test on real devices across OS versions, and handle App Store Connect ourselves: the privacy manifest, the metadata, the reviewer questions. Most of what we submit clears on the first attempt.
What's included
What you actually get
- Written in Swift, using the platform rather than working around it
- Face ID, Apple Pay, push and other native frameworks where they serve the product
- Tested on real devices across OS versions, not only in a simulator
- App Store submission handled, including privacy declarations and review
- Right-to-left Arabic and Dynamic Type supported properly
How we work
Five steps, no surprises
- 01
We talk
A call or a WhatsApp thread. You tell us what is not working; we tell you honestly whether we are the right people.
- 02
We scope it
A written plan with what you get, what it costs and how long it takes. Fixed, so there are no surprises later.
- 03
We build it
You see it as it goes, not at the end. Changes are cheap while it is still being built.
- 04
We put it live
On infrastructure we set up and secure, tested before the launch date.
- 05
We keep it running
Updates, monitoring and someone who answers. Most clients stay on a monthly agreement.
Questions
About ios
How long does App Store review take?
Usually a day or two when the submission is right. Our familiarity with the process is the reason most of what we send clears first time rather than after two weeks of correspondence.
Can you take over an existing iOS app?
Yes. We read the codebase first and report what we find, including whether it can be built on or needs restructuring before new features go in.
Which iOS versions do you support?
Normally the current version and the two before it, which covers almost every device in use. We will look at your own analytics and set the floor from that rather than from a rule of thumb.
Also
Related work
- Quality AssuranceFind it before your customers do.
- UX DesignWork out what it should do before anyone builds it.
- UI DesignScreens people can use without being trained.
- Design SystemsOne set of rules, so the tenth screen looks like the first.
- Mobile ApplicationsApps people keep on the first screen.
- AndroidAndroid apps that work on the phones people actually own.
- FlutterFlutter, when one team has to cover both stores.
- AIAI that does one job, properly.
- Machine LearningModels that earn their place in the business.
- Data ScienceAnswers from the data you already have.
- LLMsLanguage models, kept on a short leash.
- Generative AIGeneration with a human still holding the pen.
- PythonPython, for the work that has to be read as well as run.
- Back-EndWhere an order becomes an order.
- DatabaseThe part of your system that is hardest to fix later.
- Node.jsNode.js, for the systems that have to answer quickly.
- GoGo, where it has to be fast and stay simple.
- .NET.NET, for the systems a business runs on.
- JavaJava, for systems measured in decades.
- Front-EndThe half of your product people actually see.
- Web DevelopmentCompany sites, customer portals, and web systems that hold up.
- ReactReact, built so the next team can still work on it.
- AngularAngular, for systems that have to last.
Tell us what you have in mind.
An engineer reads your message and replies to you directly.
Talk to us