Case study

CLIKA. Fresh games for every gathering.

CLIKA's card games are played at real gatherings across MENA. We built an AWS platform for seasonal traffic peaks, live play across phones and an AI-assisted content operation, alongside rebuilt iOS and Android apps.

Practice AWS Cloud · DevOps Engagement Platform build · social gaming · mobile apps
Validated load profile
4×
Peak-load testing covered Ramadan and match-night demand profiles.
Rebuilt apps
2
iOS and Android with an Arabic-first experience.
Proof of concept
6 weeks
Content quality, anti-repetition and live rooms tested together.
Availability target
99.9%
Monthly platform objective, not a reported uptime measurement.
The brief

Growth put pressure on both the platform and the cards.

Games for gatherings face concentrated demand around evenings, match nights and seasonal events. The platform had to absorb those bursts without carrying peak capacity all day.

Fresh content was a separate constraint. Cards needed to work in Arabic and English, suit the audience and avoid repeating what a group had already seen. Publishing a new deck could not depend on shipping another app release.

What we did

Scale play and content independently.

Separate live rooms from the content workload

WebSocket rooms keep cards, votes and scores in sync across players' phones. Queued content jobs and elastic ECS Fargate services handle generation and core game traffic independently.

Review generated cards before publication

Amazon Bedrock generates candidate cards and supports cultural and quality checks. Human approval in the CMS remains the publication gate, giving the content team control over what reaches players.

Remember what a group has already played

Per-player and per-group history works alongside semantic duplicate detection. The system checks both previously served cards and questions that repeat the same idea in different wording.

Release decks without waiting for the app stores

Content packs are delivered through CloudFront, and the CMS publishes reviewed decks separately from app releases. Infrastructure code, pipelines and runbooks give CLIKA's team control over changes.

The outcome

A platform and a content operation ready to grow.

The engagement delivered rebuilt mobile apps, live multi-device rooms and a reviewed content workflow. A six-week proof of concept validated the difficult paths, and testing covered a four-times peak-load profile.

Performance and service objectives remain explicit: API latency below 300 ms at the 95th percentile, 99.9% monthly availability and fewer than one repeated card in 500 within a group's history window. These targets are separate from the completed load-test result.

The brief

The person you brief is the person who solves it.

One conversation · 30 minutes · no monologue