Animated logo and 1v1 card in Rive, wired into the phone app

[EmotiveImpact]

Before: the logo and the 1v1 versus screen existed only as static designs and prototype CSS. The countdown before a battle was a split screen, and a finished battle went straight to the result screen.

After: both are Rive files, and the phone app plays them.

• Logo (rive/logo, 11 KB, four artboards): the full logo (the O draws in and the blue dot lands with a ping and glow), the opening screen, a small version without the glow, and a loader. The app's house logo plays it wherever it animated before, with a light tap in the hand as the dot lands.
• 1v1 card (rive/versus, 704 KB): four intros, picked per battle in versusData.pickIntro:
  • Seam Strike for an everyday battle, including the usual 50 OUT stake;
  • Tale of the Tape for a rematch, anyone you have met before or a stake of 100+, with real rows (steps a day, today, day streak, XP, head to head);
  • the Cinematic for a grudge match (3+ meetings within one win), a derby or the top of a leaderboard;
  • Let's Run for event battles, ready for when events exist.
• Countdown: the card plays, holds a moment, then opens the live battle. While the other runner hasn't accepted, it says so and offers a way back to the Arena.
• Result reveal: the first time a finished 1v1 from the last week is opened on a phone, the result lands on the card before the result screen. YOU WIN! or YOU LOSE, K.O. with the glass crack when the winner had at least double, then WINNER and LOSER on each side's win or respect shot and the prize. A tap skips it; Continue appears at the end.

Rive needs a development build, so Expo Go keeps the old screens (detected through Constants.executionEnvironment). The web build plays the same files through @rive-app/canvas.

How: each Rive project is generated from build.py into RML and built with the Rive CLI; the built files are in each export/ folder and copied to apps/mobile/assets/rive. In the app, src/components/rive holds the players (VersusCard, RiveLogo, each with a .web.jsx twin), the runtime check, and versusData.js, which turns a battle into the card's view model values (names, places, rule, stake, prize, clock, tape rows, photos with the Fighter Pack, profile photo, then shadow runner fallback) and the result. The card's cue events drive haptics and the Add your Fighter Pack pill opens the pack screen. Adds @rive-app/react-native 0.5.5 with react-native-nitro-modules 0.36.5, @rive-app/canvas 2.43.1 and expo-dev-client ~58.0.14 (main is now on Expo SDK 58), teaches Metro the .riv extension, ships rive.wasm in public/, and links the Expo project id for EAS cloud builds. 14 new tests cover the intro rules, the tape numbers, the bound values and the result. Checked on SDK 58: typecheck, tests, web, Android and iOS bundles, and headless playback of the tape, cinematic, win and loss.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KgT8xbybc86Rc11ZV48mab

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
outhere-site	Ready	Preview	Oct 17, 2026 12:09am UTC

[EmotiveImpact]

The red outhere-site Vercel preview isn't caused by this PR. That project builds the @outhere/web workspace, which only exists on the website branches (#6, then #5). This branch is based on main, which has no pnpm workspace yet, so the build logs show "No projects matched the filters" and no dist output. Every commit pushed to a branch based on main fails the same way. This PR only adds rive/ files, which the site doesn't build. The preview should go green once #6 is merged into main and this branch is updated from main. Until then there's nothing to change here.

---

Generated by Claude Code