For broad adoption of EmojiTwo, not having ready-to-use assets of EmojiTwo is a major issue.
You should supply TTF variants of ready-to-use font files, preferably in layered COLR/CPAL format as opposed to SVG-in-OpenType. Especially for embedding in software this is important because of the fact that SVGiOT is generally larger and slower to render than COLR fonts. This would allow adoption in e.g. our Pale Moon browser project.
Of note, when creating TTF files, bitmapped glyphs should be avoided at all cost to avoid issues like Google's Noto Color Emoji has. Only use vector for optimal display at all DPIs and avoiding glyph metrics issues.
For broad adoption of EmojiTwo, not having ready-to-use assets of EmojiTwo is a major issue.
You should supply TTF variants of ready-to-use font files, preferably in layered COLR/CPAL format as opposed to SVG-in-OpenType. Especially for embedding in software this is important because of the fact that SVGiOT is generally larger and slower to render than COLR fonts. This would allow adoption in e.g. our Pale Moon browser project.
Of note, when creating TTF files, bitmapped glyphs should be avoided at all cost to avoid issues like Google's Noto Color Emoji has. Only use vector for optimal display at all DPIs and avoiding glyph metrics issues.