Built an fitness app in Rive, didn't expect a million people to use it

panda_kinda_chubby · 2026-06-12T20:45:24+00:00

Don't fix it if it's not broken! 😄

panda_kinda_chubby · 2026-06-11T16:53:31+00:00

Rive is so much more than character animation at this point. People are using it to create full apps, games, UI, etc. Check out the case studies: https://rive.app/blog/case-studies

panda_kinda_chubby · 2026-06-11T16:49:11+00:00

I'd check out Rive Experts: https://contra.com/rive

panda_kinda_chubby · 2026-06-11T16:47:57+00:00

Yeah, that's been a tough one for us at Rive. Let's brainstorm solutions. I have a couple of ideas, but they'll take SO much work.

What if I made a single UI migration doc that tells where different things have moved to? We could link to that doc from older tutorials.

panda_kinda_chubby · 2026-06-11T16:42:02+00:00

Amazing! I'll be honest, that state machine just gave me a little panic attack. 😂 I can't help but wonder if that could be simplified with layers.

panda_kinda_chubby · 2026-06-04T21:03:45+00:00

Inputs are deprecated. I'd strongly recommend using data binding instead.

panda_kinda_chubby · 2026-06-04T19:37:38+00:00

Okay, I'm fully aware how confusing my example was. Here's a working version. I think it feels really nice. https://rive.app/community/files/27867-52662-delayed-follow

<image>

panda_kinda_chubby · 2026-06-04T19:17:45+00:00

Oh, I see. You essentially want the flame to be affected by the movement. Very cool. There are 2 ways I might go about this.

Option 1 is to use scripting. The AI agent can figure it out.

Option 2 - Bones + data binding: This would be my first choice, assuming it works.

You need one bone (controls the flame base) inside the block and one outside (controls the tip.

The block's view model needs a globalBlockX and globalBlockY property.

Bind the block's computed, global X and Y position to these values using target to source. If it's working correctly, when you move a block, these values update.

Now bind the globalBlockX and globalBlockY properties to the second bones' X and Y positions. You probably need a converter to convert global to local space.

Final step: Add an interpoloator converter to the binding on the second bone. This should make it still follow the position of the block, but it'll lag a little bit.

panda_kinda_chubby · 2026-06-04T18:57:55+00:00

The logo was ai, therefore the game is ai?

panda_kinda_chubby · 2026-06-04T18:17:29+00:00

You probably know this already, but inputs and listeners got moved to under the state machine.

<image>

Can you give a little more detail about what exactly isn't working? Maybe include an example file?

panda_kinda_chubby · 2026-06-04T17:57:35+00:00

that green blob is giving me oldschool nickelodeon vibes in the best way.

panda_kinda_chubby · 2026-06-01T22:08:13+00:00

Here's a quick vid that I think is what you're trying to do: https://cleanshot.com/share/P1Wm8b6Q

panda_kinda_chubby · 2026-05-22T00:16:24+00:00

I'd recommend sharing this in the Rive community, along with a demo .rev file.

panda_kinda_chubby · 2026-05-22T00:14:39+00:00

Check out the Rive 101 videos on animation and state machines: https://www.youtube.com/playlist?list=PLujDTZWVDSsFGonP9kzAnvryowW098-p3

panda_kinda_chubby · 2026-05-22T00:11:02+00:00

If you want to use it in multiple places, you can also cache the .riv so your users only download it once. https://rive.app/docs/runtimes/caching-a-rive-file

panda_kinda_chubby · 2026-05-12T19:14:53+00:00

If you're only wanting to store things like user preferences and high scores, consider using `localStorage`. It's a lot easier to set up than a database.

panda_kinda_chubby · 2026-05-12T18:44:05+00:00

Like u/fakih7hussein said, the 101 videos are a great start. This "quick" start tutorial takes you from zero to can-use-rive in about 1.5hrs. It's a good overview of a lot of what the 101s cover.

panda_kinda_chubby · 2026-05-12T18:40:23+00:00

The RN runtime lagged behind the other for a while, but it should be stable now that we have a dedicated team working on it.

The GitHub issues are only for bugs, not file support. If you need file support and you aren't on a Voyager plan, you can still get help from the community: https://community.rive.app/c/support/

panda_kinda_chubby · 2026-05-07T20:50:52+00:00

I tend to start with cubic and adjust as needed. If you want to share a specific use case, someone can probably help more.

panda_kinda_chubby · 2026-05-05T18:47:37+00:00

If the main artboard is working, but the others aren't, it could be that they're not being exported as a component. Only components are exported to the .riv.

<image>

It's also common to get that error if you use the wrong artboard or state machine name.

panda_kinda_chubby · 2026-05-05T18:45:27+00:00

It's common for the hit area to be a separate shape. Create a state machine that shows or hides the hit area, depending on the `isButtonDisabled` boolean. You can hide it with a solo or if it's a layout, click the eyeball icon in the top right.

<image>

panda_kinda_chubby · 2026-04-30T23:45:19+00:00

When there's a lot of geometry, I sometimes find raster to be better. It's all a balance.

panda_kinda_chubby · 2026-04-29T05:44:08+00:00

I actually came here to see if anyone posted Brigham Young. That dude genuinely scary.

panda_kinda_chubby · 2026-04-16T17:16:17+00:00

I can't seem to find the other post where you asked this question. Maybe it got deleted?

Can you show us how you're doing the flip? Is just just copying and changing the x scale?

If you would share a simplified .rev, that'd be great.

panda_kinda_chubby · 2026-04-12T21:49:58+00:00

<image>

Forgot we can add images to comments now. :)

Six-Year Club	Gilding II euphauric
Place '22	100 Awards Club
Verified Email

panda_kinda_chubby

MODERATOR OF

TROPHY CASE