this post was submitted on 15 Jan 2025
20 points (100.0% liked)

Summit

767 readers
27 users here now

Community to discuss Summit, a Lemmy reader for Android.

App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit

APK: https://github.com/idunnololz/summit-for-lemmy/releases

Patreon: https://patreon.com/SummitforLemmy

Ko-Fi: https://ko-fi.com/summitforlemmy

Website: https://summit.idunnololz.com/

founded 2 years ago
MODERATORS
idunnololz
20
[Release][v1.51.0] UI polish (self.summit)
submitted 6 days ago by idunnololz to c/summit
10 comments fedilink hide all child comments
 

This release polishes different aspects of the UI. The main changes are to improve contrast in various parts of the app for both light and dark themes.

Full changelog

  • Added a setting to disable the text preview icon for certain post feed views.
  • Added support for haptic feedback on action buttons in the post feed/post screen.
  • Added a setting to enable/disable haptic feedback.
  • Fixed a bug where shadow is cut off from the link button in a post.
  • Experimental: Added special support for loops.video links.
  • Improved the contrast for the search bar in light themes.
  • Changed some image thumbnails to be rounded and also have a slight border for contrast.
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 6 days ago (2 children)

Sorry I meant I had switched it on not off. Does not work on my phone, neither gestures nor action buttons. I tested again on Voyager app and they work there, so no probs with systemwide function. Maybe wait for some more feedback from other users?

[–] idunnololz 2 points 6 days ago (1 children)

I think one action item I should add is check if the system setting for haptic feedback is on when a user turns haptics on and alert the user is haptics is not enabled in the system settings.

[–] idunnololz 1 points 5 days ago

Ugh what a mess. Apparently Google removed the ability to check if haptics is on in Android 13 because they didn't want apps to be able to set the value because the mechanism to set or check the value are the same. Then they just never added the functionality to check the system haptics state back so I can't even tell whether haptics is enabled system wide from the app :(

[–] idunnololz 2 points 6 days ago (1 children)

I just tested on the play store version on 3 devices:

  • a pixel 7
  • Samsung s24
  • moto g power 2021

It worked on all 3 devices. Note that there is a way to fire off haptic feedback even if you turn it off in the system settings. Summit does not use this method. It's possible other apps are firing haptics by ignoring the system setting.

[–] [email protected] 1 points 5 days ago* (last edited 5 days ago) (1 children)

The settings for haptic I have is to vibrate on all actions of the phone (not talking about Summit) like back open close apps etc. So when this is on then yes I have vibration in Summit as well but in every action even if the haptics in the Summit settings is off. So it's not that. Dunno if it's a GrapheneOS setting which I doubt since it works in Voyager app. Strange...

[–] idunnololz 1 points 3 days ago

For haptics, I am purposefully respecting the user's global settings for vibrations (this is also recommended by Android's documentation). So if haptics is off, then haptics will not work in the app. However there is a way to ignore the system setting. I'm not 100% sure if that's what Voyager is doing but it could explain why haptics works even if haptics is off.