Let people try the tracker first.
The browser-only workspace gives visitors a way to log tickets without creating an account. The interface states where records are saved and provides a separate path to account tracking.
Independent project · Web application
FL ScratchOffs. Data website & personal tracker.
A searchable public information site and a personal record-keeping tool, with separate places to browse data and review entered records.
- Relationship
- Independent application
- Focus
- Data, history & reporting
- Role
- Design & development
Two tasks, with a clear distinction.
Browsing published information and reviewing personal records answer different questions. We designed and developed the public interface and tracker to give each task a place.
Search, detailed records, entry screens, and summaries connect without treating them as interchangeable views. This case study examines the software and interface, rather than recommendations about buying tickets.
What the application brings together.
Public data views, personal entries, editable history, and summaries connected to records.
The personal tracker
The full cost, in one view.
Fictional demonstration records: three tickets, $35 spent, $5 returned, and a $30 net loss. The dashboard keeps the total and ticket-by-ticket trend together.
A short form. A searchable history.
The Track view combines ticket entry with searchable history and edit controls. All tickets shown were created for this case study in the browser-only workspace.
Searchable public information.
A catalogue and detailed views organize game information, with filters, source context, and observation dates.
Supporting information for each record.
Website capture from October 5, 2026. Public figures reflect that dated snapshot.
Data needs context.
Published odds, reported prize counts, observation dates, and comparison scores describe different things. Methodology notes explain the limits; scores are not validated forecasts or probabilities of a future win.
Browse the Public Information (new tab)The choices behind the interface.
Each view has a task, and the interface explains what the information means.
Show spending beside winnings.
A prize on one ticket does not tell the whole story. The dashboard puts spending, returns, and the net result together, with a chart that follows each recorded ticket.
Keep the supporting data within reach.
Search, price filters, and game pages let visitors move from a broad comparison to the details behind an individual game.
Make the limits of the data visible.
Observation dates and methodology notes sit beside the comparisons. Published odds, remaining prizes, and model scores are explained as different measures; a score is not a win probability.
What this project demonstrates.
Structured information, filters, entry screens, editable history, and summary views in a browser application. The documented interface separates browser-local records from the account path; it does not promise automatic synchronization of all records.
A customer portal, job dashboard, or record-management tool needs its own scope and access rules. This project shows relevant interface and development work.
Explore Custom ApplicationsHave information that needs a better system?
Tell us what people need to enter, find, review, or keep track of. We will define the screens and workflow around that task.
Discuss Your Application
The initial conversation is free. Scope and pricing are agreed before paid work begins.