Frequently Asked Questions

Common questions about Backflit and our best attempts at answering them.

Is this the only way to create components in Rive?

Definitely not.

There are definitely simpler ways to build many of these components, especially for small or short lived projects. Backflit leans toward solutions that scale as a project grows, even if that means a bit more structure up front.

What we trade in initial simplicity, we try to make up for in:

• Easier maintenance
• Clearer ownership of data and state
• Components that are easier to reason about months later
• Fewer surprises as UI complexity increases

If parts of this feel like too much for your use case, feel free to simplify. The files are meant to be read, modified, and adapted.

Can I use this outside of Rive?

Sure. Kinda.

Most engines already come with basic UI components, so you may not need Backflit directly unless you need more control over how your components work. That said, a lot of the logic in Backflit applies beyond Rive.

At its core, it mostly deals with state machines, data, and events. Those ideas translate well to other UI systems, even if the implementation details differ.