My iteration philosophy though is to release first, get feedback, then look at where something custom might most benefit my end users, rather than focus on the customization up front. Sometimes the component just doesn't matter as much as I thought it would, so the custom work doesn't matter. Other times it ends up being interacted with a ton, so optimizing the experience makes a lot of sense.
Would you mind providing more concretely which components are insufficient? At a minimum, this would help me to anticipate potential hot spots during my own Vuetify adoption. Further, are your customizations creating value that maybe ought to be PR'd to their projects? Do you follow the same component design for your customs?
The table components are good but not great. Find for some basic data displaying, but lack the flexibility I’m looking for in more complex views. There are some other options out there to solve this problem set though, like hot table.
I don’t use their slider component as it’s not featurful enough for me.
I use a different date and time picker.
Their select box input has some good qualities but also some issues with usability on mobile. You can work around them but it’s clunky.
As for me pushing back to them, I don’t think I will. My UI skills leave much to be desired. I’ve seen what skillful front end developers look like and I am not in their class. I’ll leave it to the experts :)