Sport shoes and CCC retailer logo

Mobile Facade for the Leading Retailer and E-commerce Group

Neontri consolidated complex backend management, like multiple system versions, secure mTLS authentication, and dynamic scalability, into one standardized API for mobile apps.

light gray lines
CCC Group financial stats

Client: CCC Group – e-commerce leader in Central and Eastern Europe, running ~1,200 stores across 23 countries under multiple brands

Industry: Retail / E-commerce

Scope: Designing and delivering a standardized Mobile API Facade that unifies backend access for CCC’s mobile apps across multiple brands and systems

Key technologies: Google Cloud Platform (GKE, Cloud SQL, Cloud Load Balancing, Cloud KMS, Memorystore), Kotlin, mTLS

Timeline: 3 months

Challenge

CCC, the leading omnichannel footwear and fashion retailer, needed a standardized API for its mobile apps. Given the client’s huge sales network operating in 23 countries, the solution had to work across multiple brands and backend systems without extra engineering for every individual app.

Delivering that meant solving two core problems:

  • Ensuring the solution could handle complex backend logic without slowing down the mobile apps that depend on it.
  • Developing a standardized, unified programming interface that could seamlessly integrate with various backends without any additional adjustments.

Solution

Our team developed the Mobile Facade – a programming interface that sits between CCC’s mobile apps and its backend systems. By hiding server-side complexity behind a unified layer, the facade allows developers to:

  • Execute custom logic to select the appropriate infrastructure based on the system’s configuration.
  • Use a single interface for integrating changes, regardless of the number of backend versions and standards.
Fatures of Mobile API Facade

Faster releases without new app versions

A standardized API allows the development team to update the backend systems without launching a new version of mobile apps every time. This enables a clean split of responsibilities: developers focus on user experiences while the Mobile Facade handles backend integrations and updates.

One interface across multiple backends

The Mobile Facade consolidates data and functionalities from different sources into a single, unified API. Since backend versions are managed centrally, every application always receives consistent, aggregated data.

Scaling without performance loss

By leveraging advanced technologies such as dynamic load balancing and auto-scaling, the backend can adapt seamlessly to changing demands. This approach allows mobile apps to maintain optimal performance even during traffic spikes and guarantees that services remain reliable under all conditions.

Security built into every exchange

Every data exchange between mobile app and backend is protected by the mTLS protocol, which utilizes certificates for mutual authentication. This ensures all connections are encrypted and only verified users can access sensitive data. Client certificate-based authorization and internal JWT token exchange between services add an additional layer, securing communication between system components.

purple abstract shapes

Looking for a solution to streamline your backend architecture?

Delivery approach

The project moved through six stages, split between Neontri’s and CCC’s development teams:

Neontri:

  • Analysis: reviewing requirements and defining scope.
  • Design: planning a microservices architecture focusing on observability and a well-thought-out division of services.
  • Core feature development: built on Google Cloud Platform (GCP) using a cloud-native approach to seamlessly integrate multiple Android and iOS applications through a single, unified interface. 
  • Implementation of security features: adding secure authorization and authentication layers.

CCC:

Testing: validating the solution before live release.

Integration: connecting the API interface with CCC’s existing applications.

Mobile API Facade development process

Working closely with the CCC team, we delivered the complete solution in three months using Agile methodologies, iterative development cycles, SOLID principles, and Test-Driven Development (TDD). The delivery included comprehensive technical documentation to simplify handoff and integration on the client’s side.

Results

The Mobile Facade reduced the risk of integration problems stemming from different backend systems. All updates, including new API versions, can now roll out without forcing a new mobile app release, shortening the path from backend change to live feature.

For a business running ~90 platforms across 23 countries, that consolidation matters. Mobile teams now work against one interface instead of maintaining separate integration logic for each app, while the Mobile Facade manages which backend version and infrastructure route handles each request.

Technology used for Mobile API Facade solution

Technology:

  • Google Kubernetes Engine for logic, security, gateway, and matter components. 
  • Cloud SQL, Cloud Load Balancing, Cloud Key Management, and Memorystore for caching
  • Kotlin for solution development

Security:

  • At-rest and in-transit encryption using mTLS
  • Certificates generated per standard practice (Certificate Signing Requests, PKCS #10)
  • Access limited via Certificate Revocation Lists (CRL)
  • TLS 1.3 with AEAD-compliant algorithms
  • Data encrypted at rest using AES-256
A woman is checking her email box

Want to upgrade your systems without operational risk?

From architecture to security to rollout, we guide retail and e-commerce businesses through modernizing their systems without disrupting existing apps.

Our solution engineering process

  • 01

    Analysis

    The client’s existing systems and requirements are reviewed to define the solution’s scope, ensuring every decision aligns with the operational outcomes before engineering begins.

  • 02

    Design

    A scalable blueprint is created to define how the solution will function, mapping out data flows and ensuring seamless compatibility within the client’s IT ecosystem.

  • 03

    Development

    We build the core logic and custom functionality using proven frameworks and modern coding standards, prioritizing security and rapid deployment cycles.

  • 04

    Implementation

    The solution is deployed directly into the designated environment, with the necessary pipelines and base configurations set up for operational readiness.

  • 05

    Testing

    An end-to-end user acceptance testing (UAT) process validates the solution across business scenarios, confirming reliability and performance before final go-live.

Written by
A young woman

Dorota Jasińska

Content Specialist
Maciek

Maciej Stępień

CEO and co-founder
Share it

Get in touch with us!

    Files *

    By submitting this request, you are accepting our privacy policy terms and allowing Neontri to contact you.