Mobile App Design in Lutsk, Ukraine
UX/UI design for mobile apps for businesses in Lutsk — native iOS/Android plus cross-platform Flutter and React Native. B2C apps for local retailers, B2B tools for furniture manufacturers and car services, loyalty apps for hotels near Lubart Castle. Figma design systems, usability tests.
15+years in product UI/UX design
40+mobile apps designed
Lutskand Volyn — primary location
100+Satisfied clients worldwide
Leave a request
Fill out the form or give me a call
Free consultation
We'll discuss your project and find the best solution
Get the result
Receive your finished app design with UI Kit and prototype
Types of Mobile Design
I design mobile apps for any platform and industry
🍎
iOS app design
Mobile app design following Apple Human Interface Guidelines with native iOS components.
🤖
Android app design
Design following Google Material Design 3 guidelines adapted for the Android ecosystem.
🔄
Cross-platform app design
Unified design for iOS and Android considering differences between both platforms.
☁️
SaaS app design
UX/UI design for cloud services and business tools with complex interfaces.
🛍️
E-commerce app design
Mobile store design with catalog, cart, payment and order tracking.
💬
Social app design
App design for messaging, communities or content platforms focused on engagement.
Work Process
1
Research & Analysis
I study your audience, competitors, and business goals. I conduct UX research and create user personas.
2
Information Architecture
I build the app structure, user flows, and navigation model. I define key usage scenarios.
3
Wireframes
I create schematic layouts for all screens. I test interaction logic before visual design begins.
4
UI Design
I develop the visual style, design system, and detailed mockups for every app screen.
5
Prototyping & Handoff
I create an interactive prototype for testing. I prepare specifications and assets for the development team.
Pricing
Choose the optimal package for your project
Starter
MVP App
10 screens
$1000$1200What's included:
- Design and development of 10 screens
- iOS or Android
- UI Kit components
- Interactive prototype
App ready in 7 days
Basic
Standard App
30 screens
$3000$3600What's included:
- Design and development of 30 screens
- iOS or Android
- UI Kit components
- Interactive prototype
- UX research
App ready in 3 weeks
Business
Pro App
50 screens
$5000$6000What's included:
- Design and development of 50 screens
- iOS or Android
- Design system
- Interactive prototype
- UX research
- Animations and micro-interactions
App ready in 1 month
Premium
Premium App
50+ screens
$5000+$6000+What's included:
- Design and development of 50+ screens
- iOS or Android
- Full design system
- In-depth UX research
- UX strategy and User Flow
- Interactive prototype
- Animations and micro-interactions
- Usability testing
- Personal project manager
- Priority support after delivery
Individual timelines
Cost will be calculated individually depending on your request.
Portfolio
Examples of completed projects
Frequently Asked Questions
Answers to the most popular questions
The price depends on the type of app and number of screens: an MVP app (10–20 key screens, one platform, basic design-token set) starts at the basic package, a full app (iOS + Android, 30–60 screens, dark mode, animations, Dev Mode handoff) is the standard package, and a product system (mobile + web cabinet + admin, shared tokens, design system documentation) is the premium package.
Exact figures are in the “Pricing” block above. The price doesn’t depend on the city — a client in Lutsk, Lviv or Berlin gets the same rates. Lutsk startups that order mobile development or branding in parallel get a combined package with significant savings.
I meet Lutsk clients in person, especially at the start. I usually drive over for a 90–120 minute brief session at your office on Sobornosti avenue, in the “European” business centre on Hrushevskoho, or at one of the coworking spaces on Lesi Ukrainky street — your choice. The Rivne–Lutsk route is ~75 km, so logistics aren’t a problem.
Further work is hybrid: weekly demos in Figma + Zoom, communication in Telegram or Slack, on-device prototypes via Figma Mirror. For larger projects (for example, agri-monitoring for a Volyn holding), additional working sessions can happen in Lutsk on demand — for instance, when we need to test the app together in the real conditions of a field or warehouse.
These are two different interface languages that shape different user expectations:
- iOS Human Interface Guidelines (Apple): tab bar at the bottom, swipe-back from the screen edge, SF Symbols, SF Pro typography, specific push/modal navigation, context menus via long-press.
- Material Design 3 (Google): bottom navigation with different mechanics, FAB, Material Symbols, Roboto/Product Sans typography, ripple effects, Material You with a dynamic palette from system wallpapers.
If you take a single iOS mockup and just port it to Android — the user feels dissonance: “something is off”. So I design two versions where it’s essential (navigation, native components, icons), and one version where the difference is visually negligible (content cards, forms, contextual modals). This balanced approach doesn’t require a doubled budget but delivers a platform-native feel.
I work with all three approaches — and know each one’s constraints:
- Native (Swift / SwiftUI for iOS, Kotlin / Jetpack Compose for Android). Best performance, full access to system APIs. The choice when the app is graphics-heavy (agri maps, AR field monitoring) or when a maximally native feel is required.
- React Native. Saves ~40% of development time thanks to a single codebase. Suitable for most business apps — logistics, HoReCa booking, e-commerce. I know that custom gestures and high-end animations are harder in RN — and I don’t propose them where they’d cause pain.
- Flutter. Best when pixel-identical look on both platforms matters and when the team already works with Dart. Allows complex graphics via CustomPainter.
Before kickoff we always discuss the stack with your CTO or developer — so the design doesn’t propose things that would be expensive or slow on the chosen framework.
Design tokens are a single source of truth for all styles in the app: colours, typography, spacing, radii, shadows, motion curves. Instead of hardcoding “#1A73E8” in twenty places of code, we describe it as color.brand.primary in Figma Variables or Tokens Studio, export to JSON and plug into React Native / Flutter / Swift / Kotlin.
What this gives a Lutsk startup:
- Fast updates. The owner decides to change the primary colour — that’s one token edit, not 20 in code.
- Dark mode out of the box. Paired tokens (light + dark) are described from the start, with no integration pain later.
- Mobile and web cabinet consistency. If we’re also building the web part, tokens are shared — the product looks like one whole.
- Scaling-ready. When a Lutsk startup enters the Polish market and launches a white label — tokens let you “re-skin” the brand in a day.
It depends on the animation type and the framework:
- Lottie — the standard for linear animations (loading, onboarding illustrations, micro-interactions on icons). I export from After Effects via bodymovin into JSON and hand it to the developer. Works natively in iOS, Android, RN, Flutter.
- Rive — a better choice for interactive stateful animations (state machine): a play/pause/loading button; a character changing emotion based on the result; dynamic charts in an agri-monitoring dashboard. The .riv file is lighter than Lottie and lets the code drive animation from the inside.
In design I treat animation not as “decoration” but as a UX element: when the interface feels alive, users trust it. Especially important for HoReCa apps in Lutsk where the emotional layer is part of the product, and for agri apps where “breathing” field charts help read state faster.
Yes — dark mode is built in from day one, not “added later”. At the design system stage I build a paired palette: for every semantic token (background, surface, text, border, accent), light and dark values are described simultaneously.
What this means in practice:
- I draw every screen in both themes from the start and verify contrast meets WCAG AA (4.5:1 for text).
- Special attention to images and illustrations — some illustrations get a separate dark version so they don’t look “cut from a white sheet”.
- I test theme switching — the transition shouldn’t “flicker” due to mis-calculated shadows or gradients.
For Lutsk apps, where users often work in the evening or in the field under varied lighting (agri, logistics), dark mode isn’t a “feature” — it’s a baseline need.
Standard cycles for mobile apps:
- MVP (10–20 screens): 4–6 weeks from brief to final handoff.
- Full app (30–60 screens, iOS + Android): 8–12 weeks.
- Product system (mobile + web + admin): 12–16 weeks, iteratively.
The time structure is usually: 15% discovery (brief, user interviews, competitive analysis — for example, I analyse foreign agri apps if you’re building for Volyn agriculture), 20% IA + flows + wireframes, 40% UI + design system + dark mode, 15% animations, edge cases, micro-interactions, 10% handoff and developer support at the start of implementation. If the app runs in parallel with backend development, we sync the cycles.
I work mostly via Figma Dev Mode — the modern standard that replaced Zeplin/Avocode in most product teams:
- The developer opens the file, switches to Dev Mode and immediately sees tokens, spacing, typography, even ready code snippets for CSS / React Native StyleSheet / SwiftUI / Compose.
- All components in the library are labelled with code-side correspondence — for example,
ButtonPrimaryLargein Figma maps to the same-named component in React Native. - Spacing and auto-layout inspection — exactly as it will be in code.
For teams that prefer Storybook, I additionally prepare component docs in a Storybook-compatible format. If your Lutsk dev team hasn’t worked with Dev Mode before — I run a separate 60-minute onboarding session showing the process. This often saves weeks of misunderstandings.
From my Volyn region practice, the most common categories are:
- Agri-monitoring. Apps for farmers and agri-holdings — field monitoring via satellite indexes (NDVI), soil-moisture sensors, weather data, treatment journals. Volyn is a strong agri region, demand is growing.
- Logistics and export. Due to proximity to the Polish border (~70 km to Yahodyn) — apps for drivers, dispatchers, customs brokers, freight forwarders. CMR scanning, truck tracking, push notifications about border queues.
- HoReCa. Table booking, delivery ordering, loyalty programs for restaurants around Lubart’s Castle and in the PortCity mall.
- Manufacturing and B2B. Apps for dairy plant employees, factories, warehouses — accounting, checklists, inventory.
- Healthcare. Booking for private clinics (Adonis, AVENA), patient cabinets.
- SaaS startups. Lutsk product teams build apps for the Polish and German B2B markets — a separate category where GDPR and localisation matter.
Each category has its own UX approach and tech stack.
Yes, in the part of store design and assets:
- App icon — I create it in all needed sizes for iOS (1024×1024 + adaptive layers) and Android (adaptive icon with foreground / background / monochrome for Material You).
- Store screenshots — 6–10 mockups with captions, adapted for iPhone 6.7" / 6.5" / 5.5" and Android phone / tablet. I localise UA, EN, PL on demand.
- Feature graphic, promo video frames — for Google Play.
- App Store / Play Console text — short and full description, keywords, what’s new — I help craft them with you.
The technical release (build, provisioning, App Store Connect) is the developer’s job or that of mobile development. If you’re still searching for a developer — I recommend partner Lutsk and Lviv teams I’ve worked with.
Yes, fully. About 70% of my clients are outside Volyn (Kyiv, Lviv, Poland, Germany, the US), and we work entirely online: brief via a Notion document + Zoom, presentations in Figma, communication in Telegram or Slack. For a Lutsk client this format is also available.
But if you’re in Lutsk and want to meet — I’ll come over. I particularly recommend an in-person brief for agri projects (it’s often useful to drive out to the field together to see the real usage context) and logistics (visit a warehouse, watch the dispatcher work). This knowledge can’t be transmitted via a call — and it’s exactly what makes the difference between “a nice mockup” and “an app people actually use”.
Why choose me?
Comparison with other options
| Alex Filiuk | Lviv product teams / NIX Lutsk / freelancers | |
|---|---|---|
| In-person meetings in Lutsk | ✅ I drive over for briefs (≈75 km from Rivne) | ❌ Zoom only or rare visits |
| iOS HIG + Material Design 3 | ✅ Two distinct versions where it matters | 📋 Often one mockup copied from Android |
| Design tokens in Figma | ✅ Variables + Tokens Studio, JSON export | ⚠️ Hardcoded styles, no single source |
| Figma Dev Mode readiness | ✅ All components, spacing, tokens | ❓ Developer eyeballs sizes in Figma |
| Lottie / Rive animations | ✅ I deliver ready .json / .riv files | 💰 Animations are an extra budget item |
| Dark mode from day one | ✅ Paired palette in tokens | 🔄 Bolted on later, with bugs |
| React Native / Flutter experience | ✅ I know both frameworks’ constraints | ❓ Designs as if it were web |
| EU / Polish market export | ✅ GDPR-aware, PL/DE/EN localisation | 📋 UA/RU only |
| Fixed price and timeline | ✅ Transparent package, no surprises | 💰 Hourly model with no ceiling |
Mobile App UX/UI Design in Lutsk, Ukraine — iOS, Android, Flutter | Alex Filiuk
Mobile App Design in Lutsk — UI/UX for iOS, Android and Cross-Platform Apps
A mobile app for a business in Lutsk and the Volyn region is no longer “a nice bonus to the website” — it’s often the main channel of customer interaction. A farmer near Kovel checks the field state in the app before driving the tractor. A dispatcher at a logistics company on Voli avenue scans a waybill on the phone before a run to Yahodyn. A guest at a restaurant by Lubart’s Castle books a table in a couple of taps. In all these scenarios, UI/UX quality directly determines whether the user completes the action — or moves on to a competitor. I’m Alex Filiuk, a Senior UI/UX designer with 15 years of experience, designing mobile apps for Ukrainian and international clients. The portfolio holds 130+ projects, of which 40+ are mobile design. This page brings together everything a Lutsk business owner or startup CTO should know before commissioning app design.
Why app design in Lutsk is not “the same as in Kyiv”
The Lutsk mobile app market has its own specifics that matter in design:
- Proximity to the Polish border (~70 km to Yahodyn). Many Lutsk businesses are export-oriented to Poland and the EU, so apps often require PL/DE/EN localisation, GDPR compliance and alignment with European UX patterns. This affects everything — from error message tone to permission request flow.
- Strong Volyn agri sector. Cereals, rapeseed, potatoes, livestock — Volyn farmers are serious buyers of tech solutions. Their apps must work in the field (unstable internet, gloves, bright sun on screen), not only in office Wi-Fi.
- HoReCa around Lubart’s Castle. Tourist flow plus Volyn cuisine creates demand for booking apps, loyalty programs, QR menus. Speed and beauty matter — a guest evaluates the app in 5 seconds.
- Small but dense IT market. NIX Lutsk, Webx, local product teams — ~3-5k IT specialists in the region. Competition for good UI/UX design is high; only quality stands out.
- Business relocation 2022+. After 2022 Lutsk welcomed companies from Kharkiv, Mariupol, Dnipro, Kyiv. Some stayed — and that added new product teams to the market with EU expansion ambitions.
iOS Human Interface Guidelines vs Material Design 3 — how I choose the interface language
One of the key decisions in mobile app design is platform nativeness. This isn’t a religious question, it’s an economic and UX one. I work with two modern standards:
- iOS Human Interface Guidelines (HIG) — Apple’s official recommendations. Tab bar at the bottom, swipe-back from the left edge, SF Symbols as the icon language, SF Pro as typography, push/modal navigation as iOS NavigationStack basis, specific context-menu logic via long-press, native haptic feedback.
- Material Design 3 (Material You) — Google’s current design language. Bottom navigation with mechanics different from iOS, Floating Action Button, Material Symbols, Roboto / Google Sans typography, ripple effects on tap, dynamic palette from the user’s system wallpaper.
What this means for a Lutsk startup:
- If your app is for a mass consumer (HoReCa, e-commerce, banking) — we definitely build native versions for iOS and Android. Users are accustomed to their platform and notice mismatches at the subconscious level.
- If the app is for internal users (B2B, corporate tool) — often we go with a single design, closer to Material — it saves budget and doesn’t hurt UX.
- If the app targets a niche audience (e.g. Volyn agronomists) — we look at device statistics: if 80% are on Android, focus on Material and create an adapted iOS version.
Design tokens, Figma Variables and a unified design system
In 15 years of practice I’ve seen dozens of apps that became unmaintainable because styles were hardcoded chaotically. One colour — in twenty places. One spacing value — in fifty. Changing a single brand parameter turns into a week of developer work. Design tokens are the systemic antidote:
- Color tokens. All app colours are described semantically:
color.background.primary,color.text.muted,color.border.subtle,color.accent.brand. In Figma Variables we create paired light + dark values. - Typography tokens. Sizes, line heights, font weights — described as roles:
font.heading.lg,font.body.md,font.caption.sm. This makes typography predictable across all 60 screens. - Spacing tokens. A base grid of 4px-multiple spacings —
space.xs,space.sm,space.md,space.lg. Everything aligns, nothing drifts. - Motion tokens. Animation durations and easing curves —
motion.duration.fast,motion.easing.standard. All transitions in the app feel like one whole. - Radius, shadow, opacity tokens. Same for corner radii, shadows, opacity.
These tokens export to JSON via Tokens Studio (a Figma plugin) and plug into code via style-dictionary, NativeBase, Tamagui or a custom implementation — depending on the stack. If we’re also doing the web part or a CRM cabinet, the tokens are shared — the product feels coherent across all platforms.
Figma Dev Mode — what modern developer handoff looks like
Five years ago Zeplin or Avocode were the standard — separate tools for handing off designs to developers. Today all that is absorbed by Figma Dev Mode, which delivers much more:
- Style and spacing inspection. The developer hovers over an element and immediately sees all CSS / React Native / SwiftUI / Jetpack Compose values.
- Ready code snippets. Figma generates initial style code — not “how to write”, but a starting point for copy-paste.
- Code linkage. Components in Figma can be linked to specific files in GitHub — the developer sees exactly which component to implement.
- Annotations. I can leave notes on the mockup itself — explanations of edge case behaviour, animation descriptions, links to API specs.
- Tokens in Dev Mode. All design tokens appear as variables with clear names — the developer uses semantics, not magic numbers.
For a Lutsk dev team encountering Dev Mode for the first time I run a separate 60-minute onboarding session. This often saves weeks of misunderstandings — especially when part of the team is remote.
Lottie and Rive — animations that won’t break the app
Animation in a mobile app isn’t “decoration”, it’s a UX element. A well-made micro-interaction makes the interface clearer (the user sees what happened) and the app more pleasant to use. I work with two main tools:
- Lottie. The standard for linear animations from After Effects via bodymovin export. Ideal for onboarding illustrations, success animations, loading indicators. .json files are very light (often <100 KB), natively supported in iOS, Android, RN, Flutter.
- Rive. A modern alternative with state machine support — animation reacts to app state without custom code logic. Examples: a like button that morphs based on like count; a mascot character changing emotion based on action result; dynamic charts in an agri-monitoring dashboard. .riv files are even lighter than Lottie.
In design I introduce animations consciously — every micro-interaction has a reason. No reason — drop it. That’s the difference between “your app feels laggy” (when there are too many heavy animations) and “your app reacts instantly” (when animations clearly assist).
Dark mode — not a “feature”, a baseline need
Lutsk context: users often work in the evening, in cars, in fields under bright or changing light. Dark mode isn’t a fashionable option, it’s a baseline requirement of a modern app. I build it in from day one, not “add it later”:
- Every design token has paired values — light and dark from the start.
- Every screen is verified in both themes — for contrast meeting WCAG AA (4.5:1 for body text, 3:1 for large).
- Images and illustrations have separate dark versions — so they don’t look “cut from a white sheet”.
- Theme transitions are animated smoothly — no flickering shadows or gradients.
React Native, Flutter or native — how to choose the stack
Before I start drawing mockups, I discuss the technology stack with the client and their developer (or CTO, if it’s a Lutsk product team). Because design must respect framework constraints:
- Native (Swift / SwiftUI or Kotlin / Jetpack Compose). Best performance, full access to system APIs (camera, AR, Bluetooth Low Energy for agri sensors). The choice for high-end products and graphics-heavy apps.
- React Native. Saves ~40% of time and budget thanks to a single JS/TS codebase. Suitable for most business apps — logistics, booking, e-commerce, B2B tooling. I know that custom gestures and complex parallax animations are difficult in RN — and I don’t propose them where they’d cause pain.
- Flutter. Best when pixel-identical look across iOS and Android matters, or when your team already works with Dart. Powerful for custom graphics via CustomPainter and skin flexibility.
If you haven’t chosen a stack yet — at the consultation I help you decide based on your budget, timeline and ambitions.
Competitors in Lutsk — who they are and why I’m a better choice
An honest assessment of the field:
- Lviv product teams. Strong players (~145 km to Lviv), often take Lutsk clients remotely. Strength — product experience. Downside — pricing and distance: live sessions in Lutsk are rare.
- NIX Lutsk, Webx. Large outsource teams, mostly working with international clients. Design is part of the package, but not the highlight of their offering.
- Local freelancers. Affordable, personally accessible — but often without product UI/UX experience (they make “pretty pictures”, not systems). Big risk on handoff and dark mode.
- Kyiv agencies. Work with Lutsk clients fully online. High level, high price.
My positioning — Senior level with 15 years of experience, fully remote work with Lutsk businesses (75 km from Rivne), fixed price and transparent timelines. The price range sits between freelancers and Kyiv agencies, but quality is at the Kyiv level.
Cases: mobile apps in the portfolio
In the portfolio you can see work on apps across categories — from service booking and CRM to healthcare and e-commerce solutions. Among them are apps for Ukrainian and international clients, product redesigns, MVP startups. If you want concrete examples for your niche (agri, logistics, HoReCa, healthcare) — write via the contact form, and I’ll pick 5–7 most relevant cases with full process descriptions: from research to Dev Mode handoff.
Project stages — what happens over 8–12 weeks
- Discovery (week 1). Brief, interviews with 3–5 potential users (via Zoom — including farmers, dispatchers, and other field roles), competitive market analysis (including foreign analogues from Poland and Germany), benchmarks.
- Information Architecture + Flows (week 2). Screen map, user journeys, primary scenarios, edge cases. Approval with the client.
- Wireframes (week 3). Low-fidelity mockups, focused on structure and logic. The cheapest stage for changes — reworking wireframes is 10x faster than UI.
- Design system foundation (week 4). Color, type, spacing, motion tokens. Base components (Button, Input, Card, ListItem). Paired light/dark palette.
- UI design (weeks 5–8). All screens in their final form. iOS and Android versions where needed. Component library. Dark mode in parallel.
- Animations + edge cases (weeks 9–10). Lottie/Rive files, micro-interactions, empty states, error states, loading states.
- Handoff (weeks 11–12). Figma Dev Mode-ready, documentation, developer onboarding, supervision at the start of implementation.
What you receive after project completion
- Figma file with full component library, tokens, all screens in two themes.
- JSON token export via Tokens Studio for code integration.
- Lottie/Rive files of all animations.
- App Store and Play Store assets — icon, screenshots, feature graphic, descriptions (UA, EN, PL on demand).
- PDF documentation of the design system with usage rules and examples.
- Recording of the onboarding session for developers — Dev Mode, tokens, library.
- Support during development — 30 days free after handoff: answers to developer questions, minor fixes, consultations.
My other services for Lutsk businesses
App design is part of an ecosystem. If you’re planning a full product launch, it’s worth combining with:
- Mobile development — implementation in React Native, Flutter or native.
- UI/UX web design — for the web cabinet or app landing page.
- Web development — backend, API, admin.
- CRM/ERP/SaaS — internal panel for the app operator.
- Branding — logo, brand identity that becomes the basis of tokens.
- UX audit — if you already have an app and want to understand where it loses users.
- Product strategy — positioning and roadmap to launch.
- Conversion optimization — for apps with commercial flows.
Mobile app design in other Ukrainian cities
I work not only with Lutsk. I actively collaborate with teams in:
- Kyiv — product SaaS, fintech, e-commerce
- Lviv — IT outsourcing and product companies
- Odesa — tourism, e-commerce, retail
- Dnipro — B2B, manufacturing, technology
- Kharkiv — IT, education, engineering
The full list — on the “Service Areas” page.
Ready to discuss a mobile app for your Lutsk business?
If you have a specific request — write via the contact form. The first consultation is free, up to 60 minutes. We discuss: app type, target audience, technology stack (or I help you choose it), approximate timeline and budget. After the consultation — a detailed proposal with a fixed price, no surprises.
I’m ready to design an app for your business in Lutsk that’s not “one of those”, but a real growth tool — on iOS, Android or cross-platform, with a thoughtful token system ready to scale to the Polish, German and broader EU market.