EFY Streamer is a livestream player for sailboat and powerboat regattas, built around an interactive timeline. These are the rough tools for marking it. We want to know what confuses you, what you'd never use, and what's missing — before any of this gets built properly.
Nothing saves. No accounts. The three tools don't talk to each other. If something looks broken it may well be, and that's worth telling us.
Every number here goes down, not up. Judge the tools against that.
Fewer hours watched. Nobody should scrub through five hours of a livestream hunting for the moment two boats came together. The timeline takes you straight there.
Fewer thousands spent on editing. An organizer shouldn't need to hire an editor to get a highlight video. The material is already marked by the time everyone's ashore.
Fewer weeks waiting. Not a video that lands next month — one that's ready about an hour after coming off the water, in time for the debrief.
The debrief is the point. Within about an hour of coming ashore, someone stands in front of a room and talks through the day's racing. That hour is the whole constraint, and it's why the marking happens live rather than afterwards: because the racing went out live, the footage already exists and is ready to play back before the boats and the camera crew are off the water.
It puts the excitement of watching live and the convenience of a finished highlight video in the same place.
Three levels, and only one of them is required to be there.
Live moderation makes the experience considerably better, but it isn't required. Organizers and streamers are stretched thin on race day, so the timeline has to be worth watching with nobody moderating at all.
Four things that look like faults but are deliberate limits of a prototype.
Roughly fifteen minutes across all three. Do the viewer on a phone if you can — that's where it'll actually be used.
General reactions are welcome, but these change what gets built.
Anyone watching can mark the moment something happens — a port-starboard incident, a capsize, the leader rounding the windward mark. Those marks build the timeline while the race is still running.
You never mark a leg. You tap instants — the class flag, the gun, each leader rounding — and the legs work themselves out. Beat 1, Run 1, Beat 2, however many the course has.
One race, its legs along the bottom, viewer markers rising above it. Nobody typed those legs.
Tell us the page, what you were doing, and what happened. Screenshots help. "The admin page confused me" is useful; "I couldn't tell which button logged a flag" is far more useful.
Disagreements between testers are the most valuable thing you can give us — where two of you want opposite things is exactly where the design is still undecided.