Flutter Developer / Mobile Engineer
Complex Flutter products,shipped all the way to production.
I own the architecture of a white-label ordering core and have developed its kiosk since the first version for an ecosystem used by 100+ restaurants. I integrate POS, payments and release workflows across iOS, Android, Web and Desktop.
- Flutter
- Dart
- Architecture
- Payments / POS
- Astana, Kazakhstan
- Open to
- Full-time · Part-time · Contract / Hybrid · Remote
- Languages
- Russian — native · English — B2
My strongest work happens at the boundaries where a mobile app meets payments, POS systems, hardware and live production.
I work beyond the UI: designing state and contracts, diagnosing payment and order failures, and carrying changes through to release builds.
Ownership
Architecture of the white-label ordering core and kiosk development since its first version.
Hard boundaries
iiko, Poster, Kaspi QR, JetPay and five physical POS terminal providers.
Full delivery cycle
From design and tests to App Store, TestFlight, web and desktop releases.
02Selected work2024 — 2026
CASE 01
AI Lillu
Qi Tech Ltd · Jul 2025 — Present
HoReCa product ecosystem
A restaurant ordering ecosystem built from a white-label core for branded apps and a separate self-service kiosk. I own the core architecture and led its refactoring while the product remained in active use; I have developed the kiosk since its first version.
100+restaurants running
the Flutter experiences
Idle screenWaiting for the first touch
Dish detailReached from the menu grid
Kiosk platformsOne kiosk codebase, four targets
iOS / iPad
Android
Desktop
Web
Product surfacesShipped from the ordering core
01Guest
QR Menu
Scan at the table, browse, order, pay.
02Brand
Restaurant app
A branded child app off the shared core.
03Real time
AI chat
Chat with voice, over WebSocket.
White-label architecture
One core package, many restaurant apps.
The ordering product is a Flutter package, while branded apps remain thin child repositories. The architecture evolves centrally without duplicating business logic across restaurants.
The kiosk is a separate application: branding and restaurant-specific behavior arrive from the admin panel.
AI Lillu core
shared Flutter package
- brand app
- brand app
- brand app
Branded child apps
Separate codebase
Admin panel
per-restaurant config
Kiosk
one app, same architecture
Integrations
An order crosses four systems before it reaches the kitchen.
My job here is to keep order and payment state consistent across the app, restaurant POS, payment provider and physical terminal.
I diagnose failures at those boundaries, cover critical flows with tests and carry fixes through release, including self-updating desktop kiosks in the field.
External systemsthe restaurant already runs these
iiko
The restaurant POS: menus, stop-lists and open table orders. It stays the source of truth.
CASE 02Open source · MIT
Declare OS-level app actions in Dart. The generator emits the iOS App Intents and Android AppFunctions code the system needs at compile time, so Siri, Spotlight, Shortcuts and on-device agents can run your app’s actions — ideally without opening the app at all.
The pitch in one line: you never open Xcode.
@AppIntent(
title: 'Add task',
phrases: [r'Add a task to $app'],
execution: Execution.background,
)
Future<IntentResult> addTask({
@Param(title: 'Title')
required String title,
DateTime? dueDate,
}) async { /* your logic */ }Proof, not a mock-up
The OS ran the handler. The app never opened.
A Dart handler, invoked by iOS from the Shortcuts app. The prompt is declared in the annotation; the answer is the handler’s return value. iOS ran the process in the background and never brought the app to the foreground — measured, not assumed.
Runner[91295] OSINTENTS_HOST
intent=addTask process=Runner uiEngine=yes
CASE 03
Enki
dBridge LLP · Sep 2024 — Jul 2025
B2B construction platform
A B2B application for construction teams across Flutter mobile and web. My contribution covered feature modules in Clean Architecture, role-based access, REST integrations, push notifications and review-driven work in a shared codebase.
Feature-first, layered
What I worked on
- Feature modules for Flutter mobile and web
- Clean Architecture and BLoC in a shared codebase
- REST, Firebase messaging and RBAC
- Code review and architecture decisions
04How I work
Constraints and risks first. Then architecture that survives production.
Context
Map product, integration and release constraints.
Solution
Design the smallest viable architecture and explicit scenario states.
Verification
Test critical branches, especially orders and payments.
Delivery
Carry the change into a build and observe it in production.
Stack
Architecture
- Flutter / Dart
- Clean Architecture
- BLoC
- Testing
Data & integrations
- REST
- WebSocket
- iiko / Poster
- Payments & POS
- Firebase
- Amplitude
Platform & delivery
- iOS / Android
- Flutter Web
- Desktop
- GitHub Actions
- TestFlight
- Docker
05Experience
Astana, Kazakhstan
Astana IT University
B.Sc. Software Engineering, 2023 — 2026
I am looking for a Flutter role with real users and engineering ownership beyond UI.
Jul 2025 — Present
Flutter Developer
Qi Tech Ltd · AI Lillu
In a three-developer Flutter team, I own the ordering core architecture and have developed the kiosk application since its first version.
- White-label core
- iPad kiosk
- POS terminals
- Desktop self-update
Sep 2024 — Jul 2025
Flutter Developer
dBridge LLP · Enki
Mobile and Flutter Web for a B2B construction platform, in a codebase shared with a team.
- Clean Architecture
- BLoC
- RBAC
- Code review