I started series where I review Dribbble designs and share what I like, don't like & why. I believe it's great way to refine design feeling
I do this for a long time because in my experience, going there, being conscious about what Dribbble is (a gallery of beautiful designs, many times just to get likes) and being attentive to the designs, exploring why you like them, why you don't like them, thinking about why the decisions were made the way they are made by the designer (and they might be wrong many times!) is a great way to refine you design feeling, taste, and style.
I thought that sharing my own thoughts about the designs might be beneficial for others as well as entertaining. I always like to see how others think about designs, products, etc.
Here is the first review for anyone interested.
Let me know what do you think about the concept. I already got feedback that it's too shallow and unprofessional. So curious to hear any though on it :)
I think one issue I have with dribble is that while it's nice the work is more often than not somewhat detached from reality especially as a small team / Indie hacker.
It's like this idealistic perfect world that you might get to in a year but I can't justify spending a whole lot of time on designs when I have a MVPs to build :p
But if you go in with that expectation it can be a great resource, just about making the tradeoffs work for you.
haha I know, I can relate to that so much. And even if you had the time to design beautiful things, then the devs wouldn't have time to develop it and polish it.
But I still really believe design is one of the cheapest assets you can have to build trust and authority with your users and is worth investing in at some stage.
And last but not least it's good to refine the "design feeling" because you can use it even when using bootstrap or whatever. Like you will then know that this headline should be bigger than this one, and that this layout should be more like that etc.
Does it make sense? haha
Yeah I agree, I was already talking from a dev perspective because that's my background hehe but you're right that there's two major issues when you don't prioritize design at all:
It's never wrong to invest in design I'd say if you don't go overboard and find the right tradeoffs.
I'm always trying to apply the Pareto principle wherever I can and design is a good fit for that I think.
Just too bad I can't design lel.
It's something new, to me... it seems pretty interesting.
You could also try reviewing stuff from code pens, or interesting Github projects.
That's actually a great idea! I was thinking about reviewing products on PH weekly with the team. But I will nudge my two technical co-founders to think about doing code pens and github projects! Thanks!
I like it!
Good luck.
Interesting video Johan!
Thanks for the kudos Lukey!