Took me so long to realise that "Google Sans Flex" is the name of the font. I read the title as "creating Google without using Flex [whatever that is]"
Making Google Sans Flex
71–80 of 97 posts
Re: Making Google Sans Flex
#72Since 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…
Of all the controversial design choices, I think Apple got this one right.
I do not care if my phone wobbles when flat on the desk. I don’t use my phone like that. It’s in my hand if I’m using it.
I use my phone camera sparingly, but when I pull it out I want it to work very well. And it does. If it takes a little bump out to fit better optics then I don’t care in the slightest.
> Google phones tackled it with an elegant solution. Thanks for that. I wouldn't know what phone to use if Pixels didn't exist.
Making your entire phone choice revolve around the shape of the camera island is the oddest top priority I’ve heard yet, but I’m glad you found one that works for you.
Re: Making Google Sans Flex
#73 > Product teams eagerly adopted Google Sans and Google Sans Text but soon highlighted a new issue: Billions of people around the globe use non-Latin scripts like Arabic, Chinese, ... The effort was monumental. It meant meticulously crafting hundreds of thousands of new ... from the flowing curves of Arabic to the complex strokes of Japanese and the distinct ...
What I know about CJK font is that one does not simply make a CJK font: they're nearly always made by modifying something existing. Even Google's previous attempt at it was made by a joint multi-year project with Adobe and bunch of experts from various companies tasked to fix what are locally sticks out for each relevant regions without breaking overall theme to make a total of 4-5 language specific fonts with major bugfixes happening for few times over couple years.That above quoted part reads to me like "oh and there's of course the fusion version of this micro nuclear because that's important", which makes little sense, so I searched around a bit just in case, and there doesn't seem to be non-Latin versions of Google Sans. The credit section does not mention obvious source of easily licensable CJK font other than "U+ Type", either.
My assumption would be that either they made an assumption that a font in CJK can't take that long relative to font in Latin, or they couldn't get one in favorable terms and the full version is proprietary. Or is it really coming later? That would be interesting if that's the case.
Re: Making Google Sans Flex
#74Cool 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
Re: Making Google Sans Flex
#75Is 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…
Re: Making Google Sans Flex
#76A 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?
Re: Making Google Sans Flex
#77Earlier quoted context omitted.
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…
2) disregarding another blatant discrimination of left-handed users: I switch a couple times per week between android and iOS devices for various reasons and the android UX is so janky and unintuitive it hurts - it might just be my particular device and it’s much better in other cases.
This might be extremely polarising but I agree with GP.
Re: Making Google Sans Flex
#78Since 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.
How about making the phone more durable by adding 1 mm to its thickness, so that a 50 gram, 4 mm thick case won't need to be added.
Re: Making Google Sans Flex
#79Earlier quoted context omitted.
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 is the default on all modern Android flavors and the overwhelming majority (>90%) of users sticks with defaults. It is likely Google is going to deprecate the navigation bar within a couple of Android versions.
> Apple iOS: the close/back button is usually on the top left corner, unreachable
You clearly never used iOS, because you just backswipe. You rarely if ever touch back buttons.
Not that I disagree although you're fighting the wrong fight. The big problem is controls being on the top instead of the bottom. Neither Apple nor Google has attempted to fix this, only Samsung partially has with OneUI. And they can't force developers to adhere to "content top, controls bottom". Ironically enough Apple had this fixed until iOS.. 12? From 7-12, the control center was at the bottom. All they had to was move the notification centre there and figure out a way to make it compatible with a gesture bar.
> right-handed users that only constitutes 90% of people
People tend to one-hand their phone with their non-dominant hand to keep their dominant hand usable.
> You should take a few steps back before displaying publicly polarizing opinions and maybe nuance your words a bit.
I use and develop for both platforms. You just sound like an angry, unknowledgeable fanboy.
Perhaps take heed to your own advice :+)
Edit: if you want an example of something that Android does way better: notification management via notification categories. I get to disable stupid promotional or "typing.." notification categories from an app, whilst maintaining functional ones. iOS should take a page from Android there.
Re: Making Google Sans Flex
#80Since 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 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 sense of aesthetics. Of all the controversial design choices, I think Apple got this one right. I do not care if my phone wobbles when flat on the desk. I don’t use my phone…