[Feature]: Feature Request: Support Custom Emoji Fonts

Open
  • Is something wrong?
#357 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
android, kotlin
Domain
desktop, mobile

Research direction

The request concerns emoji rendering, so start by finding where the app sets its text font in the Jetpack Compose theme and typography files. Check whether any emoji font setting already exists before designing an import option. The issue leaves the scope open, with no defined behavior or acceptance test, so confirm the design with a maintainer before writing code.

Written by the indexing model from the issue text.

Description

enhancement low theming

Description

It would be great to have an option to use a custom emoji font independently of the system's default emoji font.

Currently, the app respects the system's custom font for regular text, but emoji rendering may still depend on the emoji font provided by the operating system.

This can be a limitation for users running older Android versions, where newer Unicode emojis may not be supported and can appear as missing characters or empty boxes.

Proposed Solution

  • Add an option to use a custom emoji font independently of the regular text font.
  • Ideally, allow users to select or import their preferred emoji font.
  • Ensure unsupported emoji sequences fall back gracefully to the system font when possible.

Why This Matters

This would improve emoji compatibility and customization, especially for users on older Android devices who cannot easily update their system emoji fonts.

It would also give users more control over the app's appearance without requiring them to change their system-wide font settings.

Thanks for considering this feature!

Dominant language
Kotlin
Stars
44
Forks
5
Avg merge
14h 58m
Merged PRs (30d)
65

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from an1ndra/Messages

All issues in an1ndra/Messages

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.