That’s honestly something I don’t entirely get in the case of Sync. Like, there is nothing wrong with allowing users to tweak things, but Sync is like, really heavy on the Material Design 3, you look at it, and it is undoubtedly M3. Yet, there is always something odd about the way it uses it.
The main FAB is also weird, as it isn’t the primary action of the screen, it just opens a bottom sheet to bring more “actions” (some of which are destinations…)
Like, Sync is a very good app, but it has a few odd things that are really weird.
I don’t know enough about M3 to really comment on that, but when he updates things we cry about the changes. It looks like material design is 9 years old. He’s been developing Sync for, what, 12 years and a bit? So we’ve probably requested a lot of stupid shit, but he’s pretty good about listening. I know I was unhappy with some of the major UI updates and was happy he let me choose.
I’m not super sure what you’re complaining about with the navigation bar. It’s well within the realm of what Google uses them for. Go look at the YouTube app for example. It has a button on the navigation bar that opens a bottom sheet as well. I’d argue Sync’s use of it is more in-line with the guidelines than YouTube is, since the sheet for exploring is closer to a destination than a sheet for uploading different kinds of videos. The only odd thing is being able to convert the FAB into a navbar button, but at least it’s an option and not a requirement.
YouTube Music and Google Podcasts also have an “Explore” option on the navbar, they just open a page instead of a bottom navigation. He probably could convert that sheet into a page to make it more consistent, but it’s probably a sheet for usability reasons.
I think the point about the FAB is good in theory when talking about what the material guidelines say, but so few apps actually use the FAB, and I think Sync’s implementation which allows for such robust customization is a good and fairly intuitive use of it, even if it doesn’t exactly follow every guideline. It still does allow you to pick one primary action for it. It just also gives you more options.
That’s honestly something I don’t entirely get in the case of Sync. Like, there is nothing wrong with allowing users to tweak things, but Sync is like, really heavy on the Material Design 3, you look at it, and it is undoubtedly M3. Yet, there is always something odd about the way it uses it.
Take for instance, the Navigation Bar, under Material Design Guidelines it is meant for destinations. And yet, on sync it offers:
The main FAB is also weird, as it isn’t the primary action of the screen, it just opens a bottom sheet to bring more “actions” (some of which are destinations…)
Like, Sync is a very good app, but it has a few odd things that are really weird.
I don’t know enough about M3 to really comment on that, but when he updates things we cry about the changes. It looks like material design is 9 years old. He’s been developing Sync for, what, 12 years and a bit? So we’ve probably requested a lot of stupid shit, but he’s pretty good about listening. I know I was unhappy with some of the major UI updates and was happy he let me choose.
I’m not super sure what you’re complaining about with the navigation bar. It’s well within the realm of what Google uses them for. Go look at the YouTube app for example. It has a button on the navigation bar that opens a bottom sheet as well. I’d argue Sync’s use of it is more in-line with the guidelines than YouTube is, since the sheet for exploring is closer to a destination than a sheet for uploading different kinds of videos. The only odd thing is being able to convert the FAB into a navbar button, but at least it’s an option and not a requirement.
YouTube Music and Google Podcasts also have an “Explore” option on the navbar, they just open a page instead of a bottom navigation. He probably could convert that sheet into a page to make it more consistent, but it’s probably a sheet for usability reasons.
I think the point about the FAB is good in theory when talking about what the material guidelines say, but so few apps actually use the FAB, and I think Sync’s implementation which allows for such robust customization is a good and fairly intuitive use of it, even if it doesn’t exactly follow every guideline. It still does allow you to pick one primary action for it. It just also gives you more options.