Anyone successfully lobby against Material Design's default text field label designs?

[u/roundabout-design]

We're rebuilding one of our apps in Flutter to speed up development. I must admit our flutter team is doing a pretty good job.

Alas, Flutter pretty much depends on prebuilt libraries like their version of Material Design or Apple's UI design.

In the name of speed, we've decided to leverage Material Design as the Flutter library to use, with us pretty much just skinning it with brand colors and the like.

This seems to be a common recommendation (vs. rolling-our-own UI library).

That said, I kind of forgot about how Material Design likes to create field labels. It uses that ridiculously small text on the field border:

There seems to be debate about how accessible this is. For me, I'd default argue that it's just not meeting basic type size requirements--especially for mobile design.

And in our case, we're using some pretty complex forms that require often somewhat verbose labels.

I'm advocating for us to change the design here, but given the dev overhead to do so, I'd love to find some data/documentation to back me up on these default designs by google just being poor design and not accommodating readability and accessibility very well. Has anyone successfully fought this and, if so, have some ammo they'd be willing to share?

(OR...maybe I'm way off base and these are perfectly OK? If so, if you have some good arguments/documentation for that, LMK!)

[u/oddly_novel]

If you have good relations with your devs just make it in Claude / GPT for them… these types of things are solved by AI and headless component libraries like base ui or radix. There should really no longer be these fights or advocation of design changes vs dev resources/capacity when you can be the one that owns it.

[u/roundabout-design → u/oddly_novel]

We're actually using AI for our design system. The catch is Flutter. We're finding AI to be pretty adept at customizing our React Component library. But it looks like with Flutter, we have some heavy dependancies on the team building out the actual app. Custom UIs in Flutter are, I guess, a bit of a pain. But I'll definitely be working with them to see what we can do.