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

61–70 of 97 posts

Re: Making Google Sans Flex

#61

Post by assimpleaspossi »

mapt wrote: post #56
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.

If a phone needs a case, then phones should be sold with a case included. I hate cases and have never put one on my phone--and have never had a phone break or crack.

Re: Making Google Sans Flex

#62

Post by MoonZ »

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…

1°) Gesture navigation is entirely optional.

2°) Android followed UX/UI 101 about where to put frequently used buttons: where you can reach them with your thumb. Basic design, right ? Apple iOS: the close/back button is usually on the top left corner, unreachable by right-handed users that only constitutes 90% of people, number about the same in all countries and cultures. That's only one example, but that bag where it comes from is deep.

You should take a few steps back before displaying publicly polarizing opinions and maybe nuance your words a bit.

Re: Making Google Sans Flex

#63

Post by otabdeveloper4 »

grougnax wrote: post #23
the_gipsy wrote: post #22

Cool work on a font, but this page is proof that google is turning the web into some kind of JSON for their app, Chrome. Extremely sluggish on non-Chrome. Starts with a black blank empty page. Fans spinning. Takes way too long to load for just some text and some videos. Clicking a link does some SPA magic that takes me to another black blank page, and takes ages to load. Clicking back doesn't work anymore. I need to…

Just use Chrome on a MacBook Pro M4 like everyone else

No thanks, I'm good.

Re: Making Google Sans Flex

#64

Post by lesuorac »

the_gipsy wrote: post #42
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…

The irony is that you're still not discussing the font

That's his point. Since nobody else is, he's not going to either.

Re: Making Google Sans Flex

#65

Post by lesuorac »

chippiewill wrote: post #47
philipwhiuk wrote: post #27

> It’s one of the most-served fonts on the internet, clocking in at some 120 billion font requests a month. Isn't this an incredible waste of bandwidth? Surely people only need the font once.

Browsers made a fundamental change a while back to not share caches between origins because caching it became a side-channel to detecting if someone had visited it before. So now if two different websites embed the same remote font then visitors will have to download it separately for both sites. https://developer.chrome.com/blog/http-cache-partitioning

Surely one of the most popular browsers in the world could ship with some commonly requested fonts and all you'd learn is that they were using chrome which the user-agent said anyways.

Re: Making Google Sans Flex

#66

Post by lesuorac »

deafpolygon wrote: post #17

> The majority of how people experience the Google brand is through typography Ok, who wants to tell them?

Unless you experience Google through the assistant you experience through the typography.

You read search results that are rendered via typography.

Re: Making Google Sans Flex

#67

Post by silon42 »

IAmBroom wrote: post #60
jorvi wrote: post #53

Earlier quoted context omitted.

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

Mine: It's not that ba... oops, I have custom fonts disabled...

...yikes...

...goes back to disabling custom fonts in browser.

Re: Making Google Sans Flex

#68

Post by blululu »

vbezhenar wrote: post #20
planb wrote: post #2

A bit OT: What's up with the mouse pointer on that page? Why on earth would a site that has "design" in it's domain name change my mouse pointer to a finger-sized circle blob on my 4K desktop screen?

Cursor feels terrible. Native cursor moves very fast. This cursor does not feel native and moves very slow and sluggish. Do they paint it with Canvas or something like that?

I recall that it is a Div that uses the css invert property, but this can be cpu intensive depending on how it is moved (transform uses gpu I think but position is cpu)

Re: Making Google Sans Flex

#69

Post by techwizrd »

the_gipsy wrote: post #22

Cool work on a font, but this page is proof that google is turning the web into some kind of JSON for their app, Chrome. Extremely sluggish on non-Chrome. Starts with a black blank empty page. Fans spinning. Takes way too long to load for just some text and some videos. Clicking a link does some SPA magic that takes me to another black blank page, and takes ages to load. Clicking back doesn't work anymore. I need to…

I had no issues using Firefox on a 2021 M1 Pro or my Framework 13. Reader mode does not work, however.

Re: Making Google Sans Flex

#70

Post by RankingMember »

vbezhenar wrote: post #19
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…

Original iPhone got design right. I don't think there's a single modern smartphone that I like. My latest favourite smartphone was iPhone 4S. No camera bump. Perfect size, fits well in my hand, operable with one thumb. Perfect display size, enough to present all information I need. Perfectly usable without ugly case.

My only beef with that one was the slippery soap-bar edges if used without a case. Otherwise, yep, perfect size, disappears in pocket.
Post reply on HN