Apps
Native iOS apps for small, sharp ideas: Swift and SwiftUI, from the first TestFlight build to the App Store.
Need a web app or an internal tool? That’s custom software
- Typical stack
- Swift, SwiftUI, Firebase
- Timeline
- A testable build in roughly 6–12 weeks
You get
I build native iOS apps for focused, single-purpose ideas: the kind that live on your phone, talk to your watch or your health data, and do one thing genuinely well. Swift and the real platform APIs, not a cross-platform wrapper. For founders and small teams who want an app that feels like it belongs on iOS, from the first TestFlight build to the App Store listing.
- Native Swift
I build directly on the platform with Swift and SwiftUI, so the app feels right on iOS, not like a web view in a native shell.
- HealthKit & device APIs
I wire up HealthKit, Garmin sync, and other device and third-party APIs so the app reads the data it actually depends on.
- Firebase backend & auth
Sign-in, sync, and storage on a Firebase backend, so the app has somewhere to keep state and log people in.
- TestFlight to App Store
You test real builds on your own phone over TestFlight while we iterate, and I handle the App Store submission and review at the end.
- Honest about scope
I keep the first version small and sharp on purpose: one core job done well beats a wishlist that never ships.
- One pair of hands
You work with me from the first sketch to the live listing. No handoffs, no account managers in between.
You get a native iOS app in your hands on TestFlight in roughly six to twelve weeks, then a clean App Store launch: a focused first version that does its core job well, with one person who knows every line of it and stays available afterwards.
Who’s behind Blik
Jan Štok
Blik is a studio of one: I scope, design and build every project myself, so the person on your first call is the person who ships it. I’ve built hotel websites, a quoting system that replaced a distributor’s Excel and an iOS app for health data, and connected booking and smart locks for an overloaded reception. Whatever I build, you get a written handover, and on new projects the domain, hosting, repository and accounts are in your name from day one.
Three characters, one person. Blink listens, Scribble builds, Spark launches, and all three are me.
Proof
FitConnect · Own product
One view for health data scattered across apps
What changedLive heart rate, steps, weight and calories in a single dashboard
On TestFlight, not yet on the App Store. Screens show test data.
Read the case: One view for health data scattered across apps
How it goes
Discovery & proposal
We map the real problem, constraints and what success looks like, then put the scope, fixed price and timeline in writing.
You get: a clear brief and a one-page proposal
30-min call · proposal within two working days
Design & build
You see working software early and often. Brand, interface, and engineering in one pair of hands.
You get: a working build
A testable build in roughly 6–12 weeks
Launch & support
Handover, training, and a single person to call when something needs attention.
You get: the app on TestFlight, the App Store submission and a written handover
Questions
Do you build for Android too?+
I focus on native iOS. That’s where I do my best work. If you really need Android as well, I’ll tell you the trade-offs up front rather than half-build both.
Can you build a web app?+
Yes, as custom software: internal tools and web apps on Next.js or Laravel with Postgres or Supabase. On this page the apps are native iOS.
How soon can I try a real build?+
Early. A focused app reaches a testable TestFlight build in roughly six to twelve weeks, depending on scope, and you’re tapping through working versions on your own phone well before launch.
Who owns the app and its accounts?+
On new projects you do: the accounts are in your name from day one, and the code and documentation are yours once the project is paid. I handle the App Store submission and review at the end.
What does it cost?+
A fixed price per project, agreed before anything starts. No surprise invoices. Tell me the scope and I’ll send you a proposal.
You’re one person, so what if you’re unavailable?+
Fair question. The answer lies in how the project is set up, not in a promise. On new projects, the domains, hosting and repositories are in your name from day one, and the code and documentation are yours once the final payment is made. I build on mainstream tools, not a private framework, so another competent developer can pick it up. For anything in production we agree a response window in writing before it goes live.
