This big pink bbbeauty is one of several images used by our integration tests to verify the different workflows (crop v. no crop, whether to show the @2x option, whether to default to 400x300 v. 800x600, etc) that run based on the size of the original shot file.
In this case, the original shot is 1000x750, so we assume the shot is intended for HiDPI display and pre-select an 800x600 crop, but there's an option to crop it all the way down to 400x300 for normal screens.
One decision we made with this HiDPI release was that shots must now be _exactly_ 400x300 (or 800x600). (Previously, a shot could be less than 400x300.) This rule allows us to make much smarter assumptions about the user's intentions for display and simplify the upload workflows accordingly.
Before making this change, we peaked at the database to make sure there wasn't a lot of demand for less than 400x300 shots. Roughly 5% of all shots are less than 400x300 and, of those, nearly 18% are near misses, e.g. 400x299 - probably due to difficulty with the cropping tool. So another nice side effect of enforcing the size is that we can lock the crop into a 400x300 or 800x600 selection. The user merely has to position the crop target and never has to resize it.
HiDPI display wasn't a huge feature to implement, but like so many additions, it forces you to think about what you value and what you're willing to sacrifice when tweaking your product's behavior and design. Those conversations and decisions are the reason I love my job - product ownership is the bbbomb.
@Rich Thornett that last paragraph of your comment was the 3point shot for me on this one. I love that you have a glimpse into the thinking and research that went into making a product decision. So many of these discussions are happening every day and for some it is the reason that working in this industry is so compelling. And what a great use of dribbble, your product, that you not only *show* something interesting or beautiful, but also *tell* a bit about the how or why you arrived at this snapshot.
@Michael Parenteau Thanks for the kind words. Your comment is interesting - when we were building Dribbble, I actually thought there would be a lot more "tell" in the introductory comments than has played out. I'm happy with whatever level of detail folks want to offer in their shots, but since I'm short on visual skills, I need a good tell :)
@Rich Thornett yeah, I definitely didn't mean for it to be a knock on people not sharing more thought on their work. Sometimes visuals speak for themselves. But in the case of watching the process of product decisions it is really great to get a glimpse of more than just a "Boom. Here's a feature I did". Reading your comment made me think of dribbble as a playbook for a moment. And I can see how comments can facilitate that. Really, I'm just thankful you shared the insight. And would love to see more people take notice of this. The thinking and dialog we have is so critical to how we arrive at decisions. When these stories are shared, there is great opportunity to learn and grow. Thank you for taking the time to give that.
@Michael Parenteau That's great feedback - I love product stories, too. You've given me some ideas for making descriptive comments more visible and encouraged.
I think there's should be an option to upload two versions of the shot yourself. In case if user wants to make @1x shot sharper after resize from 800x600. Btw, have you tested resizing on GIFs? Usually they became corrupted after web resizings.
I never use Dribbble's crop tool. I tend to prep my shots first in Photoshop. This reminds me that Dribbble has a robust crop tool and I'll be sure to try it out soon. Maybe it'll be easier than what I've been doing.
Hey Rich, I know this doesn't pertain to your shot, but just thought you would like to know that the 'RSS feed' button covers the 'Older' button when viewing a player's shots: http://cl.ly/Jyz2
18 Responses
Pro
Rich Thornett
This big pink bbbeauty is one of several images used by our integration tests to verify the different workflows (crop v. no crop, whether to show the @2x option, whether to default to 400x300 v. 800x600, etc) that run based on the size of the original shot file.
In this case, the original shot is 1000x750, so we assume the shot is intended for HiDPI display and pre-select an 800x600 crop, but there's an option to crop it all the way down to 400x300 for normal screens.
One decision we made with this HiDPI release was that shots must now be _exactly_ 400x300 (or 800x600). (Previously, a shot could be less than 400x300.) This rule allows us to make much smarter assumptions about the user's intentions for display and simplify the upload workflows accordingly.
Before making this change, we peaked at the database to make sure there wasn't a lot of demand for less than 400x300 shots. Roughly 5% of all shots are less than 400x300 and, of those, nearly 18% are near misses, e.g. 400x299 - probably due to difficulty with the cropping tool. So another nice side effect of enforcing the size is that we can lock the crop into a 400x300 or 800x600 selection. The user merely has to position the crop target and never has to resize it.
HiDPI display wasn't a huge feature to implement, but like so many additions, it forces you to think about what you value and what you're willing to sacrifice when tweaking your product's behavior and design. Those conversations and decisions are the reason I love my job - product ownership is the bbbomb.
Hope you enjoy, please stop by and say HiDPI!
8 months ago
Pro
Emir Ayouni
Cool feature.
8 months ago
Pro
Iain MacDonald
YES! The @2x problem is solved. :D
8 months ago
Now, If only you had a button that fixed bad kerning. I'd love that 2x....
HiDPI bro!
8 months ago
Pro
Rich Thornett
@Artistdanz LOL. In my defense, it's a generated image. But I confess the beauty is not in the image, but rather when the tests pass.
8 months ago
@Rich Thornett that last paragraph of your comment was the 3point shot for me on this one. I love that you have a glimpse into the thinking and research that went into making a product decision. So many of these discussions are happening every day and for some it is the reason that working in this industry is so compelling. And what a great use of dribbble, your product, that you not only *show* something interesting or beautiful, but also *tell* a bit about the how or why you arrived at this snapshot.
Kudos!
8 months ago
Pro
Rich Thornett
@Michael Parenteau Thanks for the kind words. Your comment is interesting - when we were building Dribbble, I actually thought there would be a lot more "tell" in the introductory comments than has played out. I'm happy with whatever level of detail folks want to offer in their shots, but since I'm short on visual skills, I need a good tell :)
8 months ago
@Rich Thornett yeah, I definitely didn't mean for it to be a knock on people not sharing more thought on their work. Sometimes visuals speak for themselves. But in the case of watching the process of product decisions it is really great to get a glimpse of more than just a "Boom. Here's a feature I did". Reading your comment made me think of dribbble as a playbook for a moment. And I can see how comments can facilitate that. Really, I'm just thankful you shared the insight. And would love to see more people take notice of this. The thinking and dialog we have is so critical to how we arrive at decisions. When these stories are shared, there is great opportunity to learn and grow. Thank you for taking the time to give that.
8 months ago
Pro
Rich Thornett
@Michael Parenteau That's great feedback - I love product stories, too. You've given me some ideas for making descriptive comments more visible and encouraged.
8 months ago
Pro
Dario Calonaci
You guys are awesome
8 months ago
Pro
Tanveer Junayed
HiDPI!!!
8 months ago
Pro
Daryl Ginn
Hi, Rich.
You're awesome.
8 months ago
Pro
Igor Syvets
I think there's should be an option to upload two versions of the shot yourself. In case if user wants to make @1x shot sharper after resize from 800x600. Btw, have you tested resizing on GIFs? Usually they became corrupted after web resizings.
8 months ago
Pro
Steve Lowtwait
I never use Dribbble's crop tool. I tend to prep my shots first in Photoshop. This reminds me that Dribbble has a robust crop tool and I'll be sure to try it out soon. Maybe it'll be easier than what I've been doing.
8 months ago
Hey Rich, I know this doesn't pertain to your shot, but just thought you would like to know that the 'RSS feed' button covers the 'Older' button when viewing a player's shots: http://cl.ly/Jyz2
I'm on a Android Nexus 7 running Jellybean 4.1.
8 months ago
Just a little input from 1 user; I personally always crop my shots to exactly 400x300 in photoshop before uploading
8 months ago
That's great! I just wish the 2x version would be preloaded, it would make a big difference. Any chance?
8 months ago
"product ownership is the bbbomb."
I couldn't agree more!
about 1 month ago