iOS development

Writing the app is the easy part

Native iOS in Swift and SwiftUI, built through the whole chain from first screen to the update you ship eight months after launch.

Plenty of people can build you an iOS app. Considerably fewer can get it through App Store review without three rejections, keep it compliant as Apple changes the rules, and support it once real people are using it and filing complaints.

The code is maybe a fifth of the work. The rest is the machine around it, and it is the part that gets quoted at zero and then costs the most.


What is included

The actual scope of work

Native Swift and SwiftUI

A real iOS app, not a website in a shell. It behaves the way the platform expects, which is what users notice without being able to name it.

App Store review

Guideline compliance checked before submission rather than discovered in a rejection notice two weeks before your launch date.

Privacy nutrition labels

Accurate ones, matched to what the app actually collects. Getting these wrong is now a removal risk, not a paperwork issue.

A privacy policy at a live URL

Apple requires one and it has to stay reachable for the life of the listing. Hosted here, on infrastructure that does not disappear.

Support documentation

A real docs area for the app, hosted, searchable and updated with each release, so support requests get answered before they are sent.

App Store Optimization

The listing is a search result. Title, subtitle, keyword field, screenshots and description treated accordingly.

Analytics and crash reporting

Wired in before launch so the first crash report arrives with enough context to fix it.

An update cadence

Apps that stop shipping updates lose ranking and start failing on new iOS versions. Planned from the start.

Worth knowing

How app projects are scoped

App work starts with a written scope of exactly what version one does and, more importantly, what it does not. Most app projects that go badly do so because version one quietly grew into version three while the budget stayed the same.

Web infrastructure that the app needs, including the marketing page, the privacy policy and the support docs, is part of the same engagement rather than an afterthought once the app is already in review.

Questions

Asked often enough

Do you build for Android too?

The focus is iOS. If a project genuinely needs both from day one, I will say so early rather than take it on and stretch.

Who owns the code?

You do, along with the App Store listing and every account attached to it. Everything is set up in your name from the start.

What does it cost to keep an app running?

The Apple Developer Program is an annual fee, plus whatever backend the app needs. Beyond that, budget for periodic updates. An app is not a thing you build once.

Related

Usually run alongside this

Further reading

Written on this specifically

Start here

Tell me what you are trying to fix

Send over the site you have now, or the one you wish you had. I will tell you honestly whether I am the right person for it.

info@palmprojects.com