One squad, one screen — and everybody sees the same thing.

Ship a team app your squad actually opens on a Saturday: 21 finished screens, a fixture-to-season loop that works end to end on day one, and live updates across every phone on a Firebase project you own. Light and dark themes, GetX architecture, offline documentation, and a commented security-rules file with 50 assertions you can run yourself.

Demo Instructions — the sign-in screen is a mock and contacts no server, so any credentials are accepted. Use demo@rostora.app / demo1234, or simply tap Sign in with both fields left empty. There is no account to register, no Firebase project to create and no network required: Demo Mode is on out of the box, so every screen works on the device with a sample squad of eighteen. Onboarding has a Skip in the corner.

Rostora — Flutter Sports Team Management App: one squad, one screen

Why this one

Live across the squad on day one: one person answers a fixture and every other phone changes — Firebase Authentication and Cloud Firestore, on a project you own.
Tested, not just screenshotted: 104 tests pass, and 50 security-rule assertions run against Google’s own Firestore emulator with one npm command.
Your colours in an afternoon: every colour, radius and type token lives in one file, and the bundled documentation walks through re-skinning from it.

Demo Mode, light and dark

Every screen works before Firebase is configured. The sample team pins “today” to its own date, which is why the screenshots, the live preview and the tests all agree with each other, and nothing is written to disk while Demo Mode is on.

flutter pub get
flutter run

Demo Mode, light and dark — every screen works with no Firebase project and no account

Who is about on Saturday?

One tap for going or out, and the whole squad sees it. Rows are players, columns are the next fixtures, and every cell is one of three stamps: a filled tick for going, an outlined cross for out, a dotted question mark for nobody having answered. Your own row is pinned to the top and outlined in the brand colour, and tapping your own cell cycles your answer. You cannot tap anybody else’s — and neither can the captain, which is enforced in the security rules rather than only in the interface.

No maybe column. The third state is nobody having answered, which is the only one a captain can act on. The summary under the board counts the whole squad — 12 going, 3 out, 3 no answer — so the three numbers always add up to the roster above them.

The availability board: eighteen players against the next five fixtures, three stamps per cell

Shirts on a pitch, not cells in a grid

Tap an empty shirt and the players who said they are going are listed first. Publish, and every phone in the squad shows that player their position. Football 11, 7 and 5-a-side, futsal and basketball each come with their own drawn pitch and their own formations — 4-3-3, 4-4-2, 3-5-2, 2-3-1, 1-2-1, starting five. Volleyball and “other” get a named list instead, because a rectangle with six dots on it is a diagram nobody reads.

The line-up board: a drafted 4-3-3 beside the same line-up published to the squad

The match, as it happens

The captain logs a goal, a card or a substitution and every phone watching updates. Events sit on a horizontal band — ours above the line, theirs below.

Nothing here runs a clock. The minute is typed in, because the person keeping the record is also watching the game, and a timer started four minutes late is wrong for the whole match and then keeps running through half time. The score is counted from the goals, never typed in — so deleting one that was logged twice puts the scoreboard right again.

The match center: a scoreboard, a horizontal event band, and the sheet for logging an event

Notices and polls, instead of a group chat

A pinned notice at the top, then the questions the club is asking. Votes are shown as the people who cast them, one initials chip each, yours ringed. A team of eighteen does not want a percentage bar — it wants to know whether Ade is one of the six.

Pin what must not scroll away
Two to five answers, change your vote any time
An optional closing time, and it closes
Notices and polls only — this app replaces a group chat rather than reproducing one

The board: a pinned notice, and a poll whose votes are shown as the people who cast them

The season, from what was recorded

Appearances, goals, assists, cards and reply rates are recomputed from the fixtures, answers and match events every time they are read. Nothing is stored as a running total, so deleting a fixture corrects the table.

Three places it refuses to invent a number: no matches played yet gives you the date of the first one rather than a column of zeros; a player who joined after the last fixture has no reply rate rather than nought per cent; an unpublished line-up says so rather than showing an empty pitch.

The season screen: the record, and appearance, goal, assist and reply-rate tables

There is no server belonging to us

Connect your own Firebase project and the same app becomes a shared, live one: your squad, your project, your account, your billing. Email and password sign-in, plus anonymous sign-in for the team-mate who was handed a code in a car park and has not signed up yet — with an upgrade that links a password to the same account, so nobody loses their place in the squad by signing up late.

firestore.rules ships commented rule by rule: membership is a document, captains and coaches write fixtures and line-ups, and your answer to a fixture can only ever be written by you. 50 security-rule assertions ship with it, in a harness that runs them against Google’s own Firestore emulator with npm test. 0 composite indexes to deploy, and about 10 minutes from a new project to a live squad.

The invite code sheet, and the settings screen showing which store the app is running on

Built for developers

Clean GetX architecture: View, Controller, Service and Model, with a lazy binding per route.
One repository interface, two implementations: FirestoreTeamRepository for live data, LocalTeamRepository for Demo Mode — the screens talk to neither directly.
One colour file: app_colors.dart holds every colour the app uses, and the documentation has a re-skinning chapter built around it.
Rules and their harness ship together: firestore.rules commented rule by rule, and firestore_tests/ runs its 50 assertions on the emulator with npm test.
Eight dependencies and no vendor SDKs: flutter analyze reports zero issues.

What you get

21 screens and 9 sheets, light and dark, GetX, Material 3
8 dependencies, and no vendor SDKs; flutter analyze reports zero issues
104 tests, all passing — the season engine, the invite-code alphabet, the backup round trip and colour-contrast measurements of every text-on-fill pair in both themes
50 security-rule assertions on the emulator, in a harness you can run
Backup and restore: every team as one JSON file through the share sheet, and a round trip is byte-identical
Offline HTML documentation, 20 chapters, with a re-skinning guide and a glossary of every terminal command it asks you to run
Three bundled typefaces under the SIL Open Font License 1.1 — nothing is downloaded at run time

What you get: 21 screens, 8 dependencies, 104 tests, 50 rule assertions

Requirements

Flutter SDK 3.29 or newer, Dart 3.7+, Android Studio or VS Code. Android and iOS. A Firebase project is optional — the app is complete without one.

Support

Questions about setup, Firebase or re-skinning are answered through the item’s comments. Item support covers the template itself; it does not cover your Firebase project’s own account, quota or billing.

Notes

Third-party services and external costs: Rostora runs on bundled sample data out of the box. Connecting it to a live back end — a Firebase project of your own, with Authentication and Cloud Firestore — will involve those third-party services, which will incur their own separate costs and are not part of this item; quotas, billing and any pricing change are Google’s and yours, and the documentation works the numbers through for a 25-person squad on the free plan. Push notification delivery is not wired in this version: the app obtains a Cloud Messaging token, and sending a message needs a sender, which needs a server, so the app marks fixtures nobody has answered instead. Photographs are outside the scope of this version — avatars, crest uploads and match photos would need Firebase Storage, which is not on the free plan, so initials and a drawn pennant are used instead. Chat and private messages are not part of this item; notices and polls cover the same ground. Subscription collection, match fees and payments are not wired in either, and the upgrade screen is a mock that contacts no store and charges nothing. Leagues, tables across clubs, external fixture or score feeds and video are outside the scope of one team’s own app. Google, Apple and phone-number sign-in are documented as add-ons rather than shipped half-configured.

Rostora | Flutter Sports Team Management App with Firebase