[GH-ISSUE #1914] Ability to reorder bookmarks (Android) #1281

Closed
opened 2026-02-25 22:39:32 +03:00 by kerem · 2 comments
Owner

Originally created by @AZeed18 on GitHub (Apr 13, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1914

Describe the feature you'd like to request

Add the ability to reorder bookmarks in the Android app

Describe the solution you'd like

Maybe hold and drag to move a bookmark, or buttons to move up and down

Describe alternatives you've considered

Reorder only from a desktop browser

Originally created by @AZeed18 on GitHub (Apr 13, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1914 ### Describe the feature you'd like to request Add the ability to reorder bookmarks in the Android app ### Describe the solution you'd like Maybe hold and drag to move a bookmark, or buttons to move up and down ### Describe alternatives you've considered Reorder only from a desktop browser
kerem 2026-02-25 22:39:32 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Apr 13, 2025):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

<!-- gh-comment-id:2799899205 --> @github-actions[bot] commented on GitHub (Apr 13, 2025): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (Apr 16, 2025):

Hello @AZeed18
Thank you for your feedback! I really appreciate it!
There is already an open request for this at https://github.com/floccusaddon/floccus/issues/1148
I'm thus closing this in favor of the other request to avoid keeping duplicate requests.

<!-- gh-comment-id:2808873438 --> @marcelklehr commented on GitHub (Apr 16, 2025): Hello @AZeed18 Thank you for your feedback! I really appreciate it! There is already an open request for this at https://github.com/floccusaddon/floccus/issues/1148 I'm thus closing this in favor of the other request to avoid keeping duplicate requests.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#1281
No description provided.