this post was submitted on 24 Mar 2025
18 points (100.0% liked)
Summit
887 readers
11 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
Support the app
Website: https://summit.idunnololz.com/
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To simplify these requests I will group all of the moderation requests together in the roadmap.
Will be in the next release.
This is already a feature in the app technically. In the create comment screen tap the three dots button (top right) > Show full context.
Too vague to action on as-is.
This is already supported. Tap Search in the nav bar > Tap the search field > Tap either "Filter by community" or "Filter by creator".
Everything else has been added to the roadmap.
Maybe I can elaborate on @asudox's note:
When I went to this post, initially, after having changed accounts across instances in the app, it didn't give me the instances-mismatch prompt at the top even after refreshing, and then I couldn't comment. This happened with multiple posts and I haven't able to figure out how to get it to change APIs at the moment of account-switching. For example, the Lemmy app Thunder has no such issue; it always uses the correct API per account.
Could you please provide some reproduction steps for this issue? I cannot reproduce it with how I am testing the app.
I ultimately couldn't replicate it, but there was a weird time just a few hours ago when I was in one account and literally everything I opened in the feed opened in the other one, which then kept yielding this desync error so I couldn't comment (even after ). I'll see what I can do to reproduce it...
Could there be a setting added to automatically open the keyboard immediately on this first tap, which is how comment-searching already works? Search currently feels like the new/worse Play Store, which makes you have to tap the magnifying glass at the bottom, and then the text field at the top, which seems counterintuitive. Thanks!
Additionally:
I have to manually look for it again the way I found it the first time instead of just being able to press Back or any faster way to return to it.
~~There is no localized view history or something like that.~~ The way other apps do it is by allowing the general search to be accessible from a side pane or 3-dot menu at all times.
Update: Okay, I found History. Wow, the settings are deep!
Regarding the search screen: There is a feature request on the roadmap to make double tapping search on the bottom bar open the search screen with search focused.
This could solve this issue but it's not perfect since the gesture is random and doesn't really follow any existing UX design. By the way the reason why search looks the way it does is because I received feedback that some people wanted to be able to view their communities with a single tap of a button and when not on the home screen. The search screen has turned into a general hub of random lists as a result of that request.
For being able to search from a post, there isn't technically anything preventing this from being supported in the app. I just think it's a not something the average user would use. As a solution I can add a setting that shows the bottom bar even on the post screen. I'll add this to the roadmap but let me know if you don't like this idea.
The option for a persistent bottom bar would be fine, yeah! An option to immediately show the keyboard or not when calling the search engine might be nice as well and would solve this issue without disgruntling the users you reference.
Sure i can add that to the roadmap.
Thanks for the info