For the initial implementation of #670, there won't be a useful ordering to the results. This means a user might have to type a longer, more specific query to find their desired emoji than they might with good ranking.
This issue is for ranking the results. The ranking should match what the web app does:
https://github.com/zulip/zulip/blob/65f05794e/web/shared/src/typeahead.ts#L322-L382
(We might make exceptions and depart from that ordering if there are areas where we see an alternative that's substantially better in either quality of results or clarity of code, without being particularly worse on the other axis.)
Broadly, that ranking looks like:
"Popular emoji", before realm emoji, before (other) Unicode emoji, where "popular emoji" means a hard-coded list of six emoji like :+1:.
Names that exactly match the query, before names that have it as a prefix, before other matches.
For the initial implementation of #670, there won't be a useful ordering to the results. This means a user might have to type a longer, more specific query to find their desired emoji than they might with good ranking.
This issue is for ranking the results. The ranking should match what the web app does: https://github.com/zulip/zulip/blob/65f05794e/web/shared/src/typeahead.ts#L322-L382 (We might make exceptions and depart from that ordering if there are areas where we see an alternative that's substantially better in either quality of results or clarity of code, without being particularly worse on the other axis.)
Broadly, that ranking looks like:
For details, see the web implementation.
Related issues
670
228
618
881