Mobile and web apps, backends that handle load, interface design. You talk directly to the person who writes the code and owns the deadline — no account managers, no status calls, no retelling through third parties.
Send your task and get a breakdown, the key architecture decisions, a timeline and a price range. One document, no "let me check with the team".
I take on projects where the solution has to hold together: one person is responsible for architecture, code and deadline, so nothing gets lost in handoffs.
iOS and Android from a single codebase with Kotlin Multiplatform where it makes sense, and native where nothing else will do.
From an idea to a version you can show to users and investors. We build the shortest thing that's already useful.
Customer portals, dashboards, internal tools. Fast interfaces you won't have to apologize for.
APIs, queues, data processing. Designed so that traffic growth is a reason to celebrate, not to be on call.
The interface is designed together with the logic, not stretched over it. One author, one consistent system.
That's a normal place to start. We'll sort it out together, and you'll get back a problem statement you can actually work with.
No surprises in the invoice or the timeline: every stage ends with something you can open and try.
A short call or a written brief — your choice: what the business does, where it hurts, what you use now. Sometimes it turns out you don't need development at all — I'll tell you so.
Architecture, stages, risks and a price range on a single page. No 40-page appendices, no terms you'd need a lawyer to decode.
The core user flow end to end: screens, data, deployment. At this point it's already clear whether we're building the right product.
Access to the repository and staging from day one. Plans change — you'll know the cost of a change before I start on it.
I stay on for further development or hand the project over to your team, with documentation people can actually read.
A few things I've built and shipped.
Android and iOS, Kotlin Multiplatform. I worked on it as a KMP developer in a team of 7.
My own app. One Kotlin Multiplatform codebase with Android, iOS, desktop and web targets — live on Google Play.
My own service for running my marketplace store: Android and iOS apps with a Ktor backend.
A jobs and services marketplace built with Flutter. The move from API 35 to 36 broke the edge-to-edge layout — found and fixed within a day.
The document stays with you whether or not we work together. You can take it to any contractor — it's a fair way to get acquainted.
The stack is chosen for the task, not for the résumé. If it's cheaper to build on off-the-shelf services, I'll say so — even if it makes the invoice smaller.
Because the risk is capped by stages: the first is a free estimate, the second is a working skeleton for a fixed price. You decide whether to continue after each one, not at the very beginning.
The person you're talking to: architecture, code and release are on me from start to finish. For narrow areas I bring in specialists I trust, but responsibility for the deadline and the result isn't shared.
The repository, infrastructure and documentation live in your accounts from day one. Work is paid stage by stage — half upfront, the rest on delivery — so you never pay for more than the current stage.
It depends on scope, but you'll get a price range on day three — free and with no obligation. I work with a fixed price per stage or hourly, from €30 per hour — whichever suits you.
In English, mostly in writing: a shared chat, written updates and a short demo video at the end of every stage. Calls when they genuinely help. I'm online 07:00–16:00 UTC.
You get an invoice in EUR or USD for each stage and pay by bank transfer. Half of the stage is paid upfront, the rest when you accept the result.
A couple of paragraphs about where things stand and what you'd like is enough. Then a short call or a written Q&A — your choice — and an estimate on day three.
I'll reply with two or three questions and suggest a time for a call — or we can keep it in writing if you prefer.
Faster on TelegramI'll reply from sergei@skilanet.co within one working day — usually in 2–3 hours.