Product design · Flutter engineering2026Project world

SquadTactics Pro

Matchday control, without the chaos.

A bilingual football operations platform that connects coaches and players across lineups, fixtures, contracts, training, live match events, and post-match reporting.

My roleEnd-to-end product design and mobile engineering
Tactical replay01 / 11
SquadTactics Pro football management mobile app, screen 1

Use arrow keys · swipe on touch · tap the screen rail

Match intelligence

The system behind matchday.

Audience

Coaches, players, and football staff working before, during, and after a match.

Delivered scope

Mobile product strategy, bilingual UX, Flutter architecture, Firebase data, and live-match workflows.

Defining constraint

Match actions must stay fast and recoverable even when connectivity or attention is limited.

02Role journeys

Coach and player experiences share one system while exposing different decisions.

06Formation models

Six tactical structures drive the same reusable lineup engine.

11Starting positions

A full starting XI can be assigned, swapped, and validated before kickoff.

Verified evidence · These figures describe implemented product scope, not estimated business uplift.

01 / Opposition

Read the chaos before kickoff.

Football teams jump between chats, spreadsheets, and memory. The product needed to keep sensitive match decisions quick while giving every role only what it needs.

02 / Position

Owning the full touchline system.

End-to-end product design and mobile engineering

03 / Game plan

Tactical calls that shaped the product.

  1. 01

    Separated coach and player journeys without splitting the visual language.

  2. 02

    Designed the lineup builder around fast formation changes and safe player swaps.

  3. 03

    Added a confirmation layer before match data becomes permanent.

  4. 04

    Built responsive light, dark, English, and Arabic experiences from one system.

System architecture

One match, three connected operating layers.

The design system follows football operations instead of treating every feature as a separate screen.

01

Prepare

Fixtures, availability, roster status, contracts, and lineup selection establish match context.

02

Operate

Periods, goals, substitutions, added time, and player minutes remain usable under pressure.

03

Remember

The confirmed report turns live events into player history and team records.

04 / Match plan · SDLC

Four phases. One coordinated XI.

01

Map the team

Defined coach, player, matchday, and ownership responsibilities before shaping screens.

02

Model the match

Connected fixtures, lineups, live events, contracts, and reports as one product system.

03

Build the rhythm

Created reusable Flutter flows with fast feedback and a consistent tactical language.

04

Test the edges

Pressure-tested swaps, permissions, confirmations, localization, and real-device behavior.

05 / Full time

A coherent working product spanning pre-match planning, live operations, team communication, and player records rather than a collection of disconnected screens.

Next validationThe next validation step is a timed matchday test with coaches using the app under poor connectivity.
FlutterRiverpodGoRouterFirebaseFigma