Rostora | Flutter Sports Team Management App with Firebase

Rostora 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 [email protected] / 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.Why Rostora oneRostora 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.Rostora  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 runWho 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.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 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.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.