Mobile App Specification: Fixtures, Results, and Ladder Views #7
Description
Overview
This mobile app presents a sports tournament interface for users to browse events, fixtures, results, and ladder standings across various divisions.
Sections
1. Home Page: News Feed
- Top Menu Bar: Permanent, expandable navigation across sections.
- Scrolling News Feed: Lists news items like articles, announcements, or featured stories.
2. Competitions and Results Section
- Event Grid View: Large tiles, each representing a competition event with logo.
- Navigation: Clicking a tile opens the event details view.
3. Event Detail: Season Selection
- If the event includes multiple seasons, prompt user to select a year.
4. Division Selection View
- Lists all divisions within the selected event/year (e.g. Men’s Open, Women’s 40s).
- Each tile is labeled and optionally color-coded.
5. Fixtures and Results View
- Shows fixtures for selected division.
- Displays match cards:
- Teams, time, field.
- Result (when available).
- Example format:
Team A vs Team B - 3:00 PM - Field 1.
6. Ladder View (New Feature)
- Toggle option from the Fixtures view.
- Display current standings within the division.
- Fields:
- Team name
- Matches played (P)
- Wins (W), Draws (D), Losses (L)
- Points (Pts), Goal Difference (GD)
Example Ladder Entry
| Team | P | W | D | L | Pts | GD |
|---|---|---|---|---|---|---|
| ThunderCats | 3 | 3 | 0 | 0 | 9 | +12 |
| StormBreakers | 3 | 2 | 0 | 1 | 6 | +5 |
Navigation Flow Summary
- Home → Competitions → Event → Year → Division → Fixtures ⟷ Ladder
Notes
- The ladder should update in real time as results are entered.
- Users should be able to easily switch between Fixtures and Ladder view using a tabbed interface or segmented control.
Given the above specification, produce a functional prototype (stub out REST API calls, use static data) of this application.
It should be implemented using the Flutter framework for cross platform delivery from a common code base, adhere to language best practices, follow idioms, and be built using the most modern version available.
It must also include GitHub Actions workflows for validation of the build process, and produce artefacts that can be retrieved for testing on actual devices (iOS, iPadOS, and Android).