3 ms·
I dislike the redesign, some parts at least. The bottom navbar particularly irks me. It's a navbar a la iOS, completely nonstandard for Android, where the slidi
by andrepd 9y ago
I dislike the redesign, some parts at least. The bottom navbar particularly irks me. It's a navbar a la iOS, completely nonstandard for Android, where the sliding sidebar is preferred to navigate between sections of the app.
The previous app had perfect compliance with the standard interface guidelines, no unexpected custom elements. This version has them by the truckload. It was much cleaner before, so this feels like a regression (even though I like some parts, such as the "Latest" screen. EDIT: The "Categories" screen is very pleasing and navigable too, were it not for the floating Search button senselessly blocking parts of the screen. I've always hated that trainwreck of an element. Particularly needless in this case: search belongs on a searchbar on the top (most usability and least surprise).
- app4soft 9y agoF-Droid could be improved in next versions, if you will send your feedback (issues, bug reports and feature requests) directly to F-Droid Team ;)
- hiq 9y agoOP's pull request would be to basically revert all commits since last version, I don't think it's helpful. As OP, I was satisfied with the original design, and I really don't want the new one, so I'll keep an older version for as long as I can.
- s73ver_ 9y agoThe bottom navbar has been part of the Material guidelines for a while now. Sliding sidebars are bad because of the challenges they pose for discoverability. https://material.io/guidelines/components/bottom-navigation.html https://material.io/guidelines/components/bottom-navigation....
- on_and_off 9y agoThey are also on top ... with our huge phones, it is a pain to reach. Anecdotally, resources wise it makes me happy to do not have sliding so I don't need to maintain 3 pages in memory
- pserwylo 9y agoWe are aware that it is not to everyone's liking, but we've done our best to modernise and appeal to a wider audience, all the while conducting UX tests and responding to feedback. One thing we'd really love is for there to be an "F-Droid Light" which forks the previous stable release, strips it down, and offers the essentially app store experience with no bells and whistles on the widest range of devices [0]. Alas we are a small volunteer team and this would add a maintinence burden we can't seem to muster at this point. [0] - https://gitlab.com/fdroid/fdroidclient/issues/48 https://gitlab.com/fdroid/fdroidclient/issues/48
- hiq 9y agoIs anything bad going to happen if we stick to a previous version, assuming that there is no security vulnerability in those? I plan to do that, because of the new design. If there's no changes in protocol it should be OK I guess.
- pserwylo 9y agoWe added a new metadata format for this release to deal with translatable metadata, feature graphics, screenshots, etc. The server tools output the old and new metadata to the repository webroot though, so the old version will still be supported for some time. I'm not aware of any plans to completely deprecate and remove it.
- hawski 9y ago> The bottom navbar particularly irks me. It's a navbar a la iOS, completely nonstandard for Android, where the sliding sidebar is preferred to navigate between sections of the app. Have you seen the YouTube app lately?
- eighthave 9y agoWe actually did a lot of work to make sure that the new UI fit into the design guidelines and actual UI practice. Indeed, we tried to make it feel more natural for more users. Of course, its a big change from the old UI, so that's a big change. Plus its free software, so people who like the old UI can maintain it. If you are interested in learning more about our design process, you can see it in our issue tracker: https://gitlab.com/fdroid/fdroidclient/issues?milestone_title=0.103+-+UX+Overhaul&page=2&scope=all&sort=created_date&state=closed https://gitlab.com/fdroid/fdroidclient/issues?milestone_titl...