Google's design language is pretty unsurpassed, well documented and very user-friendly, thanks also to a ton of research that has been done in connection with Android, I guess.
So I see nothing wrong with him using that, in fact it would be a major factor for me personally in considering any Google service alternatives.
Keeping the switching barrier low is key for successful and widespread user adoption.
I actually think bad UI design is THE single greatest impediment for widespread adoption of free or open-source software imho. A lot has been written on that subject but I think the trope is "open-source developers cannot create good UIs". It is an old but well-accepted axiom, same as "Poland cannot into space", and it seems everyone adheres to it... ;-)
So using an established and "known good" design language is in fact ingenious.
So I see nothing wrong with him using that, in fact it would be a major factor for me personally in considering any Google service alternatives.
Keeping the switching barrier low is key for successful and widespread user adoption.
I actually think bad UI design is THE single greatest impediment for widespread adoption of free or open-source software imho. A lot has been written on that subject but I think the trope is "open-source developers cannot create good UIs". It is an old but well-accepted axiom, same as "Poland cannot into space", and it seems everyone adheres to it... ;-)
So using an established and "known good" design language is in fact ingenious.