Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Font size issue

Open
#828 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
54/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
android, kotlin
Domain
mobile

Research direction

Start by locating the existing font-size setting and the message-list and conversation screens it affects; the issue does not name files or tests. Trace how the setting is stored and applied in both places, then determine how each can have a separate value. Done when users can set each size independently and the existing behavior is covered by relevant tests.

Written by the indexing model from the issue text.

Description

feature request needs triage
Checklist
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
Feature description

Could you add a separate font setting for the message list and the conversations themselves?

Why do you want this feature?

Currently, the app only has one font setting, which covers the font size for both the message list and the conversations.
I find that there's a big difference in font size between those two places, so I'm therefore unable to find a suitable setting.

Additional information

No response

Dominant language
Kotlin
Stars
1.6k
Forks
187
Avg merge
2d 9h
Merged PRs (30d)
20

Getting set up

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 FossifyOrg/Messages

All issues in FossifyOrg/Messages

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.