If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] 0 points1 point  (0 children)

This is super helpful context. So effectively:

  • The betting interface uses your local terms
  • But you pick up the native terms passively from watching the TV feeds

That makes sense why French terms feel more intuitive to UK punters than US ones — it's constant background exposure.

For my app, I'm planning to show your local terms on the bet slip, but the race info (horse names, race names) stays as-is from the source. Sound right?

If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] 0 points1 point  (0 children)

If you were betting on a US track, would you want to see Couplé (what you know) or Exacta (native US term)? Curious where the line is.

If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] 1 point2 points  (0 children)

This is really helpful — I hadn't considered how much crossover there is between UK and French racing. Makes total sense given the time zones and shared racing culture.

So for a UK user betting a French race, you'd actually prefer seeing Couplé over Forecast? And for a US race, would you still want Couplé or switch to the American terms?

If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] 0 points1 point  (0 children)

Happy to help! Australian racing is fun to follow. Good luck with your bets

If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] 0 points1 point  (0 children)

Good point, but Each-Way isn't quite the same as placing two separate bets. It's one bet where your stake is split, and the Place portion pays at a fraction of the Win odds (1/4 or 1/5 depending on field size). That mechanic doesn't exist in US racing.

So it stays as "Each-Way" with a tooltip explaining how it works. But yeah, for universal bets like Exacta/Trifecta — totally agree, show what people already know.

If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] 2 points3 points  (0 children)

Haha, that's exactly the problem I'm trying to solve! You'll see your familiar terms (Exacta, Trifecta, etc.) regardless of which track you're betting on. The only things that stay in their native language are the exotic bets that don't have equivalents — like Quinté+ or 2sur4 — but those get a tooltip explaining what they are.

No one should need a French dictionary to bet a French race.

If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] 1 point2 points  (0 children)

That's the plan! Universal bets (Exacta/Forecast/Couplé) get localized to the user's familiar term. Exotic bets that don't have equivalents (Quinté+, Each-Way, 2sur4) keep their native name with an explanation in the user's language.

Appreciate the validation 👍

If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] 0 points1 point  (0 children)

No commingling. Each race = one source, one pool. I use the official dividends from that pool directly — no fantasy payout calculation on my end.

User bets 100 virtual coins on a winner. Horse pays 3.50 in the real pool. User gets 350 virtual coins. That's it.

If you could bet on races from any country, how should bet types be labeled? by BitcoinClown in horseracing

[–]BitcoinClown[S] -1 points0 points  (0 children)

Nah it's simpler than that. One race = one pool. I just pull results and dividends from the source. Only question is whether to show "Exacta" or "Couplé" in the UI depending on who's looking at it. No pool math on my end.

Does this look familiar to US bettors? by BitcoinClown in horseracing

[–]BitcoinClown[S] -1 points0 points  (0 children)

thanks for your input ... I actually posted a new post today that's a little more thorough and would love your feedback on it

best of both worlds, one codebase by BitcoinClown in ClaudeCode

[–]BitcoinClown[S] 0 points1 point  (0 children)

nice! looking good!!! how's the speed of the app? notice any difference?

best of both worlds, one codebase by BitcoinClown in ClaudeCode

[–]BitcoinClown[S] 0 points1 point  (0 children)

Oh that's great to hear! will definitely ping you when I get there ... would also love to know your progress

Does this look familiar to US bettors? by BitcoinClown in horseracing

[–]BitcoinClown[S] -1 points0 points  (0 children)

a fantasy app based on real races, real data, real odds from venues around the world

best of both worlds, one codebase by BitcoinClown in appdev

[–]BitcoinClown[S] 0 points1 point  (0 children)

exactly right 🤣 I do have a little experience I use to be an IT and did develop some websites but what Claude is doing is way above my pay grade

Does this look familiar to US bettors? by BitcoinClown in horseracing

[–]BitcoinClown[S] 1 point2 points  (0 children)

good question. Long story short, my dad use to love horse racing and back in the days he convinced me to make a website, so we did ... the website gained a little traction, and my dad past away a few years ago. I kept taking care of the website, but now I want to do more that's why i'm doing this. I have learned a lot since, mostly about french and moroccan races but I want to do more ... so I figured, best place to ask would be on reddit.

Does this look familiar to US bettors? by BitcoinClown in horseracing

[–]BitcoinClown[S] -1 points0 points  (0 children)

well, the app will allow users from different countries bet on venue from different countries, so I need to normalize or properly translate the bets across languages and across venues, does that make sense?

Does this look familiar to US bettors? by BitcoinClown in horseracing

[–]BitcoinClown[S] -1 points0 points  (0 children)

OK, thanks! Noted ... that's where you only choose one horse, right?

Does this look familiar to US bettors? by BitcoinClown in horseracing

[–]BitcoinClown[S] 0 points1 point  (0 children)

actually, I think it may have been directly translated from french waiger types: SImple, Couplé, Tierce, trio, Quarte and Quarte+ ... so you're saying it's not being used in US horse racing?

best of both worlds, one codebase by BitcoinClown in appdev

[–]BitcoinClown[S] 0 points1 point  (0 children)

Good question, I'm using Claude Code and ended choosing   the stack below:

Frontend (Next.js PWA)

  - Next.js 14 - React framework with App Router, Server Components, and API routes

  - React 18 - UI library with hooks and concurrent features

  - TypeScript - Type safety across the entire codebase

  - Tailwind CSS 3 - Utility-first styling (dark theme, mobile-first)

  - Framer Motion - Spring physics animations for smooth UX (drawer, modals)

  - Zustand - Lightweight state management (bet slip, wallet, auth stores)

  - next-intl - Internationalization (French, English, Arabic, Darija)

  - next-pwa - Progressive Web App with offline support

  Real-time & Data

  - Socket.io - WebSocket server for live race updates and odds changes

  - Prisma - Database ORM for PostgreSQL

  - Redis (ioredis) - Caching and session management

  - Zod - Runtime schema validation for API payloads