Open thunderbiscuit opened 1 year ago
Hi @BhuvanAde. You are more than welcome to investigate, but I do think that it's a rather technical issue related to the Compose compiler and compatibility with older Android APIs. If you are an UI/UX designer, I'm not sure this issue is the perfect fit for you. I also didn't put any extra comment there, so I do wonder if maybe you thought it was something else than what the bug actually is. Let me know if you want more explanations.
@thunderbiscuit Please let me know if there are any issues related to UI/UX. I would love to do that!
At the moment there isn't much, as I'm sort of repositioning the project towards cleaning up some technical debt and preparing for the 1.0 release. You can keep an eye on the issues I tagged for the 1.0 milestone here. There isn't much, but hopefully we add a few as bug reports come in!
If you'd like to try the latest version in the Play Store and play around with it, you can also open up issues on the repo with small UI issues and suggestions (for example I'm not sure how the app looks on very small screens or very large ones, so if you have access to that you could share screenshots of UI breaks if there are any).
standardShadow is an extension function that is based on advancedShadow modifier right?
I am not able to figure out the expected and actual behavior ( I am on Android 11). Here is what I can see from Cancel
button that seems to use standardShadow
Hey @thunderbiscuit, I'm Bhuvan Ade. A UI/UX Designer Can I please work on this issue?