Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Making Google Sans Flex

design.google

Post reply on HN
Print view View original

51–60 of 97 posts

Re: Making Google Sans Flex

#51

Post by torben-friis »

albert_e wrote: post #33
torben-friis wrote: post #6

There is something about the page that makes me dizzy on mobile. I’m not sure if it’s a subtle animation but I get the feeling of things moving/deforming while I read.

>> Product lockups didn’t match the new Google logo >> The 2015 logo redesign was a smashing success. Watch the distance between these two lines. It changes to more compact - subtly- as we scroll it into view (am on mobile- chrome on android). Feels like the page is trying to do too much fancy stuff. I cant take their blog seriously if this is their idea of good design and user experience.

Ugh, you’re right. It’s like a parallax for the titles. Not really a good impression.

Re: Making Google Sans Flex

#52

Post by jorvi »

TekMol wrote: post #10

Since even after 2 hours nobody is discussing the actual font, let me tell you what comes to my mind when I read anything about Google and design: They got phone design right. I just can't get my head around it that even Apple, which is supposed to be THE design company, is making phones that can't lay on a table without wobbling like a barstool on a crooked floor. It just feels so broken to me. So detrimental to my…

I'd rather have a wobbly phone (how often do you push on your screen when it is flat on the table?) and a proper OS than a proper phone and a wobbly OS.

Gesture navigation on Android was introduced half a decade ago and it is still broken. In most apps my edge swipe to pull out a drawer or a swipe on the right side to 'forward' are still detected as back button swipes. Editing details at the edge of a photo often gets detected as a back button swipe. Ridiculous.

Re: Making Google Sans Flex

#53

Post by jorvi »

pityJuke wrote: post #35
guessmyname wrote: post #31

Is there a monospaced version of this font? Pretty much every font I try has one or two things that bug me. I’ve spent the last ten years making my own, first in FontForge, now in Glyphs.app, but it’s incredibly time-consuming. I’ll work on it for a while, then give up for months, delete everything, switch to a different font, use it for a few days, start hating it… and end up back at making my own font again. This c…

From TFA: > Google Sans Mono was created in 2020 to support contexts that needed fixed-width characters for editorial design, at medium and large text sizes. Despite this, it soon got its first big product integration, replacing Roboto Mono in Google Chat. The only problem? Developers hated it. [...] > Recognizing this critical need, a dedicated effort was launched to craft Google Sans Code, a monospaced typeface spe…

What is that abomination of a curly brace. It looks like a squiggle that someone had to jot down in a rush.

https://fonts.google.com/specimen/Google+Sans+Code

Re: Making Google Sans Flex

#55

Post by Angostura »

skydhash wrote: post #41
makeitdouble wrote: post #29

Earlier quoted context omitted.

> Perfectly usable without ugly case. Why would you buy an ugly case and not a clean and well designed, functional one ? If you liked the original iPhone design, getting a rounded and hand fitting case would be the go too IMHO (on the size difference, there's no way out at this point)

My previous phone was the iphone 8. It’s trully a world of difference in usability compared to the iPhone 13 I’m using now. I have big hands, so I can ise the latter one-handed, but a lot of people I’ve seen don’t.

Why not the excellent iPhone 13 Mini?

Re: Making Google Sans Flex

#56

Post by mapt »

TekMol wrote: post #10

Since even after 2 hours nobody is discussing the actual font, let me tell you what comes to my mind when I read anything about Google and design: They got phone design right. I just can't get my head around it that even Apple, which is supposed to be THE design company, is making phones that can't lay on a table without wobbling like a barstool on a crooked floor. It just feels so broken to me. So detrimental to my…

Some of these companies are now designing the phone on the assumption you're going to case it. No other reason to make a Pixel camera bump w/ scratch-vulnerable screen stick out so far.

Re: Making Google Sans Flex

#57

Post by _fzslm »

It's a really pretty, humanist font, and those tend to be my favourite fonts. I was never the biggest fan of the grotesk-style Roboto/Inter/Univers, especially in the context of a user interface, which should feel a little bit friendlier imo.

I use Avenir on my Samsung phone, which is also pretty nice. I like Circular, Proxima Nova and Frutiger too, but they are all very expensive.

This font is free, flexible and genuinely really nice to look at. It's a good day for font nerds like me.

Re: Making Google Sans Flex

#58

Post by Y-bar »

jorvi wrote: post #52
TekMol wrote: post #10

Since even after 2 hours nobody is discussing the actual font, let me tell you what comes to my mind when I read anything about Google and design: They got phone design right. I just can't get my head around it that even Apple, which is supposed to be THE design company, is making phones that can't lay on a table without wobbling like a barstool on a crooked floor. It just feels so broken to me. So detrimental to my…

I'd rather have a wobbly phone (how often do you push on your screen when it is flat on the table?) and a proper OS than a proper phone and a wobbly OS. Gesture navigation on Android was introduced half a decade ago and it is still broken . In most apps my edge swipe to pull out a drawer or a swipe on the right side to 'forward' are still detected as back button swipes. Editing details at the edge of a photo often ge…

The wobbling is the worst part of the hardware on my iPhone mini, annoys me probably more than fifty times per week.

Because I often unlock it when it is on the desk I also miss Touch ID a lot, because with Face ID I also have to lean forward every time for it to recognise me.

Re: Making Google Sans Flex

#59

Post by maaarghk »

jorvi wrote: post #53
pityJuke wrote: post #35

Earlier quoted context omitted.

From TFA: > Google Sans Mono was created in 2020 to support contexts that needed fixed-width characters for editorial design, at medium and large text sizes. Despite this, it soon got its first big product integration, replacing Roboto Mono in Google Chat. The only problem? Developers hated it. [...] > Recognizing this critical need, a dedicated effort was launched to craft Google Sans Code, a monospaced typeface spe…

What is that abomination of a curly brace. It looks like a squiggle that someone had to jot down in a rush. https://fonts.google.com/specimen/Google+Sans+Code

Hmm, my first reaction was the same as yours. But I have quite bad eyesight and looking at the "regular 400 at 16px" example on the page reminded me that I definitely sometimes find myself squinting trying to work out whether a character is a parenthesis or a brace (Droid Sans Mono). So I suppose it'd probably be quite helpful to have a brace that's very visually distinct from parenthesis even if it's not particularly pretty on its own.

Re: Making Google Sans Flex

#60

Post by IAmBroom »

jorvi wrote: post #53
pityJuke wrote: post #35

Earlier quoted context omitted.

From TFA: > Google Sans Mono was created in 2020 to support contexts that needed fixed-width characters for editorial design, at medium and large text sizes. Despite this, it soon got its first big product integration, replacing Roboto Mono in Google Chat. The only problem? Developers hated it. [...] > Recognizing this critical need, a dedicated effort was launched to craft Google Sans Code, a monospaced typeface spe…

What is that abomination of a curly brace. It looks like a squiggle that someone had to jot down in a rush. https://fonts.google.com/specimen/Google+Sans+Code

Oh, it can't be that ba.... OMG KILL IT WITH FIRE! WE HATES IT!

--my actual reaction

Post reply on HN