Available for contract work

Senior Apple platform
engineer. Available
for hire.

Ten years shipping iOS software at companies like Beats by Dre, Marshall, and HOMER Learning. Now available for select contract work — building new features, auditing AI-generated code, and getting apps across the App Store finish line.

About KC
KC Okolo
Kenechi 'KC' Okolo
Senior iOS Engineer · Founder, Canvas and the Machine
10 yrs
shipping Apple software
450k+
downloads across own apps
5
live apps in production
2015
shipping independently since
Past clients
Beats by Dre Marshall HOMER Learning Perigee
What I offer

Three ways to work together.

Whether you need a feature built from scratch, a codebase made sense of, or a release that's been stalling finally shipped — there's an engagement that fits.

🍎
01
Apple Platform Development
End-to-end feature work on iOS, macOS, and visionOS. From greenfield builds to extending existing apps, with a focus on production-quality Swift from day one.
  • SwiftUI & UIKit — modern and legacy codebases
  • WidgetKit, Live Activities, Dynamic Island
  • CoreLocation, MapKit, ARKit, AVFoundation
  • Supabase, Firebase, and custom REST backends
  • Apple Watch, App Clips, and App Extensions
Good for: startups, agencies, and product teams that need senior iOS muscle without a full-time hire
🚀
03
Release Preparation
The finish line is the hardest part. I'll get your app from "almost ready" to "live on the App Store" — handling everything that stands between you and approval.
  • App Store submission and metadata
  • Crash triage and Instruments profiling
  • TestFlight → production pipeline setup
  • Rejection response and resubmission
  • Privacy manifest, entitlements, and compliance
Good for: teams stuck at the finish line, or anyone who has hit an App Store wall they can't get past alone
The vibe code problem

You built the app.
Now what?

AI coding tools have made it possible to build a working iOS app without writing much Swift yourself. That's genuinely useful — until the app needs to actually ship.

The code that Cursor or Claude produces is often structurally unsound: deeply nested view hierarchies that SwiftUI can't optimise, missing error handling that crashes silently, memory patterns that degrade over time, and architectures that will fight you at every turn as you try to add features.

You can't always see it. The app runs, the previews look right, and then it crashes in review or on a real device. A senior engineer who uses these tools daily can read the output and tell you exactly what's fragile and what needs fixing before it costs you users or time.

💥
Crashes in App Store review
AI-generated code often misses edge cases that only surface on real devices under review conditions.
🐌
Unexplained performance issues
SwiftUI misuse, unthrottled network calls, and memory leaks that the AI didn't know to avoid.
🔒
Privacy and entitlement failures
Missing privacy manifests, incorrect capability declarations, and permission flows that Apple won't accept.
🏗️
Architecture that blocks progress
Code that works today but makes every future feature twice as hard to build as it should be.
🤷
Nobody understands what it does
AI-generated code with no clear ownership, inconsistent patterns, and no mental model behind it.
How it works

Simple process.
No surprises.

01
Brief intro call
A 20-minute conversation about your project, timeline, and what a good outcome looks like. No cost, no commitment. I'll tell you honestly if I can help and how.
02
Scoping and proposal
A clear written proposal covering scope, timeline, and rate. Fixed-price for audits and defined deliverables; day rate for ongoing development work.
03
Delivery
Regular updates, async-friendly communication, and a bias toward shipping. I work the way a senior contractor should: minimal hand-holding required.
Common questions

Before you reach out.

London-based, but most contract work is fully remote. I'm comfortable with async communication across time zones and have worked with distributed teams throughout my career.
A written report — typically a structured document covering: architecture overview, identified risks and anti-patterns, a prioritised list of issues (critical / high / medium / low), and recommended fixes with rationale. For smaller codebases this is usually a 5–10 page document; for larger ones it may run longer. Optionally, I can follow the audit with hands-on remediation work.
No — I specialise exclusively in Apple platforms: iOS, macOS, and visionOS. This focus is intentional. If your project is React Native or Flutter and you need Apple-side expertise, I can still help with the native layer, but I won't take on the full project.
Availability varies. For audit work, turnaround is usually 1–2 weeks from scoping to delivery. For ongoing development, start dates depend on current commitments. Reach out and I'll give you an honest picture of my availability.
For a code audit: access to the repository (or a representative sample) and a brief description of the app and your concerns. For development work: a description of what you need built, any existing codebase context, and your rough timeline. A short email is enough to get started.
Get in touch

Let's talk about
your project.

Tell me what you're building, what's blocking you, or just send a link to your repository. I'll respond within one business day.

Send a message →