On the more philosophical size, The Shape of Design by Frank Chimero is a must read. My absolute favorite technical design book is Grid Systems in Graphic Design by Josef-Müller Brockmann. What books can you recommend, regarding design? I think it was much more of an exercise in patience, exploration and iteration than some sort of magic insight. He made hundreds of coded iterations before landing on the grid you know today. There are more where some things are just stripes on the page. There are some where the images are square. There are explorations that are a list of images. The early explorations that Evan had done make no assumptions though. Both of those two were very designer-heavy and didn't have mass market appeal. The latter is the closest thing you'd find to Pinterest. When you think about FFFound and Dropular, the former was just a bunch of images sequentially on a page. If you think about sites like Facebook and Twitter, those were text-heavy streams with the occasional photo. I think that at least initially, Pinterest was considered unique because it was very, very visual and organic in a way that many other websites at the time were not.
My first project was the mobile website (which sadly is still online). When I joined, he was working on a visual refresh of the website, which I helped out on. He did all of the original design and systems work probably about a year or more before I joined. I was the first product design hire, which is different from the first product designer, who would be Evan Sharp, our cofounder. This isn't the last you'll hear from me about this. I have a whole essay on this waiting for me to have time to edit and design some stuff in Editorially.
We're good enough at this software thing that it doesn't have to be like that. There are tools that let you do information architecture, but you can only get to real data and behaviors in code. But you have to jump between programs to access different parts. We have the first in tools like Photoshop, Sketch, After Effects, Flinto, Keynote, etc. The ability to define behaviors and information architecture.Advanced drawing and animation capabilities.In a nutshell, a modern design tool needs to have three things: Albeit new and unhindered by history like Photoshop, Sketch is not on trajectory to be the digital design tool of the next two decades as Photoshop has been. I don't think either is a viable long-term solution. I think Photoshop sucks, but its a lot more capable than Sketch. I have a LOT of opinions on design tools. I make a lot of prototypes, but I probably have one of the higher code competency levels on the team. Historically its been pretty difficult to develop on our platform if its not your full-time job, but its getting easier and as a result, more designers have been coding. Many, but not all, of our designers code. In a few release cycles, we're planning on trying to switch to Layervault for some of the collaboration and delivery stuff. It sucks, and I'm looking for a replacement. The design org uses Basecamp to share progress and gather feedback. It's not the best, but it works better than anything else out there. The organization uses Asana for tasks and bugs.
I've seen people use Balsalmiq and Illustrator for wireframes, but I don't wireframe often so I can't talk too much about that.
There's a few Sketch outliers, but we're weeding that out because it isn't a viable tool for the work we do right now and it's more important that everyone be able to easily use anyone else's files.
0 kommentar(er)
