Lottie render

[Totemancer]

Noticed that using rlottie.worker.ts to display and render Lottie files. This seems not compatible with rasterized Lotties, including data:image/webp;base64, webp, jpg, or png images as usually seen from the Bodymovin plugin in After Effects.

Can we ask please to add support for such rasterized Lotties, or in case data:image/ is detected, disable the playback and fallback to image to prevent displaying broken state images?

Example NFT (External metadata can be found on this page to test locally): https://tonscan.org/nft/EQDc5dZf9dL7e96eUYNBjUWsxQ9R3qdLxwqkLNMXjhQ2OKNr

"lottie": "https://collection.totemancer.com/nft/c/totemancer_assets/1-mov/BEA_5MB.lottie.json"

Thank you!

[Totemancer]

Some other things to notice:

If you have about 10+ animated Telegram gifts in MyTonWallet, they all start playing at once (as you scroll), causing memory issues and the whole app refreshes/crashes.

In the network activity, it looks like the Lottie file is downloaded every time it plays. Might consider local caching since this metadata rarely changes to improve performance and reduce network hits.

Suggestion: Load Lottie animations only when the NFT is maximized to view with the use of static thumbnails in lists to reduce memory and network usage.

[Yachicken7]

Yes