Random App Attack #3: Field Frenzy

Loaded SRC_URL

https://producingtechnology.com/65-apps/okeolamide_180348_15200412_ooo38_field-frenzy.html

The browser tab title is simply "Field Frenzy." The app presents itself as Spring Field Frenzy, dated Atlanta, GA · April 18, 2026.

App Behavior Summary

Field Frenzy is a live scoreboard for school-style field day or house cup competitions — think Hogwarts houses racking up points across a day of events. The default state ships with Red House and Blue House head-to-head, and the app is genuinely interactive (unlike the typical AI-generated mock).

The layout is arcade-inspired: a dark grid background with neon green headline type, and the following real, working controls:

• House panels — Each house gets a large tinted score number, a POINTS label, and four scoring buttons (+1, +5, +10, -1). All four buttons actually mutate the score live.
• Crown indicator — A 👑 emoji floats above the currently-leading house and moves as the lead changes.
• Leaderboard — Horizontal bar chart showing each house's points in its house color.
• + Add House — Opens a modal with a house-name input, a color swatch picker, and an optional starting-points field. Submitting adds a new, fully-functional score panel in real time.
• 🏆 Declare Winner, ↻ Reset Scores, ⟲ Reload JSON — Event-management controls at the bottom. Reset genuinely zeroes every house's score.
• Event Log — Timestamped audit trail of house-level events (e.g. 18:00:26 Loaded "Field Frenzy" from producingtechnology.com, 18:00:50 All scores reset to 0, 18:01:02 Added "111" to the scoreboard).

Notably, this is the most functional of the apps I've reviewed in this series — score state, new-house creation, reset, and the event log all actually work end-to-end in the browser without requiring a backend.

What Didn't Work as Expected

• No validation on house creation. I was able to add a house named 111 — the form accepts numbers-only, empty-ish, or arbitrarily long strings with no minimum length, uniqueness check, or trim-whitespace handling.
• You can add a house but you can't remove one. Once 111 was on the board, there was no delete affordance on the panel, no right-click, and no edit mode. The only way to get rid of it is a full reload.
• No edit-after-create. House name, color, and starting points are all locked at creation time. A typo in a house name is permanent for the event.
• Asymmetric increment/decrement buttons. Scoring offers +1 / +5 / +10 but only -1 for corrections. Fixing an accidental +10 click requires ten -1 taps — painful in a live event context.
• No undo, no confirmation on destructive actions. Reset Scores nukes every house's score instantly with no confirmation dialog and no undo. For a real event, one misclick wipes the day's tally.
• Event log is too coarse. Individual score changes (e.g. Red House +5 at 18:03:14) are not logged — only house-level lifecycle events are. This defeats the log's value as a scoring audit trail if a parent disputes the final total.
• "Declare Winner" is ambiguous. It's not obvious what this button does, what state it puts the app in, or whether it's reversible. There's no winner screen, no confetti, no end-of-event flow shown by default.
• "Reload JSON" is unexplained. The button reads like developer debug UI leaking into the user-facing product — where does the JSON live, what does reloading do, and why would a scorekeeper ever click it mid-event?
• The date is hardcoded. April 18, 2026 is baked into the page. For a reusable field-day scoreboard, the date and event title should be editable at event setup.
• No keyboard shortcuts. In a real frenzy, a scorekeeper wants to press R + 5 for Red +5, not hunt-and-click. The app is mouse-only.
• No fullscreen / presentation mode. This is a scoreboard — its highest-value view is on a projector or TV in the gym. There's no distraction-free fullscreen layout, no auto-hiding of admin controls.
• No persistence. The event log warns Loaded "Field Frenzy" from producingtechnology.com every page load, which implies a fresh start — a mid-event browser refresh appears to lose all live scoring state, a catastrophic failure mode for the use case.
• Leaderboard bar scaling is awkward with lopsided scores. With one house at 3 and two at 0, the 3-point bar spans the full width and the two 0-point bars are invisibly thin — no minimum bar width and no explicit empty-state styling.

Improvement Prompt

Harden Field Frenzy from a working prototype into something you could actually trust to run a school field day, without losing its arcade aesthetic. Specifically: (1) Add a one-time Event Setup screen (event title, date, venue, number of houses, default house colors) that persists to localStorage, so refreshes do not wipe state mid-event and the title/date/venue stop being hardcoded. (2) On every house panel, add a kebab menu with Rename, Recolor, and Delete house (with confirmation); enforce unique, non-empty, trimmed, length-capped house names at creation and rename time. (3) Make scoring symmetric: offer -1 / -5 / -10 alongside +1 / +5 / +10, and add a persistent Undo last score change button plus Cmd/Ctrl+Z shortcut. (4) Log every score delta to the Event Log with house name, delta, resulting total, and timestamp — this becomes the dispute-resolution audit trail. Add an Export CSV button for after-event records. (5) Gate Reset Scores behind a typed-confirmation dialog (type RESET to confirm) and offer Undo reset for 30 seconds via a toast. (6) Replace Declare Winner with a proper end-of-event flow: modal announcing 1st/2nd/3rd place, confetti, final leaderboard snapshot, and a shareable summary image. (7) Add keyboard shortcuts for power users: first letter of each house + number key (e.g. R then 5 = Red House +5, Shift+key for subtraction), with an on-screen legend behind a ? key. (8) Add a Presentation Mode toggle (fullscreen, large scores, auto-hide admin buttons) designed for projectors, and a subtle sound effect on score changes (mutable). (9) Replace the developer-facing Reload JSON button with either a clearly-labeled Load saved event picker or hide it behind an advanced/admin menu — it should not sit next to user-facing controls. (10) Fix the leaderboard bar scaling so 0-point bars render with a minimum visible width and show a — state, and so the scale rebases smoothly as new leaders emerge. (11) Preserve the neon-arcade visual language exactly — dark grid, glowing green headline, tinted house colors, crown indicator — any new controls should feel native to that aesthetic, not like generic admin UI bolted on top.