Mobile App Design in Lutsk, Ukraine

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:

1. Style and spacing inspection. The developer hovers over an element and immediately sees all CSS / React Native / SwiftUI / Jetpack Compose values.
2. Ready code snippets. Figma generates initial style code — not “how to write”, but a starting point for copy-paste.
3. Code linkage. Components in Figma can be linked to specific files in GitHub — the developer sees exactly which component to implement.
4. Annotations. I can leave notes on the mockup itself — explanations of edge case behaviour, animation descriptions, links to API specs.
5. 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

1. 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.
2. Information Architecture + Flows (week 2). Screen map, user journeys, primary scenarios, edge cases. Approval with the client.
3. Wireframes (week 3). Low-fidelity mockups, focused on structure and logic. The cheapest stage for changes — reworking wireframes is 10x faster than UI.
4. Design system foundation (week 4). Color, type, spacing, motion tokens. Base components (Button, Input, Card, ListItem). Paired light/dark palette.
5. UI design (weeks 5–8). All screens in their final form. iOS and Android versions where needed. Component library. Dark mode in parallel.
6. Animations + edge cases (weeks 9–10). Lottie/Rive files, micro-interactions, empty states, error states, loading states.
7. 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.