Connect4Sports

The brief

A sports community that wanted two things in one app: a place for members to post and follow each other, and a shop selling kit and bookings alongside it. Those are usually two products with two different rhythms — a feed is read constantly and a checkout is used rarely — and putting them behind one navigation without one swallowing the other was the interesting part.

My part

Flutter development on the client, against a REST backend built by the team. Feed, profiles, product listing and the checkout path, on Android and iOS from one codebase.

Decisions

The feed is the app; the shop is a destination. The commerce section is reachable in one tap and never interrupts the feed. An app that opens on a storefront teaches people to stop opening it.

Clean architecture, because the scope was known to be moving. Two product areas that grow at different rates share a codebase for years; keeping the feature boundaries strict is what let each be changed without regression tests firing in the other.