Revert back UI changes

[kalekad]

Android v5.9.0

Moving the static search field to a bouncing icon that doesn't respond to the back gesture when expanded is not a good idea.
And adding Pull down and Push up buttons next to the Sync button just greatly increases the chance that the user will lose their bookmarks.

I think the account name has been added to the main screen. I assume this is useful when there are multiple accounts. If there’s only one account in the app, I wouldn’t display anything.

[github-actions]

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! 💙

[marcelklehr]

Hello @kalekad
Thank you for taking the time to give feedback!

Moving the static search field to a bouncing icon that doesn't respond to the back gesture when expanded is not a good idea.

Good point! I can make it respond to the back gesture.

And adding Pull down and Push up buttons next to the Sync button just greatly increases the chance that the user will lose their bookmarks.

I disagree. I think the push and pull buttons are needed occasionally, and they were previously hidden behind a long press on the sync button and were thus hard to discover and it even easier to lose bookmarks when you wanted to sync down for example but pressed not long enough, causing a normal sync instead.

I think the account name has been added to the main screen. I assume this is useful when there are multiple accounts. If there’s only one account in the app, I wouldn’t display anything.

Indeed, that's a good idea!

Thank you for your input!

[kalekad]

I disagree. I think the push and pull buttons are needed occasionally, and they were previously hidden behind a long press on the sync button and were thus hard to discover and it even easier to lose bookmarks when you wanted to sync down for example but pressed not long enough, causing a normal sync instead.

Well, even if they are sometimes useful, that doesn't mean they have to stay where they are. What if they were moved to Settings? And the static search field could be brought back.

[marcelklehr]

Can you describe in more detail your perspective? Why was the directly visible search input box better than the search button that displays and immediately focuses that same box? is it about the push/pull buttons being to prominent for their limited use and danger?

What would you say to the following design?

Current design	Proposed design	Proposed design
-	-	-