u/Winter-Initiative-86

Current Dilemma. My girlfriend and I have individual tickets for Open Solo for both men and women on June 1 and we also have a mixed doubles ticket on June 3.

As the race day fast approaches, we are doubting if it is advisable to do both races with only 1 day rest considering the recovery time we need to perform effectively on each event. We are comfortable of selling one and do one race for us to experience but before that, does any of you have experience of doing 2 races in a week?

I know it depends on the fitness level. I recently finished the Brooklyn Half Marathon last May 16, finished in 1hr and 56mins cruised the whole race at 161bpm so endurance is there. I can also comfortably run under 4:45/km in short runs and I regularly lift weights so I can say I am physically fit but I wonder what will be the toll to my body after the solo open on june 1st. What do yall think? Should we sell the mixed doubles and do the open or the other way around?

Appreciate any leads.

https://preview.redd.it/tlc54pannfyg1.png?width=2866&format=png&auto=webp&s=b925d0bd1c7ca51562fbc69f9df5065f121edc20

Live: trakkr.nyc

Built for the CUNY AI Innovation Hackathon 2026. Type a station, get a one-screen safety report — crime risk verdict (SAFE / CAUTION / HIGH RISK), 30-day elevator/escalator failure forecast, live MTA service alerts. Zero login, zero data stored, sub-second.

I'm not a developer. The whole thing was vibecoded. Hackathon's done but I bought the domain so I'm keeping it alive and iterating. That's why I want real UX feedback now — before I build on top of a shaky base.

The stack (full vibecoded chain):

AI tools

• Claude Opus 4.7 — primary builder. Wrote the React code, structured components, debugged everything I threw at it.
• Google Stitch — generated full-page UI drafts I cherry-picked and adapted.
• Claude Design — UI mockups and component sketches before committing to layouts.
• 21st.dev — animations and prebuilt motion components. Saved me from learning Framer Motion from scratch.

Frontend

• React + Tailwind, deployed on Vercel.

Backend / ML

• Python + scikit-learn, deployed on Render.
• Two trained classifiers — elevator SLA breach (96.8% acc, AUC 0.65) and chronic crime hotspot (96.8% acc, AUC 0.95). Both cross-validated against unseen records.

Data

• Mapbox API for maps and geocoding (address → nearest station).
• MTA API for live train and equipment feeds.
• NYPD historical data via NYC Open Data — 5+ years of transit crime records.
• MTA elevator/escalator availability via data.ny.gov.

The process (the actual vibe):

1. Started with a question, not a product idea: "is the subway actually getting worse, or does it just feel that way?"
2. Wrote a findings.md analysis doc in Claude first. Forced the data to make a case before any code.
3. Trained the ML models second. Validated before building any UI.
4. Generated rough page layouts in Stitch and Claude Design. Picked the ones that didn't look like every other AI landing page (still working on this).
5. Pulled animation patterns from 21st.dev. Wired Mapbox for geocoding so people could enter an address instead of memorizing station names.
6. Opus 4.7 stitched it together, debugged, and shipped — frontend on Vercel, API on Render.

What I'm proud of:

• Headline does its job: "Other apps tell you what broke. Trakkr tells you what's about to."
• Single-input UX — type any NYC address, Mapbox finds the nearest station, the model returns a verdict. No filters, no menu, no setup.
• Models actually generalize. Not toy numbers — validated on records the system never saw.

What I'm unsure about (the asks — be brutal):

1. Hero rotation. Headline cycles through "smarter / safer / smoother / surprise-free / right on time." Playful or annoying?
2. Trust badges under the CTA ("real live MTA data · trained on years of records · no login · sub-second"). Necessary or visual noise?
3. "Who It's For" — 4 personas. Daily commuters, accessibility riders, parents, researchers. Helpful segmentation or am I telling people who they are?
4. 10 testimonials in the carousel. Probably too many, and I worry they read AI-generated. Right number? Three? Five? And how do you make hackathon-stage social proof not feel fake?
5. Navy + orange palette. Smart (MTA-familiar) or boring (looks like every transit project)?
6. "TrakkRecord™" trademark. Memorable branding or premature swagger for a hackathon piece?
7. Buy-me-a-coffee floating button. Distracting from the primary CTA or fine?
8. Mobile. Built desktop-first, patched mobile after. Probably shows. Fastest way to find what's broken without a real testing setup?
9. The big one — for vibecoded sites specifically: what's the dead giveaway something was AI-built but undesigned? I want the heuristic so I can spot it in my own work going forward.

Look, I'm not posting this for upvotes — I'm posting it because I know my UI/UX instincts are weak and I want to build them. If you've shipped a vibecoded product, designed a landing page that converted, or just have strong opinions on what makes a transit tool feel trustworthy, I want to hear it. Tell me what's broken, what's underbaked, what's trying too hard. Drop a tip on a tool, a pattern, a YouTube channel, a designer to follow — anything that helped you go from "this works" to "this looks intentional." I'll read every comment and reply to as many as I can. The product is going to keep evolving, and the next version will be better because of what you tell me here.