End-to-end delivery
Come with an idea or a finished design — if you need one, I bring a designer I trust. Then architecture, implementation, App Store submission and the support that follows the launch.
Available for freelance & contract work
From idea
to App Store.
Thirty-plus iOS apps shipped in Swift and SwiftUI — I take a product from the first sketch through App Store review to the subscriptions that pay for it.
or write to [email protected]
- 30+
- Apps shipped to the App Store
- 5+
- Years writing Swift every day
- 100%
- Native Swift, never a wrapper
What I do
What I can build for you
Four shapes the work usually takes. Most projects are the first one.
Monetization & retention
Subscriptions that convert. RevenueCat and Superwall wired properly, paywalls tested against each other, trials and win-backs tuned instead of guessed.
Rescue & refactor
Inherited a codebase that fights back? I untangle legacy UIKit and Objective‑C, cut crash rates and make the build reliable again — without stopping the roadmap.
Inside your team
Contract work embedded with your engineers, as an individual contributor or leading the iOS side: code review, architecture calls, mentoring and release ownership.
About
Thirty-plus apps in. One platform, done properly.
- 30+
- Apps released
- 5+
- Years in Swift
- Lead
- and IC roles
- E2E
- Idea to App Store
- Written scope and fixed milestones
- Weekly TestFlight builds
- You own the code and every account
- Submission and review handled for you
I'm Dmytro Grytsenko, a senior iOS engineer working out of Ukraine. Over five years I've shipped more than thirty apps to the App Store — for agencies, for product teams, and a few under my own name. Different categories, different sizes, the same platform every time.
I work end to end. That means an empty Xcode project on Monday and a live listing at the end: architecture, SwiftUI screens, the server integration, App Store Connect metadata, the privacy questionnaire, the rejection that comes back on a Friday and the point release that answers it. Nobody has to translate between a designer, a backend and a "mobile guy" — that's one conversation, with me.
I care about the money side. A beautiful app that nobody subscribes to is a hobby. I've built subscription flows on RevenueCat and Superwall — paywalls tested against each other rather than argued about, trials and intro offers priced deliberately, win-back and churn recovery wired in from the first release instead of bolted on after the numbers disappoint.
And about knowing whether it worked. Mixpanel, Amplitude, AppsFlyer and Adjust for attribution and funnels, Usercentrics for consent so the analytics stay GDPR-clean. Instrumented properly, before launch, so the first cohort actually tells you something.
I've spent as much time inside teams as alone: as an individual contributor in product companies and leading the iOS side — code review, architecture calls, onboarding juniors, owning the release train. Whether you need someone to build the whole thing or to slot into a standup on Monday, both are familiar ground.
Underneath all of it: native Swift, first-party frameworks, as few dependencies as the job allows. An app you can still build five years from now.
Tools
What I work with
First-party frameworks wherever Apple ships one, and a short list of third-party tools that have earned their place over thirty-odd releases.
Language & UI
SwiftUI first, UIKit where it still wins
- Swift
- SwiftUI
- UIKit
- Swift Concurrency
- Combine
- Swift Charts
Data & sync
Local-first, synced when it earns it
- SwiftData
- CloudKit
- Core Data
- Supabase
- Firebase
- Realm
Monetization
Where an app makes or loses its money
- RevenueCat
- Superwall
- StoreKit 2
- Paywall A/B testing
- Trials & offers
- Churn recovery
Analytics & attribution
Numbers you can actually trust
- Mixpanel
- Amplitude
- AppsFlyer
- Adjust
- Firebase Analytics
- Usercentrics (CMP)
Engagement
Reasons to open the app again
- Push notifications
- Live Activities
- WidgetKit
- App Intents
- Deep linking
- App Clips
Ship & operate
Release day is not the finish line
- App Store Connect
- TestFlight
- Xcode Cloud
- Fastlane
- Swift Testing
- Instruments
Selected work
Apps under my own name
Everything you own and every date that comes with it — warranties, renewals, services — with a reminder before one slips.
- SwiftUI
- SwiftData
- CloudKit
- StoreKit 2
How it works
How we'll work together
- 01
Scope
We agree on what the first release actually needs — and what can wait. You get a written plan with milestones before any code is written.
- 02
Build
Weekly TestFlight builds, so you are never guessing about progress. Architecture decisions are documented, not buried in commits.
- 03
Ship
Submission, review responses, privacy declarations, release notes. I handle the App Store Connect paperwork that sinks first-time launches.
- 04
Grow
Paywalls measured against each other, funnels instrumented, crashes watched. Release day is where the interesting work starts.
Contact
Have an idea?
Let's ship it.
A paragraph is enough: what the app does, who it's for, and roughly when you need it live. If it's a rescue job, tell me what's broken.
- 1 A reply within two business days From me, not an autoresponder.
- 2 An honest read on scope Including when the answer is "this is smaller than you think".
- 3 A written plan before any code Milestones, price and what the first release contains.