11–20 of 45 posts
What's the rationale behind this? Also, can someone explain me why Slack forces Google-themed emojis? I personally like the Windows design with black stroke
You can change the type of emoji Slack uses.
[0] https://get.slack.help/hc/en-us/articles/202931348-Emoji-and...
It seemed later in the week that this got turned around: https://twitter.com/Sam0711er/status/961312320537415681
A now-deleted tweet by a different developer facing the same issue stated that Apple apparently clarified by saying that using emoji as "media" was forbidden, but "content" was okay. Whatever that means.
Between this and the gun/water pistol thing, it really seems like Apple thinks of Unicode as their personal playground, and simply do not think through the network effects of their policies at all.
> Means if your app displays emoji anywhere without a user having it typed in, it’s illegal and will be rejected. How does that work in a chat app, when the remote user has typed that in on their device?
My inner rules lawyer does note that this could pose a problem for any bot that emits emoji...
> Means if your app displays emoji anywhere without a user having it typed in, it’s illegal and will be rejected. How does that work in a chat app, when the remote user has typed that in on their device?
Presumably a remote user is still a user. My inner rules lawyer does note that this could pose a problem for any bot that emits emoji...
Apple's Emoji designs are copyrighted to Apple. The unicode standard only defines character codes, and what they should "generally" look like (hell, Unicode's own example designs are monochrome line drawings). So this makes complete sense. If people started using Apple's logos on the App's UI, they would respond in exactly the same way. And if they're so invested in using emojis as a "key marketing strategy", why did…
Apple also owns the copyright on their San Fransisco font, but you don't see them blocking approval on apps for having text in the UI. The Roman alphabet only defines what letters should "generally" look like, so it would make sense. You want graphical representations of letters? Bring your own. Those ones are Apple's.
[1] https://en.wikipedia.org/wiki/Intellectual_property_protecti...
It seemed later in the week that this got turned around: https://twitter.com/Sam0711er/status/961312320537415681
The practical upshot of such a policy would be everyone shipping their own fonts instead of using Apple's system fonts, just to be safe. This would be nothing but trouble - bloated app sizes, more ram pressure, uneven look and feel, and diminished influence on Unicode. A now-deleted tweet by a different developer facing the same issue stated that Apple apparently clarified by saying that using emoji as "media" was fo…
From what I read other places, it meant that if it was non-variable and shipped with the app (UI, app data, etc) then it was "media" and not ok. If it was user supplied (like a text message), externally loaded (web page), etc... then it was "content" and ok.
Earlier quoted context omitted.
Apple also owns the copyright on their San Fransisco font, but you don't see them blocking approval on apps for having text in the UI. The Roman alphabet only defines what letters should "generally" look like, so it would make sense. You want graphical representations of letters? Bring your own. Those ones are Apple's.
At least in the US, fonts can not by copyrighted [1]. [1] https://en.wikipedia.org/wiki/Intellectual_property_protecti...
So practically, they are copyrighted. Are you going to redesign the TrueType font from scratch?
Apple's Emoji designs are copyrighted to Apple. The unicode standard only defines character codes, and what they should "generally" look like (hell, Unicode's own example designs are monochrome line drawings). So this makes complete sense. If people started using Apple's logos on the App's UI, they would respond in exactly the same way. And if they're so invested in using emojis as a "key marketing strategy", why did…
The fault lies with the Unicode consortium for opening this can of worms. The standard should have been reserved for outline letter forms only. Adding a set of full-color illustrations that expands every year was madness.
It’s especially bad for embedded devices that need to render text. It used to be that you could ship vector fonts for the major global scripts in less than 500k, and you could feel fairly confident that new glyphs aren’t randomly added.
Today you need to ship an emoji font and make sure that your font engine can render color graphics. Google offers the only semi-decent free color emoji font, and it weighs about 7 MB. That’s a vexing increase in system font footprint just so that there’s a poop illustration on disk when needed. You also need to update the set every year when the standard adds “depressed poop” or “sulking lizardman” or whatever.
From a UX point of view, it sucks because the free emoji font doesn’t look like the Apple one (because that look is copyrighted!), and inevitably someone will complain about it.
At least HN has the good sense to filter the emoji junk from comments.
What's the rationale behind this? Also, can someone explain me why Slack forces Google-themed emojis? I personally like the Windows design with black stroke
One possible reason is for accessibility (VoiceOver) and i18n.
good.