this post was submitted on 12 Jul 2023
89 points (97.8% liked)

Voyager

5579 readers
22 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! 👇

Number of sponsors badge

💙

founded 1 year ago
MODERATORS
 

It’s probably a minor thing, but I dearly miss the Apollo feature to press on the title bar while deep in a comment thread and have it take me to the top. A second press would then return you to where you were.

Can we please have that feature in Voyager?

you are viewing a single comment's thread
view the rest of the comments
[–] corb3t 1 points 1 year ago (5 children)

Have you ever used GitHub? You can submit suggestions to Voyager’s GitHub, located here:

https://github.com/aeharding/voyager

[–] [email protected] 3 points 1 year ago (4 children)

I’ll see if I can put in a suggestion over there too. I’m used to r/ApolloApp and r/ApolloAppBeta being the places to interact with the dev, so while I understand using Github for version/issue/documentation tracking and updating, I think using this community for bugs and feature requests is better because it doesn’t send people to another site, and keeping people here then further builds the Voyager community.

[–] corb3t 3 points 1 year ago (1 children)

For sure! Discussing new features within this community is a great idea - I just know the dev himself said he implements suggestions faster when they’re put in GitHub, so it may be worth adding over there eventually.

I added a suggestion for adding starts next to subcommunities to favorite them, and they were able to implement them in a few days - pretty cool!

[–] [email protected] 1 points 1 year ago

There is an issue raised for this.

It’s currently somewhat blocked because PWAs cannot access the status bar. They are working on some other options though.

load more comments (2 replies)
load more comments (2 replies)