1. Use the search bar at the top to check if your request already exists.

2. Upvote any existing requests you want us to prioritize.

3. Use the 🚧 In progress, 🚀 Launched, and 🗺️ Planned labels in the Filter menu above to see what we’re working on.

4. If your request does not exist yet, create a new one. Duplicate requests will be deleted.

It's unusual to see a tool geared towards the web which eschews Vue support. While Vue may not be quite as popular as React, it is still widely used, and offering support (be it a simple wrapper, or something more) would go a long way for the community. It would be great to see this offered as a feature in the future.

Selecting a mesh in "Animation" should navigate to the parent or directly enter edit mode.

With the ability to edit objects simultaneously, you can snap an object's vertex to another object's vertex.

Require a button to key all objects's current properties instead of keying them one by one.

Currently searching doesn't find any state machine layers. That would be handy.

Shortcuts on Windows are pretty universal amongst apps. For example, search is CTRL+F.

Imagine if every app uses different shortcuts for common tasks. Firefox search is SHIFT+Q, MS Word search is ALT+R, VS Code search is CTRL+Y, etc. That would be pretty unproductive.

Rive does not use Windows-standard shortcuts. That is a pity, not necessary. It makes it less intuitive to work with and less productive due to unintended actions caused by the brain not wired to the keyboard.

Please, stick to an industry standard or provide the user with the option to re-map shortcuts.

Some sort of function that allows exporting animations that only exist as a combination of layers in the state machine. As opposed to rendering one animation timeline at a time. Ex. If I had a state machine where each layer controls a different aspect of my animation, currently, I cannot export a sequence where all animations are playing together.

Just adding to ask if any updates/detail on this upcoming feature?

beside the possibility of keying the volume in the future, I wish we can have the control to pause and stop an audio piste. this will give the ability to switch from one song to another in runtime if needed.

For turrets and stuff.

Voice chat per file. Instead of just having a user in the file, make voice chat available within the file. Whenever I've actively collaborated on a file, I've used slack to coordinate. Maybe not worth it since things like huddle and meet exist, but I do think we should take as many steps as possible to eliminate the need for additional software.

A workshop file would allow you to invite users to a file where they can watch you work on something. This, I believe, would be a better way to do internal training, rather than deal with the low frame rates of things like Meet and Zoom. This idea only works if we have voice chat.

As great as it will be to have a way to quickly share files between users, realistically you still need other tools like slack or discord if you want to send someone information about the file. I think it would be great if this could all live in that Info panel Alex was showing off today.

Comments - Comments would be a good way to just shoot someone a file with a quick message like "Hey, I need help with this interaction".

Video - Attaching a video file (created outside of Rive) or a video walkthrough (something created within the Editor) would eliminate the need to send someone a message outside of the editor explaining how a file works, or how a particular interaction is set up.

A shortcut to save a current revision would be nice. Instead of saving the current revision within the file (though that would be nice too), it would prompt you to rename the revision, then save a copy of the file to your file browser. Instead of dumping it into a random location,  it would wrap the current file, plus the saved revision into a folder. It might also be nice that if you save a current revision, you could send that revision to other users, or to a specific destination within a team or in your file browser.

This is an easy way to prototype interactions; then, instead of creating a new file, you can save those prototypes and delete them from the file after building your finalized assets.

This also serves as a way to freely brainstorm in a file, save an idea, delete the artboard, and continue working.

Seems like a lot of those new share functionality has been thought about already, but figured I'd drop in some of those ideas here.

Share directly with a user. Team spaces are great, but in reality, they get cluttered REALLY quickly. They're a great space for finalized assets to live while waiting for production. Those assets are easily updated within that space as well. The big problem is when someone on your team wants help with a particular interaction, you probably want to avoid clogging up the team space with random files, so having the ability to share a file directly would be a great addition. We could have a few sharing options that could make the experience flexible and be right for any situation.

1. Send to team - Sends a copy of the file from your personal space, directly to the team space.

   Bonus points if you could dictate exactly where the file ends up, so the ability to say, send to Folder X or Y.

   BIG bonus points if you could "tag a team member". This would allow you to tag a team member and that team member would receive a notification that "a new file has been added to the X Folder on your team". In addition to tagging, sending a little note with the file would also go a long way.

   MORE bonus points if files that you are tagged in could be found in the "shared with me" tab in the file browser.

2. Share with user - Shares a copy of a file directly with a user. That file lives in a "shared with me" in the file browser. This is an ad-hoc team space where shared files live. They don't have to be collaborative like a team file, but could they be? The idea with this is to make sharing a file easy, without needing to clog up a team space or, without needing to download a .rev, send the file and a message on Slack or email.

   In an ideal world, users would receive a notification that a new file has been shared with them, and the sending user could attach, AT A MINIMUM, a message to the file. The PERFECT scenario is if we could attach a video clip.

   As an add-on to the "Save current revision" idea, sending a specific revision would also be great.

3. Share with viewer - Basically, a share link, but more akin to a community post. Viewers would be able to leave general feedback, maybe even give reactions similar to how community posts work now?

   Files shared in this way would also live in the "shared with me" tab on the file browser... so viewers would need to have their own Rive account.

   Good way to share with the big boss man who is just there for the final thumbs up or down.

4. Share for review -  This is similar to sharing with a viewer, except there's added functionality for creative directors, or heads of motion, or whatever the role would be. It would likely look like a share-link or community post window.

   CMD+SHIFT+C - Takes a screenshot, pauses playback, or somehow creates a timestamp so that specific feedback can be given.

   In a perfect world, you'd be able to draw on the window.

Would be nice to be able to copy modifiers from one text object to another

Would be nice to be able to quickly create an animation, folder, or state machine by right clicking the empty space (instead of having to go up to the plus (+) icon

When copy/pasting things from one tool to another, the expectation from other design tools is that the object you're pasting immediately appears where you're working. I'm not sure if I'd want it to show up in the assets in this case. I think if I drag it in then that's different, and I want it to appear in Assets.