[yieldcrv]

this would be a big hit with NFTs in a couple ways:

easiest: the team's own website can display the NFT images in their own gallery, similar to OP. Anywhere else displaying the NFT will not have these effects, like the marketplaces

medium: major NFT marketplaces and displayers allow 3mf file format, which is a 3D file format which can also accept mouse over movement and other UI interactivity on top of the main image (or 3D object). so one would do this in 3D software first and then render out distinct files

hard but efficient: you can embed an HTML/SVG viewer into the NFT code itself, which could theoretically include all of this CSS and mouseover/tap events. This would make it more portable to be rendered with these features in more places and wouldn't require as much cumbersome processing and file portability to do everything needed for the .3mf format. The additional benefit is that all of this code could be directly onchain (while the raster image still is on IPFS/elsewhere)

[random_kris]

How can I about this to put your words to reality

[yieldcrv]

I’m the biggest fan of the third option, basically you are relying on nft image viewers being so universally compatible with everything that can be returned from the nft getImage protocol standards

One is a raster image

Two is an interactive 3D file

Three is HTML injection

you can stuff each into the image method