Services
iOS development
An iPhone or iPad app, scoped as a project and carried through to a shippable build.
iOS project consulting for a defined app: a new build, a release that is stuck, or a codebase the current team did not write. The public example is Curio, an iPhone game Jon helped develop in 2012.
Who it is for
- A firm that needs an iPhone or iPad app as a project, with a scope and a finish line.
- A team that inherited an iOS codebase and needs a senior person to get the next release out.
- A product owner who wants the person doing the work to have shipped before, and to say so without a chart position attached.
What the work includes
A defined app, not a platform
The screens, the data, and the release that matter. Native iOS. The engagement ends when that build is in a state the team can ship or maintain.
Reading the code that exists
If there is already an app, the first work is the path that is stuck: a crash, a flow, a release that will not go out. A rewrite is a separate decision.
Ship as the finish line
Build, test on device, and the submission steps the project actually needs. App Store process is part of the work when that is how the app reaches people. It is not an ongoing growth retainer.
A handoff the next developer can use
The project leaves notes and a build the in-house person can open. It does not leave a dependency on a studio.
How an engagement starts
An iOS engagement starts with the app and the date it has to be in someone’s hands. If the honest scope is a small release on an existing codebase, that is the project. If the honest answer is that this practice is the wrong fit, that gets said early.
If iOS development is the project, send a paragraph.
Name the system, what is stuck, and any date that already exists. That is enough to tell whether this practice is the right one.