Malish — native iOS + Android local marketplace

The brief — take a multi-store retail chain online without breaking the floor

The Malish team came to us with a successful offline chain of children's-goods stores and a clear digital ambition: bring the assortment online without forcing parents to travel to a store with kids in tow, and reach demand beyond the walking radius of each location. The constraint was not aspirational; it was operational. The offline inventory operation works, the store staff knows the catalog, and the chain's competitive advantage is the assortment curation that earned its reputation. The digital surface had to extend that operation, not replace it — and could not introduce a stock-misalignment incident that breaks customer trust in either direction. The buyer profile spans US and EU consumer-retail patterns for similar chains expanding online: parents who research on the phone in the evening, expect predictable inventory accuracy, and re-purchase on a sub-30-second flow when the product is already known. SaaS marketplace platforms were eliminated because their vendor-defined inventory rules and integration constraints fight the chain's own assortment logic. A Flutter MVP was considered and de-prioritized because retail polish — system-native haptics, predictable accessibility, idiomatic platform behavior — is exactly where a children's-goods buyer notices the difference, and the trust premium on this category does not survive an uncanny-valley UI. The result is a native Swift iOS client, a native Kotlin Android client, a Symfony backend with a React admin panel, ElasticSearch-powered catalog, two-way inventory sync with the offline stores, and integrated delivery — all positioned for audiences across the US and EU under GDPR and CCPA expectations from launch.

By the numbers

A snapshot of what the Malish build delivered across native iOS, native Android, the Symfony admin, and the multi-store inventory sync in its first production cycle.

Delivery methodology

A five-phase build that took Malish from an offline-only retail chain to a native iOS + Android marketplace with a multi-store inventory sync and integrated delivery.

Launching across the United States and the European Union

Malish launched on Apple App Store and Google Play with storefronts active across the United States and the European Union for retail chains expanding online. The same architecture serves a multi-store children's-goods chain in California, New York, Texas, Florida, or Washington in the US, and in the Netherlands, Germany, France, Ireland, or Sweden in the EU, without per-region forks of the codebase. Consent flows are region-aware at the client layer: buyers from the EU and EEA receive a GDPR-style granular consent screen with separate toggles for any optional product analytics; buyers from California receive a CCPA-style "Do Not Sell or Share My Personal Information" disclosure in the same flow. Data-handling practices are aligned with GDPR for European users and with the US state-privacy patchwork — CCPA / CPRA (California), VCDPA (Virginia), CPA (Colorado), CTDPA (Connecticut), UCPA (Utah), TDPSA (Texas), and Oregon CPA. Because the data model minimizes personal data by design and explicitly does not solicit child-identifying information, regional compliance reduces to honest disclosure and a clean consent flow rather than per-jurisdiction data segregation.

Infrastructure rolled out across EU and US regions in parallel — Netherlands, Germany, France, Sweden, and Ireland for EU coverage; US East and US West for North America — so the apps serve both markets with low latency from launch. Both the App Store age rating and the Google Play content rating were calibrated for the children's-goods retail feature set, and the in-app privacy policy was drafted to document the architecture above, citing GDPR obligations and California CCPA obligations directly. The engineering team behind the build sits across CET and runs a CET workday with East-Coast US overlap (9 AM–1 PM ET) for stand-ups, store-review choreography, and incident response — the timezone that lets a US-based retail operator and an EU engineering team share four hours of live overlap every day. The marketplace serves US & EU audiences as one unified surface.

Tech stack and roadmap

The active custom software development roadmap for Malish includes a loyalty subsystem with per-store tiering and a parent-facing rewards wallet, a store-locator surface with real-time hours and pickup-window booking, an expanded delivery-zone model for cross-store fulfillment, and a wholesale tier for B2B customers in the US and EU childcare segment. A web companion surface is scoped as a phase-two extension — sharing the Symfony backend and the design-tokens spec with the native clients — to capture desktop research traffic without forcing parents off mobile. Infrastructure plans include further reconciliation-log automation, an internal stock-misalignment alerting harness, and a future independent readiness assessment scaffolded into the cloud & DevOps roadmap.

Build a marketplace like this — talk to us

If you are planning a native iOS + Android marketplace, a multi-store retail chain going online, or any consumer-retail product where the inventory sync and the platform polish both have to land together for audiences in the US and EU, we have shipped this stack end-to-end and can compress the build timeline meaningfully. The engineering team behind it sits inside YuSMP Group. We work fixed-price for well-scoped MVPs and on dedicated development teams for ongoing delivery, with a CET workday and a guaranteed East-Coast US overlap (9 AM–1 PM ET) window for stand-ups, demos, and incident response.

Share this case