Where the design community meets.
Designer Joined almost 3 years ago
If "Onboarding" is being defined as helping a user learn about how to use your product and make them feel comfortable with the product, then "onboarding" should never stop.
Making "timeless" design decisions that last half a decade are really really hard. I'm 2.5 years into my current role and I'm structuring my design decisions around long term value so we'll see how it goes :)
The people who buy UI kits realise that they can shortcut some of their work (not all of it) by handing over a bit of cash. I haven't purchased a UI kit (yet) but I certainly have purchased resources (graphic assets etc) because I don't have the time to do it and it's not that expensive really. Also, when you hand over money, you can be picky and get something that is really high quality, unlike the gazillion free things that are out there.
Why would you want to make one? Well, if it gets popular you can literally live off the passive income it makes. That's a huge attraction for people. Who wouldn't want to get paid while they're sleeping? Even if it isn't very popular, you can get some extra cash on the side, and if you enjoy make UI kits for fun, it's a hobby that pays you :)
I didn't recognise him :/
"The Google interface looks like the perfect GUI for toddlers" If toddlers can use it then they've created a good interface design for the masses :)
A crucial point the author makes is that notifications should be more opt-in vs opt-out. Finding the preferences is one thing, but if notifications were opt-in, the need to find preferences is greatly diminished.
I really like the idea of opt-in notifications for "non-crucial" type alerts. Having someone like an Instagram photo from 4 years ago probably doesn't need a notification. That should probably be opt-in. But someone sending you a DM should probably be opt-out.
Better defaults is what will work better here, not just making it easy to find preferences/settings. It also means that if you send fewer notifications, the ones that get sent will be more likely to be actioned/opened.
FIGMA HTML CSS PEN/PAPER
That's basically it. There are other 'tools' that are used just to help support this workflow (Preview and Photos app on macOS, Git) but really, it's those 4 things. It's amazing just how far those few tools can take almost any web design.
The article was reasonable until the conclusion. "In summary, functional CSS doesn’t make much sense to me, as a front-end developer." It sounds like a statement speaking on behalf of font-end developers. I work with front-end developers who really enjoy using functional CSS. Functional CSS just doesn't make sense to you, personally.
Also: "I don’t think it’s a coincidence that back-end developers have written most functional CSS libraries." How did they come up with that one? Adam Morse is a designer and tachyons is one of the main functional CSS libraries. I'm active in the tachyons slack channel and there was a poll a while ago showing a reasonable 60/40ish split between people in #general. The fact that functional CSS resonates with designers should be something we should take note of and think about.
Functional CSS is powerful for many reasons. One of them is being able to just "add a bit of padding" or "make that text orange" without having to dig into the CSS files and write new CSS. You can just whack "pa2" or "orange" to the HTML and be done with it. And there's no confusion for the next designer/developer when they edit the HTML.
Sigh I could go on but I'll stop. I think most people who criticise functional CSS should use it for a good 6 months and see how it changes their workflow. That's what I did before forming an opinion.
This 100%. Go right now and look at ANY popular shot. I guarantee 90%+ of the comments are just "Great shot!". There isn't no real sense of community.
But I guess shipping more features will fix this!
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.