New answers tagged style-guide
Thinking from the product perspective, i would suggest break it down as a feature and its components and define priorities within these feature backlogs. That's how it is done with good product development life cycles. I would break it down like: Having no border Ability to have border and define thickness and color I would consider the border and its ...
Whether an image (or group of images) has a border or not is highly dependent on a) the images in question and b) the aesthetic opinion of the artist. So, ideally it's an option, and adjustable at that. But it sounds like you have to pick one or the other. In that case, as you can see by the answers thus far: it doesn't matter as everyone is going to have ...
Purely aesthetically I like the balance of the one with borders. This provides some breathing room for one image to transition into another. The one with thin lines looks awkward because those pictures don't really work when fit together.
Go with a thin border. Don't hint to the user whether or not you'll have borders. Just do it.
Top 50 recent answers are included