Where the design community meets.
New York City http://mattaningram.com Joined over 5 years ago
I'm enjoying the Design Social Club slack channel: Slack Invite Link
Please, please, please learn from Google Inbox. So many new email clients come out claiming to be a new way to do email, and in the end they are almost all identical in general layout (three columns!) and features.
Google Inbox actually refined the email management experience, it didn't just add a million ways to view and search stuff. For example when I pinned/starred items and then archived the grouping they were in, only the non-pinned items got archived. Of course Gmail did not implement this when Inbox shut down and now Gmail is a shitshow.
Another one is grouping items by date instead of just having this impenetrable infinite list. It was nice being able to scan everything I got in the last week and archive it quickly, it narrowed down the cognitive load of what I had to look at before making the decision to pin, archive, reply, etc.
It continues to boggle my mind that company after company fail at actually improving email when Google Inbox had it right for years already (and were not just targeting business users!).
Ew, that answer to the low contrast situation. I've always gotten an icky vibe from Superhuman, and the recent privacy drama around them and the answer that it is low contrast to be "sexy" makes me dislike them so much more.
K however are widely used in just about any list based app for going up and down. It's not unique to Superhuman and has been around for a long time. Also the behavior of jumping to another email without going back to the inbox is standard across most email clients I've used, not sure how that is a selling point for Superhuman.
The one new feature appears to be sending by timezone, otherwise it looks like Superhuman is just hype with nothing really behind it. Google Inbox was better than this.
Same here, I'm also excited for the release of Modulz and Hadron as competitors.
Unfortunately I missed the Modulz alpha/beta, but I’m worried it’s not exactly the tool I’m looking for. I’ve been talking to the creator on Twitter and it seems like he is against exposing the HTML and CSS to designers and instead basically just giving them a variety of pre-built components and modules and tokens they can theme.
Modulz, Hadron, Brook.io, Webflow (sort of but demonstrates how powerful this can be), handoff.design, and many others.
The counter argument I hear is that people feel they will lose creativity if they can’t position items anywhere they want. But this just tells me they don’t know CSS because position: absolute and position: fixed let you do exactly that.
My only fear is these tools will over abstract away from HTML and CSS instead of being a means to teach designers these useful skills. One of the reasons we have such a big discussion about design systems right now is because designers AND developers refuse to properly learn HTML and CSS.
Sketch and Figma are slowly recreating every feature of CSS (not perfectly) because they chose to build their own rendering engine instead of just using HTML and CSS.
This causes so many issues with developer handoff. I see product designers switching to an HTML/CSS based tool over the next couple of years instead of sticking with Figma/Sketch.
You will get all the other benefits that Figma/Sketch provides, while having all the benefits of a box-model right out of the box.
Show me a complex data web app that has form or input design which is "outside the box". It doesn't really exist because it makes it a lot harder to use.
Designers work on a wide range of different things. If they are working on a marketing or advertising agency gig, then sure thinking outside-of-the-box might be appropriate (and a design system is not really needed), but for working on a complex product in-house, then you sometimes need to be more conservative in how you implement things and want to stick to a repeatable and documented pattern.
The point is not to exactly emulate the web, the point is to have basic features like wrappers resizing based on content, and if you happen to be designing for the web you also get features that bring it closer to that medium.
Designing with HTML and CSS will get you a more complete set of design tools for native app design than any of the existing drawing tools give you. I sometimes design for native apps with HTML and CSS written by hand because of the limitations of tools like Figma and Sketch.
You get all the freedom of those drawing tools (
position: fixed or
position: absolute let you place an item essentially anywhere) while also having all the benefits of a box-model that brings you closer to the actual experience of web AND native.
Until design tools have a box-model concept they are going to be fundamentally underpowered compared to HTML and CSS.
I love Figma, but I see it getting outpaced by a tool built on web technologies in the next couple of years.
The problem is a lot of the design tools going that direction are all working on trying to make production-ready code which I think is skipping too many steps.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.