Lumintik
All case studies

Reliability

How we solved it with FUTTEM

Mobile app in production, Colombia.

Client
FUTTEM
Country
Colombia
Sector
Sports
FUTTEM call ups on the Apple Watch

The problem

An app in production with real users that could not stop every time something changed.

The solution

Three separate environments, controlled deployments and end to end tracing.

Why it worked

The app is live on the App Store and Google Play, with a widget and Apple Watch, and every change goes through three environments (testing, QA and production) with end to end traces before it reaches the players.

In numbers

3
isolated environments: testing, QA and production
3
platforms: iOS, Android and Apple Watch
1.2.2
version published on the stores

Verifiable in the code and on the app stores, September 2026.

The app, on the staging environment

Real screens from the staging build with a test account: the environment the team checks before every production release. Hover to pause, or pick a stop on the rail.

Tools

  • AWS
  • NestJS
  • Flutter
  • PostgreSQL
  • Socket.IO
  • Firebase
  • OpenTelemetry
  • PostHog

Project images

  • A club screen with its squad and upcoming matches
  • A match in detail: pitch, time, spots and cost
  • The players called up split into two teams, with the waiting list
  • Training, fitness and promotional videos
  • The form to call a new match

Facing a similar problem?

Tell us what you need. We review your case and reply by email.

Next case studyHow we solved it with EZDocuAI

Get a Quote

Complete the form and discover how we can help you achieve your growth goals with custom solutions.