# Idea: Device-specific screenshots (or, Abusing Retina.js on Addressbin)

DevFeed: [Idea: Device-specific screenshots (or, Abusing Retina.js on Addressbin)](<https://devfeed.tech/articles/idea-device-specific-screenshots-or-abusing-retina-js-on-addressbin-32092.md>)

Original publisher: [Read original article](<https://adambard.com/blog/abusing-retina-on-addressbin/>)

Published: 2013-05-19T00:00:00Z

Content type: opinion

Language: en

Sources: [Adam Bard](<https://devfeed.tech/sources/adam-bard.md>)

Topics: [screen](<https://devfeed.tech/topics/screen.md>), [Image](<https://devfeed.tech/topics/image.md>), [client](<https://devfeed.tech/topics/client.md>)

Tags: [developer](<https://devfeed.tech/tags/developer.md>), [images](<https://devfeed.tech/tags/images.md>), [js](<https://devfeed.tech/tags/js.md>), [screenshots](<https://devfeed.tech/tags/screenshots.md>), [websites](<https://devfeed.tech/tags/websites.md>)

## AI overview

An experiment uses retina.js to serve different Outlook screenshots to users with standard and Retina displays on the Addressbin homepage. The author suggests adapting the approach for other operating-system-specific images and notes that its effect on business outcomes remains untested.

## Source excerpt

In January I came into possession of a new retina-display Macbook Pro. The screen is amazing, but has the side effect of making images on websites look mostly like garbage, unless the developer has taken extra steps to serve double-sized images to people with fancy screens. I ran across this problem trying to put a screenshot of Outlook on the homepage of Addressbin.com, my latest project. I knew it looked fine for almost every other visitor, but it was jarring for me, and presumably to anyone with a retina screen.