Currently, it is difficult for users, developers, and designers to instantly distinguish between fonts created in-house by Google (like Roboto, Noto, and Product Sans) and third-party or community-contributed fonts hosted on Google Fonts.
I propose that Google adopts a standard suffix naming convention for all first-party fonts designed/made by Google, similar to how Microsoft utilizes the "MS" suffix (e.g., Comic Sans MS, Trebuchet MS) to denote proprietary or core system fonts.
Currently, it is difficult for users, developers, and designers to instantly distinguish between fonts created in-house by Google (like Roboto, Noto, and Product Sans) and third-party or community-contributed fonts hosted on Google Fonts.
I propose that Google adopts a standard suffix naming convention for all first-party fonts designed/made by Google, similar to how Microsoft utilizes the "MS" suffix (e.g., Comic Sans MS, Trebuchet MS) to denote proprietary or core system fonts.
Potential suffix ideas:
-> AB (for Alphabet) -> e.g., Roboto AB, Noto Sans AB
-> LS (for Larry & Sergey) -> e.g., Roboto LS, Noto Sans LS
Keeping the names as they are, which forces users to dig through metadata files or external documentation to verify if a font is an official Google-engineered product.
Adding a suffix would elevate Google's design branding, streamline font management in design software drops, and give clear, immediate recognition to first-party typography assets.
-> AB (for Alphabet) -> e.g., Roboto AB, Noto Sans AB
-> LS (for Larry & Sergey) -> e.g., Roboto LS, Noto Sans LS
Keeping the names as they are, which forces users to dig through metadata files or external documentation to verify if a font is an official Google-engineered product.
Adding a suffix would elevate Google's design branding, streamline font management in design software drops, and give clear, immediate recognition to first-party typography assets.
Currently, it is difficult for users, developers, and designers to instantly distinguish between fonts created in-house by Google (like Roboto, Noto, and Product Sans) and third-party or community-contributed fonts hosted on Google Fonts.
I propose that Google adopts a standard suffix naming convention for all first-party fonts designed/made by Google, similar to how Microsoft utilizes the "MS" suffix (e.g., Comic Sans MS, Trebuchet MS) to denote proprietary or core system fonts.
Currently, it is difficult for users, developers, and designers to instantly distinguish between fonts created in-house by Google (like Roboto, Noto, and Product Sans) and third-party or community-contributed fonts hosted on Google Fonts.
I propose that Google adopts a standard suffix naming convention for all first-party fonts designed/made by Google, similar to how Microsoft utilizes the "MS" suffix (e.g., Comic Sans MS, Trebuchet MS) to denote proprietary or core system fonts.
Potential suffix ideas:
-> AB (for Alphabet) -> e.g., Roboto AB, Noto Sans AB
-> LS (for Larry & Sergey) -> e.g., Roboto LS, Noto Sans LS
Keeping the names as they are, which forces users to dig through metadata files or external documentation to verify if a font is an official Google-engineered product.
Adding a suffix would elevate Google's design branding, streamline font management in design software drops, and give clear, immediate recognition to first-party typography assets.
-> AB (for Alphabet) -> e.g., Roboto AB, Noto Sans AB
-> LS (for Larry & Sergey) -> e.g., Roboto LS, Noto Sans LS
Keeping the names as they are, which forces users to dig through metadata files or external documentation to verify if a font is an official Google-engineered product.
Adding a suffix would elevate Google's design branding, streamline font management in design software drops, and give clear, immediate recognition to first-party typography assets.