About the service
I am an Objective-C developer and work in the part of the Apple world that most people avoid: mature applications written years ago and still making money. If you have a project with manual memory hints, a tangle of categories and deprecated APIs, I know how to read it, understand why it's structured that way, and bring it under control without the risky rewrite from scratch. Through years of work on large Objective-C projects for iOS and macOS, I know well where the fragile places usually hide and how to touch them safely.
My daily work is repair and modernization, not reinvention from a blank slate. I catch crashes from symbolicated reports and in Instruments, eliminate retain cycles and threading bugs, replace APIs that Apple deprecated, and rebuild old projects on current Xcode and SDK versions. When you're ready to move to Swift, I do it gradually: setting up a clean compatibility bridge, annotating Objective-C classes with proper nullability and generics annotations, migrating module by module so the app doesn't stop shipping for a day. I also take on thankless but critical work: keeping the app in the store, updating it for new OS versions, and restoring builds broken by certificate, profile, or dependency changes.
If your Objective-C app seems frozen because nobody wants to touch it, that's exactly my situation. Describe the symptoms and give me repository access, and I'll start with a short assessment of the code's state before proposing concrete steps with minimal risk.
— Fixing crashes, memory leaks and retain cycles in Objective-C
— Modernizing legacy iOS and macOS codebases
— Objective-C and Swift compatibility, gradual migration
— Updating deprecated APIs and restoring Xcode builds
— App Store support, releases and updates for OS versions
— Debugging through Instruments and symbolicated crash logs
My daily work is repair and modernization, not reinvention from a blank slate. I catch crashes from symbolicated reports and in Instruments, eliminate retain cycles and threading bugs, replace APIs that Apple deprecated, and rebuild old projects on current Xcode and SDK versions. When you're ready to move to Swift, I do it gradually: setting up a clean compatibility bridge, annotating Objective-C classes with proper nullability and generics annotations, migrating module by module so the app doesn't stop shipping for a day. I also take on thankless but critical work: keeping the app in the store, updating it for new OS versions, and restoring builds broken by certificate, profile, or dependency changes.
If your Objective-C app seems frozen because nobody wants to touch it, that's exactly my situation. Describe the symptoms and give me repository access, and I'll start with a short assessment of the code's state before proposing concrete steps with minimal risk.
— Fixing crashes, memory leaks and retain cycles in Objective-C
— Modernizing legacy iOS and macOS codebases
— Objective-C and Swift compatibility, gradual migration
— Updating deprecated APIs and restoring Xcode builds
— App Store support, releases and updates for OS versions
— Debugging through Instruments and symbolicated crash logs
