[Feature Request] Toggle to use Android System Default Fonts (Accessibility & Readability)

[gander2388]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Android

Body

The Problem
Currently, the GitHub Mobile app on Android forces the use of hardcoded, bundled React Native fonts for its UI and monospace code blocks. While I understand this aligns with GitHub's design system, it completely overrides the Android OS-level system font settings.
This causes two major issues:

1. Accessibility (A11y) block: Users who rely on specific system-wide fonts for readability (e.g., high-legibility fonts, dyslexia-friendly fonts, or specialized system font weights) cannot apply them to GitHub Mobile. The app forces its own font, ignoring system-level user needs.
2. CJK Typography Inconsistency: Because the bundled English/Latin fonts do not contain CJK (Chinese, Japanese, Korean) characters, the app falls back to the system font only for CJK text. This results in a very jarring, misaligned typographic experience where English letters and Chinese characters look completely disconnected in weight and style within the same sentence.
   Proposed Solution
   Please add a simple toggle in Settings -> Appearance (e.g., "Use System Font").
   When enabled, the app should respect the Android system default sans-serif and monospace font families instead of loading the bundled .ttf assets. Many modern communication and productivity apps (like Telegram) offer this exact toggle to respect user accessibility settings.

Why this matters
A development tool should prioritize code readability and user accessibility over strict brand consistency on mobile devices. Allowing users to opt into their native system fonts would make reading long Issues and code reviews much more comfortable.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐