Hi there! I'm Roni, I traded 1,000lbs horses for 1,000 line bugs.

Problem

Official rulebooks are long and written for officials, not fans. If you want to know why a call went the way it did, you shouldn't have to dig through a PDF to find out.

Solution

I designed and built a Q&A app that answers rules questions in plain language, grounded in official volleyball and basketball rulebooks. It also has an "Ask by voice" mode built on LiveKit.

Problem

SheKnows busts myths about women's sports using Gemini with live web search. Answers sound confident either way, so I needed to know whether it was actually getting the facts right.

Solution

I built an eval suite of 26 test claims to score the app's verdicts. It showed that search grounding was essential: without it, the same model confidently called true 2025 records false.

Problem

Annual data-heavy report viewed by thousands. Previous versions had rigid layouts, and cross-browser issues slipped through under deadline pressure. We needed a flexible front-end that wouldn't break with last-minute changes.

Solution

I led front-end development with Next.js, Tailwind, and react-spring, building systems that adapt instead of forcing content into fixed layouts. Charts that had custom animation and styles. I also chose the animation library and guided design conversations.

Problem

Sports stats are everywhere, but most dashboards feel static and cluttered. I wanted a clean, animated view of women's sports team statistics that's actually enjoyable to check, not just another table of numbers. Plus, ESPN's API doesn't cover every league I'd like to include, so I needed a flexible system that can adapt as I add more sports.

Solution

I built an animated dashboard that pulls live sports data from the ESPN API and displays key stats - wins, win percentage, goal difference, and team rankings - in a visual, scannable layout. Motion is used purposefully to guide the eye, not just for decoration. The component-based structure means I can add new leagues (MLV, WPBL, etc.) as API access allows, even if each one requires a slightly different data mapping.

Problem

The supporters group for Denver Summit FC needed a way to process membership payments through Square and automatically trigger welcome emails via Brevo. Wix handled the frontend, but no native connector existed to tie Square payment success to Brevo automation.

Solution

I built a custom workflow using Square's SDK to handle payment processing. On successful payment, the Wix backend (via a backend file) receives the confirmation, then sends the supporter's form data to Brevo's API to trigger an automated welcome email sequence. The setup includes an HTML widget for the Square form, frontend page code to manage state, and backend logic to connect everything.