Retail, Commerce & Consumer Brands · Native Mobile Apps and the Consumer Commerce Backend
Native Mobile Apps and the Consumer Commerce Backend
Embedding across mobile, QA, and backend teams to keep brand experiences coherent at scale
The Client · A global athletic apparel and footwear brand
Overview
A global athletic apparel and footwear brand engaged Taller to embed engineering capacity across its native mobile apps, quality-assurance practice, and consumer-app backend.
The Problem
The client’s consumer apps (its fitness app and running app) were where the brand and the athlete met day to day. Its B2B platform served the wholesale channel, reaching millions of customers across nineteen languages on Android and iOS. With this many features, locales, and platforms, engineering coherence was what decided whether the apps felt like one brand or a scattering of disconnected products, and coherence at that scale took sustained, pod-level ownership inside the client’s release pipeline, not one-off project handoffs. That was the commitment the client brought Taller in to provide.
The Solution
Taller worked across the entire stack behind these apps to keep them fast, stable, and on-brand. On the backend (a Java and Spring Boot spine running on Amazon Web Services), Taller engineers built and maintained the microservices that powered the apps, strengthening the high-throughput data stores, real-time streaming, and behind-the-scenes processing that kept everything responsive under heavy load, and automating deployment so new work shipped reliably. On the front end, they developed the native iOS (Swift) and Android (Kotlin) apps themselves.
The clearest mark of Taller’s ownership was in quality engineering: rather than testing from the outside, Taller’s QA engineers were embedded directly in the client’s production release pipeline, managing the app-store release consoles, running experiment-aware tests behind feature flags, validating that analytics fired correctly, monitoring crashes, and doing the network-level debugging that told a genuine production bug apart from a test-environment fluke. This was what kept release quality high across so many features, languages, and devices. Taller engineers also worked inside the client’s own named squads, including a North America capacity team.
The Impact
Taller’s mobile QA engineers operated within the client’s release cadence, not alongside it. The recognition pattern across the engagement (client-issued spot bonuses, internal recognition awards, and Taller engineers earning advancement into senior roles within the client’s structure) marked this out as a long-tenure managed practice rather than a staff-augmentation arrangement.
