
Full-Stack Developer to Stabilise Football Web App (React
- or -
Post a project like this- Posted:
- Proposals: 86
- Remote
- #4529669
- OPPORTUNITY
- Open for Proposals











Description
BEGIN YOUR PROPOSAL WITH THE WORD "ANFIELD". Then state your fixed price, timescale and how you would test.
WHAT M1 DELIVERS
1. Working sign-in: users open the app and start without a login screen (for example Supabase anonymous sign-in), each with their own protected data.
2. Match controls and football clock: one slim row - FIRST HALF START/STOP | SECOND HALF START/STOP | PAUSE/RESUME. A personal clock per user, calculated from server timestamps so it stays exact through refreshes: 00:00-45+ and 45:00-90+, including added time. Pause freezes the display; resume shows the real elapsed match time. No automatic jump to results at 90.
3. Notes: each voice or typed observation saved as its own note, stamped with the match minute when it began, shown in chronological order (newest at the bottom), with no duplicates and no silent failures.
4. Speech-to-text: continuous voice input (browser Web Speech API) alongside typing in both boxes - pre-match preview and live notebook - without voice overwriting typed text. Automatic restart after interruptions, clear microphone permission steps, a Retry button, and the microphone shuts down properly.
5. Recovery: notes saved locally first and synced afterwards, so a page refresh or Wi-Fi drop never loses or duplicates anything.
6. Interface: match the approved design reference - prominent stadium, compact control row, small white pre-match box, larger white live notebook (black text). No extra cards or admin clutter.
7. Basic security hygiene needed for the above (no self-promotion to admin, notes locked after saving, input validation), plus lint errors and the one vulnerable dependency fixed.
ACCEPTANCE: seven tests - Start/Sync Kickoff, New Match, Voice and Typed Observations, Microphone Permissions, Refresh and Wi-Fi Interruption, Visual Acceptance, Match Controls and Clock - all demonstrated, including extended speech with natural pauses, football terms and player names.
DELIVERY: a live working preview; the source code as a GitHub repository transferred to me; migration files with short setup instructions; a note of any remaining limitations. Main test browser is desktop Chrome, plus a basic tablet check. Full mobile testing is not required.
NOT IN M1: server-side scoring, leaderboards, Fan League, user accounts, privacy/legal pages, paid speech services. These come later.
BUDGET AND TIMING: $500 fixed price, delivery within about one week.
LONGER TERM: Couch Coach is intended to grow into a commercial football product. If M1 goes well, there may be scope for a longer relationship, including a more entrepreneurial role, to be discussed separately and not assumed. Please briefly say whether that would interest you.
The source code and design reference will be shared with shortlisted applicants.
Seamus K.
0% (0)New Proposal
Create an account now and send a proposal now to get this project.
Sign upClarification Board Ask a Question
-

Should each user be able to run only one live match at a time in Milestone 1, or must the app support several concurrent matches?
-

-/ Should anonymous users retain their match history across browser sessions, or is cross-device recovery also expected?
-/ For kickoff synchronisation, should users manually adjust the clock to match a live football broadcast, or should it always start from their own kickoff action?
-/ Once observations are saved, should they become permanently read-only, or should users have a short window to correct transcription errors?
-

1. Is the current Supabase database schema and Bolt.new source code ready for review?
2. Should match clock state and note timestamps be persisted through Supabase for cross device consistency? -

1. Could you share the design reference so I can review the existing implementation and identify the main areas that need stabilisation?
2. Is the current Supabase database structure already in place, or will M1 require new tables and migrations?
