Replies: 1 comment 3 replies
-
Thanks, @buzzb0x, for your feedback. To address the issue of inconsistent Lottie rendering experiences across platforms (Mobile and Web), we're developing a cross-platform, performant player in Rust. This development has led us to focus on the dotlottie-web, along with the dotlottie-android and dotlottie-ios players, which are built on top of dotlottie-rs. As part of this shift, we've decided to deprecate the old package @dolottie/player-component, recommending dotlottie-web as its successor. I understand there's currently a lack of documentation for the new dotLottie-web player. I assure you that I will ensure it's updated soon and will keep you informed on the progress. In the meantime, for use cases and usage, you can refer to the READMEs of dotlottie-web and the CodePen examples. The dotlottie-web player supports almost all the features of the old package, including the ability to play .lottie multi-animations. We are still working on adding state machine support, which we expect to complete later this year. Although the |
Beta Was this translation helpful? Give feedback.
-
Hello,
Thanks for the development of this new and improved library. I noticed you added a deprecation notice to the old one last week, and we started using Lottie on a project I'm working on so we switched to this one.
We're now needed to use multiple animations in the same dotlottie as well as state machines, and this package doesn't support any of that. Furthermore, no documentation is up to date on the website yet.
Should we just switch back to the old package? Maybe be clearer on the documentation and on the old package that this is an early release and only supports the most basic use cases?
Cheers
Beta Was this translation helpful? Give feedback.
All reactions