Simplified sign-in
Fast sign-in and registration by phone number, with a personal guest account.
Restaurants · Mobile app
Vilka-Lozhka is a mobile app for a fast-casual restaurant chain. YuSMP took over two live native apps with accumulated bugs and an unstable payment flow, fixed the critical issues, and added a loyalty program, built-in card payments and pickup ordering.

In short: what the product is and who we built it for.
Vilka-Lozhka is a chain of farm-to-table cafes serving home-style food made from country produce. The client already had iOS and Android apps, but they had accumulated technical debt: critical bugs, unstable payments and a fragmented customer journey from the menu to checkout. The task wasn't to build a product from scratch but to fix an existing one — keeping the audience and the habits users already had, while making the app reliable and modern.
We took both native apps into work in parallel, synchronized their logic around a shared backend, and reworked the key flows: sign-in, the menu catalog, the cart, checkout and pickup. As a separate track, we added a loyalty program with a bonus balance, so the app would not just take orders but also bring guests back.
The existing apps worked, but unreliably: users ran into errors, and the payment flow failed from time to time — directly hurting revenue and trust. The client needed the apps brought up to standard without losing the guest base already built up.
The second goal was growth: the chain lacked a loyalty program and convenient pickup ordering. Without a bonus balance and a clear way to pick a restaurant and pickup time, the app stayed a menu showcase rather than a tool for repeat orders.
How we built the product, from architecture to process.
We started with an audit: we listed the critical bugs and the weak points of the payment flow, then split the work into two tracks — stabilization and growth. In stabilization we fixed the bugs and rebuilt payments on built-in card processing with saved cards. In growth we added new scenarios without breaking the interface guests were used to.
We laid out the customer journey linearly: simplified sign-in by phone number, an intuitive catalog and cart, then checkout with pickup selection, a ready time and bonus points covering up to 30% of the order. iOS and Android were developed in parallel on native Swift and Kotlin stacks, while the backend logic and loyalty program ran on PHP Laravel, so both platforms worked off the same data.
Tools chosen to fit the product’s goals.
With a mature codebase, a full rewrite means losing accumulated business logic and a long regression period. A refactor keeps the working modules, fixes specific problems, and gets back into the app stores faster.
Key capabilities that solved the business problem.
Fast sign-in and registration by phone number, with a personal guest account.
An intuitive menu catalog and a cart showing the order contents, quantities and the total.
Reliable payment right inside the app, with saved bank cards.
Pickup checkout with a choice of restaurant, address and ready time.
A bonus balance that accrues and can be spent — covering up to 30% of the order total.
Critical bugs and payment failures that hurt revenue and guest trust were eliminated.
Key product screens, step by step.



The app opens with a branded splash screen for the Vilka-Lozhka farm cafe, tagged with "Home-style food from country produce".
Next comes a visual showcase of farm products and a "40 minutes" badge that sets the tone: fresh food, fast. The style is clean, light and close to the chain's brand.


Sign-in is built on simplified authentication: the guest enters a phone number on the "Sign up" screen and taps "Next", agreeing to the terms of use.
A minimal number of fields and a clear keyboard lower the barrier to entry — guests reach their account and start ordering in just a few steps.


In the "Cart", dishes are grouped by line item with a photo, name, price, quantity and packaging type (container, cup).
At the bottom is the order total and a "Checkout" button. Each item can be removed, and the full cart contents are visible before moving to checkout.


At checkout, the guest picks the restaurant address, leaves a comment, and sets a pickup time, with the option to change it within the nearest window (~40 minutes).
A separate checkbox lets guests apply bonus points to cover up to 30% of the total — so the loyalty program is built right into checkout.


The second checkout step is delivery and payment: the guest fills in the address (city, street, apartment, entrance, floor) and picks a saved card from the list.
Built-in card processing stores several cards with masked numbers, and an order comment field lets guests add details — for example, "no mushrooms".
The native iOS and Android apps talk to a server API. The payment flow runs through a card-processing SDK: card data is not stored on the app's server and is tokenized on the payment gateway's side.
The apps handle personal data — phone number, order history, bonus balance. Data is processed under the requirements of the client's jurisdiction and stored on servers hosted locally, with role-restricted access.
2 native apps — iOS and Android: a deep refactor of the legacy codebase, not a rewrite from scratch.
Critical bugs eliminated: payment crashes, lost sessions, incorrect cart recalculation.
Loyalty program: sign-up by phone number, a bonus balance that accrues and can be spent.
Built-in card payments: one-off and recurring payments without leaving the app, card data is not stored.
Pickup ordering: choosing a restaurant from a map list and a convenient pickup time.
Published in the App Store and Google Play: both apps passed store review and were released.
Refactoring is reworking existing code without changing its outward behavior: fixing bugs, improving structure, optimizing performance. It's an alternative to a full rewrite — accumulated business logic is kept, and the app reaches the stores faster.
A user signs up by phone number and gets a bonus balance. Points accrue with every order and can be used to pay for the next one. Points history is visible in the app's personal account.
Built-in card processing lets guests pay for an order directly inside the app without leaving to an external page. Both one-off and recurring payments are supported. Card data is not stored: it is tokenized on the payment gateway's side.
Personal data is processed under the requirements of the client's jurisdiction. Data is stored on locally hosted servers with role-restricted access, and users give consent to data processing before using the app.
Timelines depend on the volume of legacy code, the depth of the required changes and whether technical documentation exists. A typical range for projects like this is 12–20 weeks. This isn't a guarantee for any specific project — actual timelines are agreed at the briefing.
Companies from retail, medtech, logistics and e-commerce that we helped build digital products.
The full spectrum of development — from native mobile apps to web platforms, AI and cloud. Pick a direction or order a turnkey project.
Native iOS & Android plus cross-platform Flutter and React Native — from MVPs to apps with millions of installs.
Learn moreNative Swift / SwiftUI iOS apps — with Apple Pay, Sign in with Apple, App Store Connect deployment pipelines.
Learn moreNative Kotlin / Jetpack Compose Android apps — Material 3, Google Play release pipelines, Firebase integration.
Learn moreSingle Dart codebase across iOS, Android, web and desktop — with native modules where needed.
Learn moreProduction web apps on React, Next.js, Vue and Node — SaaS dashboards, B2B portals, marketing-conversion stacks.
Learn moreREST, GraphQL and gRPC APIs — designed for partners, mobile clients and internal microservices.
Learn moreBespoke platforms for mid-market and enterprise teams — internal tools, vertical SaaS, mission-critical backends. Discovery to launch in 12–36 weeks.
Learn moreFocused MVPs in 12–20 weeks — one or two integrations, real users on day one, telemetry built-in.
Learn moreEnd-to-end ownership of a digital product — design, build, ship and continuous evolution.
Learn moreTool-using agents that plan, retrieve, act and self-evaluate — in customer service, ops automation, internal copilots.
Learn moreAWS, Azure and GCP architecture, Kubernetes, Terraform/Pulumi, CI/CD and observability — SRE-grade operations for product teams.
Learn moreTechnical SEO, Core Web Vitals, structured data, internal-link architecture — built into your engineering process.
Learn moreRelated cases

Rapid clickable prototype that scoped the MVP and cut the mobile build budget 20% before a line of production code — US & EU ready.
View case
iOS & Android apps, a courier-routing engine, and a multi-role ops panel on a shared Laravel backend — multi-vendor ordering for the US & EU.
View case
Native events, booking, and ticketing app with QR entry — events discovery for Armenia, engineered to US & EU client standards.
View case20 articles across 5 categories — engineering-led guides on AI, SaaS, MVP, compliance and mobile for US and EU product teams.

Performance-tested comparison of RN (New Architecture) and Flutter (Impeller) across hiring, time-to-market and EU/US compliance.
Read article
Real cost ranges by region (US onshore, Western EU, EU nearshore), team and feature scope. With a worked fintech example.
Read article
Data-driven framework for choosing iOS-first or Android-first in 2026 — US & EU market share, ARPU, review timelines, EU DMA.
Read articleTell us about your app and where it's struggling — bugs, payments, loyalty or ordering flows. We'll help you plan a refactor that keeps your audience and modernizes the product underneath.
Share a few details and a senior consultant will reply within one business day.
Email: sales@yusmpgroup.com
Phone: +374 44 871 811
Offices: KAMAR Business Center, Vazgen Sargsyan St. 2, Yerevan, Armenia · Remote — East-Coast US overlap (9 AM–1 PM ET)