Blog News Contact Get a proposal

Flower delivery · Discovery for 2 mobile apps

FlowDelivery: discovery for a flower delivery app

A discovery phase for two mobile products of a flower shop chain: a customer app for ordering flowers with delivery and an internal florist app for managing the range. One data model, auto-hiding of bouquets when components run out, and prototypes ready for development.

Discovery for two linked mobile apps: customer and floristSingle data model: bouquets, components and stock in one systemBouquet auto-hidden when any component runs outSmart catalog with automatic visibility updates3-step checkout: cart → details → confirmationCostly extra feature cut at design stage for a simpler architecture
FlowDelivery — Flower delivery, e-commerce
FlowDeliveryFlower delivery, e-commerce
ClientFlowDelivery, a chain of flower shops
IndustryFlower delivery, e-commerce
PlatformsMobile: customer app and florist app
TimelineDiscovery phase: design, prototypes, documentation

About the product

In short: what the product is and who we built it for.

FlowDelivery is a chain of flower shops that needed its digital flower delivery ecosystem designed before development began. The task was to run a discovery phase and prepare a complete package of documentation and prototypes for two mobile products sharing one data model and non-trivial stock availability logic.

The discovery covered two interconnected apps at once: a customer app for ordering bouquets with delivery, and an internal florist app for managing the range and keeping track of component availability.

The challenge

A bouquet is a composite product: it is assembled from components, and any of them can run out of stock. Showing customers a bouquet that cannot be assembled is unacceptable, as it leads to cancelled orders and disappointment.

The key design task was therefore to link the customer catalog and the florist’s stock records through one data model in which bouquet availability is recalculated automatically. Just as important was not to overcomplicate the system and to fit the architecture into a reasonable development budget and timeline.

Project highlights

  • Smart bouquet catalog driven by component stock
  • Dynamic product card with price and composition
  • 3-step checkout
  • Range management for florists
  • Automatic availability recalculation
  • Two apps on one data model

Solution and approach

How we built the product, from architecture to process.

During discovery we designed the architecture of both apps on one data model: the bouquet catalog, components and stock live in a single system, and bouquet availability is calculated automatically. The core of the logic is auto-hiding: if any component runs short, the bouquet is automatically removed from the customer catalog and returns once stock is restored.

For both the customer and the internal product we prepared clickable prototypes of the key screens and documentation sufficient for handover to development. When one of the proposed features turned out to be redundant and expensive, the team proposed a simpler architecture that kept all the required functionality.

Tech stack

Tools chosen to fit the product’s goals.

AnalyticsAnalysis of scenarios and requirements during discovery
DesignUI/UX design and clickable prototypes

Why discovery before development instead of building right away

A discovery phase is structured product design before the first line of code is written. For a task with two interconnected apps and a shared data model this matters most of all: an architectural mistake at the start turns into rework of both products during development.

Product features

Key capabilities that solved the business problem.

Smart catalog

Bouquet visibility updates automatically based on component availability.

Product card

A dynamic card: price, composition and add to cart.

3-step checkout

Cart → checkout → order confirmation.

Range management

Florists add and edit bouquets.

Stock control

Component availability is recalculated automatically.

Bouquet auto-hiding

A bouquet is hidden from the catalog when any component runs short.

How it works

Key product screens, step by step.

FlowDelivery customer app catalog with category filters and express delivery, and a bouquet card with price and compositionFlowDelivery customer app catalog with category filters and express delivery, and a bouquet card with price and composition

Catalog and product card

The home screen of the customer app is a catalog with search and category filters (Gifts, Bouquets, Gypsophila, Lilies), an express delivery block and products with prices and the florist’s city.

The bouquet card shows a large photo, the name, dimensions (height and width), price, delivery address and time, composition and an add-to-cart button. The catalog updates automatically: a bouquet missing the components it needs is hidden from the listing.

FlowDelivery catalog layout with an Other products grid and the Morning dew bouquet card with composition and delivery timeFlowDelivery catalog layout with an Other products grid and the Morning dew bouquet card with composition and delivery time

Viewing and choosing a bouquet

The same screen shows the full catalog layout: express delivery, “Other products” as a tile grid with prices, and a detailed card for the selected bouquet, “Morning dew”, with its composition (pistachio foliage, cymbidium and other components), price and a delivery time of about 45 minutes.

A photo gallery of the bouquet with a swipe indicator helps customers look at the product closely before adding it to the cart.

Cart, checkout and confirmation

An order takes three steps. The cart collects the selected bouquets with quantities and the total. At checkout the customer enters the recipient’s phone number, the delivery address and the payment method (cash on delivery) and sees the delivery cost and a delivery time of 35–40 minutes.

The final “Order accepted” screen confirms the order: a manager will contact the customer shortly.

One data model, catalog reliability and personal data

The value of discovery lies in a consistent data model: the bouquet catalog, components and stock are described so that availability is recalculated automatically, and customers never see a bouquet that cannot be assembled.

The prototypes and documentation cover both apps and the key scenarios, which reduces risk during development. Removing the redundant feature and moving to a simpler architecture further cut the future budget and timeline without any loss of functionality.

The discovery also covered the architecture for storing and processing users’ personal data (name, phone number, delivery address). The model keeps data stored locally and limits it to a minimal set of fields, following the data minimization principle.

Both apps are designed for personal data to be processed under the requirements of the client’s jurisdiction: user consent to processing, a privacy policy and storage on locally hosted servers, with role-restricted access. The client acts as the data controller.

By the numbers

2products designed in one discovery
1single data model for both apps
3 stepscustomer journey: cart → checkout → confirmation
-1redundant feature dropped to save budget and time

2 products designed in one discovery: a customer app and a florist app.

One data model: the bouquet catalog, components and stock are a shared source for both apps.

Bouquet auto-hiding logic for missing components, designed without an additional service.

A range management tool: stock control with automatic recalculation of available items.

An optimized architecture: a costly redundant feature was removed at the design stage.

A complete package of documentation and prototypes, sufficient for handover to development without a repeat briefing.

Frequently asked questions

What is a discovery phase in mobile app development?

Discovery is the product design stage before development starts: interviews with the client, analysis of user scenarios, architecture and interface design, prototypes and technical documentation. The result is a clear specification and prototypes that let development start right away. This lowers risk and the cost of changes compared with starting without design.

What does the client get at the end of discovery?

The client gets a description of user scenarios (user stories), an architecture diagram of the apps and the data model, clickable prototypes of the key screens, a specification for the development team, and an assessment of complexity and risks. This package lets development start without briefing the developers all over again.

How is the availability logic for bouquets and components designed?

The FlowDelivery discovery produced one model: every bouquet consists of components (flowers, greenery, packaging), and each component has a stock level. If any component runs short, the bouquet is automatically hidden from the customer catalog. Florists manage stock in the internal app, and every change is immediately reflected in what customers can order. This approach rules out orders for items that are not available.

How does discovery help save the development budget?

The cost of fixing an architectural mistake grows with every development stage. During discovery a fix takes hours and costs very little; once development has started it takes days and refactoring; after release it takes weeks and rework. In the FlowDelivery project a redundant feature that could have made development significantly more expensive was found and removed at the design stage. Discovery for two interconnected apps typically takes 3–6 weeks.

How long does mobile app discovery take?

It depends on the number of apps, the complexity of the business logic and the client’s availability for sync meetings. The typical range is 2–4 weeks for one app and 3–6 weeks for two interconnected apps with a shared data model. This is not a guarantee for a specific project: the actual timeline is agreed at the briefing.

Trusted by product teams across the US and Europe

Companies from retail, medtech, logistics and e-commerce that we helped build digital products.

SuperStep logo
Unilab logo
Plonq logo
Galamart logo
GROM Security logo
Move2Armenia logo
Moscow Windows logo
Fork & Spoon logo
Konga logo
xRouten logo
REHAU logo
AIS logo

YuSMP Group development services

The full spectrum of development — from native mobile apps to web platforms, AI and cloud. Pick a direction or order a turnkey project.

Mobile App Development

Native iOS & Android plus cross-platform Flutter and React Native — from MVPs to apps with millions of installs.

Learn more

iOS Development

Native Swift / SwiftUI iOS apps — with Apple Pay, Sign in with Apple, App Store Connect deployment pipelines.

Learn more

Android Development

Native Kotlin / Jetpack Compose Android apps — Material 3, Google Play release pipelines, Firebase integration.

Learn more

Flutter Development

Single Dart codebase across iOS, Android, web and desktop — with native modules where needed.

Learn more

Web Application Development

Production web apps on React, Next.js, Vue and Node — SaaS dashboards, B2B portals, marketing-conversion stacks.

Learn more

API Development Services

REST, GraphQL and gRPC APIs — designed for partners, mobile clients and internal microservices.

Learn more

Custom Software Development

Bespoke platforms for mid-market and enterprise teams — internal tools, vertical SaaS, mission-critical backends. Discovery to launch in 12–36 weeks.

Learn more

MVP Development

Focused MVPs in 12–20 weeks — one or two integrations, real users on day one, telemetry built-in.

Learn more

Product Engineering

End-to-end ownership of a digital product — design, build, ship and continuous evolution.

Learn more

AI Agents Development

Tool-using agents that plan, retrieve, act and self-evaluate — in customer service, ops automation, internal copilots.

Learn more

Cloud & DevOps

AWS, Azure and GCP architecture, Kubernetes, Terraform/Pulumi, CI/CD and observability — SRE-grade operations for product teams.

Learn more

Technical SEO & Growth

Technical SEO, Core Web Vitals, structured data, internal-link architecture — built into your engineering process.

Learn more

Planning a delivery or e-commerce app? Start with discovery — talk to us

Tell us about your products, stock and ordering process, and we will help you design the apps, the data model and the prototypes before development starts. Let’s discuss how a similar discovery could work for your business.

Get a proposal

Share a few details and a senior consultant will reply within one business day.

Free project estimate — we’ll come back with a plan within 1–2 business days.
  • Requirements review and tech-stack recommendations
  • Estimate of timeline, budget and team composition
  • No commitment — just a clear plan

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)

— required fields