Our Dev mode team filed a bug for this, but then got busy with other projects surrounding Config 2024. Now that things are slowing down again, they hope to do a deeper dive into fixing this issue.
We appreciate your patience and understanding - stay tuned!
Hey guys, any updates? I saw the same issue and now most Android team are moving towards Compose, and we need the proper code translation for the dev team.
Our team reported back that Android hasn’t improved the functionality of the .shadow() modifier since we originally filed a ticket, so there is no easy fix yet.
To correctly translate Figma shadows to Android shadows, we would have to build a custom modifier from scratch. This would be a separate package or library that users would install. Instead of .shadown(), users would use .figmaShadow() to replicate the behavior of Figma shadows.
Is this something you’d be interested in?
I’ve updated this topic into a feature request to gauge overall interest from the community. If we get enough votes from dev mode folks, we’ll be able to advocate for the project and team effort it would require to build.