Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You get a lot of mileage out of platform-native UI elements. Also, people have been making megabyte-sized icons these days.


I raised a ticket with Slack when I tried to upload a team-icon. They wanted a _minimum_ of 512px^2. For an icon that will never be larger than 64px^2. They told that was intentional but didn't explain why (I guess the ticket handler just didn't know why) Wtf.


That's for "retina" displays. I don't think there are any 8x displays right now, but probably they want to be future-proof for a while


> That's for "retina" displays. I don't think there are any 8x displays right now, but probably they want to be future-proof for a while

It's kinda unreasonable to put restrictions on the users in order to achieve that. I mean, your slack team might not even be around by the time such displays are introduced. Why force the users to jump through hoops for such a silly reason? 90% of the time they're just going to resize whatever image they have in the quickest, dirtiest way to meet the system's arbitrary requirements.


> They wanted a _minimum_ of 512px^2.

It seems like there's a pretty simple malicious-compliance solution for your problem...

Bonus points for using http://jpegify.me/


As others pointed out, this is for future-proof high-dpi monitors. A smarter approach would be to ask for it in a vector format with hints for specific resolutions.


To have a hi-res version available for (future) hidpi screens and to apply their own (optimized?) scaling algorithms to.


Presumably because the icon will be shown on high-dpi displays (retina screens etc), no?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: