Where the design community meets.
Designer at Shopify Joined almost 6 years ago via an invitation from Greg B.
Helen hasn't posted any stories yet.
Shopify is always hiring great Designers.
Location: Toronto or Ottawa Canada
If you're in for a challenge: we're shaping the future of commerce, not just e-commerce.
If you're in for the team: we have a team of 40-ish Designers. Our developer team is also outstanding. You can learn from amazing people everyday.
If you're in for "culture": you'll be able to find someone here who loves what you love, most likely.
If you like other things like food and unlimited vacation, we got that too: http://www.shopify.com/careers. You can even go home at 5PM if you want to.
Hey, is there a way to RSVP outside of Facebook?
Product designers take in all aspects of design and business strategy to make decisions about how to build a project. The most important aspect for me is the ability to understand business and how design could serve it.
Whereas visual designers are more focused on the look and feel and information architects are more focused on the flow of the content, product designers take in everything and use it to guide the product. I like to think of it as the digital product version of a Creative Director.
While you can argue that all designers should be involved in the business and understand strategy, some designers are simply not good at that nor do they like doing it.
This is a quote about it, from an article about changing from "Like" to heart icons: http://stoweboyd.com/post/33227418776/a-heart-is-different-from-a-star
What's really frustrating with this post is, "Does function triumph design in this case?"
At what point did she actually talk about design?
I see a lot of statements that allude to a service that could potentially be helpful but nowhere on the page does it actually communicate clearly what the company does.
I would probably stay away from just learning a software app or browsing websites to learn design. If you want to learn how to become a better visual designer, the fundamentals of design are what you should brushing up on.
Typography, grids, and colour theory are your basics. Start reading the primers that cover that. Most of what you see on Dribbble, while (may be) very nice, occasionally lacks understanding of the fundamentals and copying them would be a bad way to learn.
You could probably learn a lot from print work alone, even if your work is primarily on the web. Also, the fashion industry tends to be more innovative in it's use of typography and grids, so there is a lot to learn in that space.
UI components aren't a good way to start. Everyone can learn how to make a box. The best designers build systems not boxes.
Yes, it's possible to be a hybrid, but it will take time.
There's an end to this?
You should try all of them and see if it works for you.
I've always done something along the lines of what OOCSS proposes. I think it's a great starting point to learn how to abstract your code and generally reduce the amount of redundant styles you are creating. Additionally, I am a big fan of BEM but in large projects it can overcomplicate things when poorly implemented. If you go too crazy with it, the class names can get overwhelming and hard to read. Everything with a little bit of moderation is a good rule of thumb.
As for SMACSS, I'm not a big fan of it at all. I have tried it on small and large projects. The rules for it are too fuzzy for me and I've found it slows down my production time because of the fuzziness. You may find you like it, but it hasn't worked at all for me.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.