-
Notifications
You must be signed in to change notification settings - Fork 26
post interaction button changes (re-up) #811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
post interaction button changes (re-up) #811
Conversation
Summary of ChangesHello @ThatOneCalculator, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on refining the user experience for post interaction buttons by introducing both visual and haptic feedback. It adds a subtle 'pop' animation and haptic feedback when users like or bookmark a post, ensuring a more engaging and responsive interaction. Additionally, it implements smooth transitions for the icons of these buttons and makes a minor adjustment to their size in specific display contexts. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a 'pop' animation and haptic feedback for interaction buttons like 'Like' and 'Bookmark', and adjusts icon sizes. The changes are well-contained and improve the user experience by providing clear visual feedback. My review includes suggestions to simplify the animation logic, improve code readability by removing magic numbers, and refine the use of haptic feedback to better align with platform conventions. Overall, a nice enhancement to the UI.
ui/timeline/src/commonMain/kotlin/com/tunjid/heron/timeline/ui/post/PostInteractions.kt
Outdated
Show resolved
Hide resolved
ui/timeline/src/commonMain/kotlin/com/tunjid/heron/timeline/ui/post/PostInteractions.kt
Show resolved
Hide resolved
ui/timeline/src/commonMain/kotlin/com/tunjid/heron/timeline/ui/post/PostInteractions.kt
Show resolved
Hide resolved
|
There are some small perf things I'll fix on top of your commits. |
|
Ty! I'm sure that I'm missing a lot of best practices, I've never done any meaningful work in Jetpack Compose until now. |
|
Sorry still reviewing this. One of the reasons animating this has been put off for so long is that the architecture of the app is offline first and the database is always the source of truth. So changes to When the app is offline, the anim is really delayed and looks off. The Bluesky post about assuming opportunistic writes would be nice, but then I have to manage state about what the expected value and the actual value are. So each tap has an expected value where the db should eventually catch up to. In the case the app is offline, this won't happen anytime soon and I need to have a sort of intermediate state showing the like (or bookmark, repost, etc) is pending. This is why I wanted to use lottie so I could play an animation loop till the action is confirmed. |
|
I don't think that the pop animation looping would look good, imo it should either be:
|
|
Superceded by the PR above. Closing. |
Re-up of #809 just for the button size & pop