Native apps and practical AI
I help teams build reliable iOS and macOS products, bring AI models on device, and improve how they work with AI. You work directly with me, starting with a real task or engineering problem and a clearly defined outcome.
Custom AI workflows for your team
I start from your team’s real tasks and build workflows that fit them: agent skills that know your codebase, connections to the tools you already use, and verification loops that check every result. Hands-on sessions help your team run, evaluate, and adapt them on its own.
The replay needs JavaScript. It follows an engagement from a kickoff call through interviews, a workflow design, drafted skills and checks, a hands-on session and a team trial, to the decision to adopt.
A condensed, illustrative replay of this kind of engagement, not a recording.
What I help with
- Identify where AI can help and where it adds overhead.
- Build agent skills, reusable instructions, and automations around your codebase and real work.
- Connect workflows to the tools your team already uses.
- Design verification loops that check every result and feed findings into the next iteration.
- Run hands-on sessions so your team can run, evaluate, and adapt the workflows on its own.
What you take away
- Skills, tool connections, and verification checks made for your codebase.
- A working workflow built on one of your real tasks.
- Hands-on sessions and a handover your team can maintain.
Evaluate time spent, review effort, and quality before deciding what to adopt more widely.
Native apps, end to end
Native iOS and macOS apps in SwiftUI, UIKit and AppKit, from the first build to App Store submission, with StoreKit or RevenueCat when the app sells something. My own apps shipped this way, and at AppUnite I built two fintech apps from scratch while leading the team.
What I help with
- Building an iOS or macOS app in SwiftUI, UIKit or AppKit, from the first build to release.
- In-app purchases and subscriptions with StoreKit or RevenueCat, and product analytics.
- Modular architecture and test-driven development from the start.
- Automated builds, releases, and App Store submission with GitHub Actions and Fastlane.
What you take away
- The app in your repository, submitted for App Store review.
- An automated build and release pipeline your team can run.
- A handover covering decisions and remaining limitations.
The replay needs JavaScript. It follows one app from a typed brief through planning, parallel builders, a failed test and its fix, checks in the simulator, and your approvals, to App Store review. The app it ships is DoseWise.
A condensed, illustrative replay of this kind of engagement, not a recording.
On-device AI and audio
Bring AI and speech features into an iOS or macOS product: local model integration, on-device transcription, text-to-speech, and audio capture, from an initial technical direction to a feature your team can maintain.
At Littlebird, I built the local on-device meeting transcription pipeline for its macOS meeting assistant.
The replay needs JavaScript. It follows a feature from a brief and an API choice through parallel builders, a failed sleep and wake test and its recovery path, to a person listening on real hardware before handover.
A condensed, illustrative replay of this kind of engagement, not a recording.
What I help with
- Integrating and running local models on device.
- Transcription and text-to-speech features.
- macOS audio capture, processing, and recovery.
What you take away
- Integration with your team’s workflow.
- The agreed change and relevant verification.
- A handover covering decisions and remaining limitations.
Architecture and reliability
A persistent reliability issue, a delivery bottleneck, or an architecture decision that needs another perspective. I work with your team to understand the system, examine the evidence, and identify the changes that matter most. I can start with a focused review or take an agreed change through implementation and handover.
What I help with
- Intermittent failures and Swift concurrency problems.
- Module boundaries and difficult architecture decisions.
- Build times, release workflows, and delivery bottlenecks.
What you take away
- A concise explanation backed by evidence.
- Prioritized recommendations.
- A walkthrough with your team.
For implementation work, I also include the agreed change, relevant verification, and a handover.
The replay needs JavaScript. It follows a freeze report through triage, two hypotheses tested in parallel, a repro test that confirms one of them, your choice of fix, and a stress run and review, to a merged change.
A condensed, illustrative replay of this kind of engagement, not a recording.
How working together starts
Four steps from your first message to a handover your team can use.
-
Share the problem
The product, what is happening, and what you want to change.
-
Establish the fit
Discuss the goal, access, constraints, and useful next steps.
-
Agree the scope
Put deliverables, price, timing, and responsibilities in writing.
-
Work and hand over
Review the result together and leave the team with usable knowledge.
Questions before getting started
What kinds of problems are a good fit?
Improving how your engineering team uses AI, from context and planning to implementation and verification. I also help with local models, transcription, text-to-speech, and audio capture, as well as iOS and macOS architecture, concurrency, and reliability.
Can you work with an existing engineering team?
Yes. The scope should fit your team’s ownership, review process, and delivery constraints. The goal is to make progress together and leave the team able to maintain the result.
Should I start with a review or implementation?
If the cause or direction is unclear, a focused review is a useful starting point. For AI workflows, I suggest starting with one real task so you can evaluate the approach. If you have an agreed engineering problem and outcome, I can discuss implementation directly.
How would remote collaboration work?
I’m based in Warsaw, Poland. I’ll discuss time-zone overlap, communication, and access requirements with you before deciding whether the engagement is a fit.
How are price and timing agreed?
After I understand the problem and access requirements, I’ll put the scope, deliverables, price, and timing in writing for you to review. The areas above are starting points for that conversation.
Tell me about your project
Tell me what you’re working on, where you’re stuck, and what you want to change. I reply within two working days.
Prefer email? hello@dominikdrag.com
Sent
Thanks, .
I’ll reply to within two working days.