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

[Bug]: Android app renders condensed/squished font across UI and markdown

Open Beginner friendly
  • Is something wrong?
#18,117 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, react-native, typescript
Domain
mobile

Research direction

Start in apps/mobile and trace how font families are assigned across the header, message body, lists, and composer on Android. Check the React Native font configuration and compare the rendered text with the web client on an Android device. Done means Android uses proportional sans-serif typography and bullets render correctly throughout the app.

Written by the indexing model from the issue text.

Description

needs more info via-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/mobile

Steps to reproduce
  1. Open the T3 Code Android mobile app on a Pixel / Android device.
  2. Connect to an active server / thread.
  3. Observe text rendering in the header bar, message body, bullet lists, and input box.
  4. Compare with the same thread viewed in Chrome mobile on the same device.
Device & OS
  • Device: Google Pixel 9
  • OS: Android 14 / Android 15
  • Client: T3 Code Android App (React Native / Expo)
  • Host Version: 0.0.46-nightly
Root Cause Context

React Native on Android does not support CSS comma-separated fallback lists. When custom font families are undefined or resolve to system fallbacks, Android defaults to sans-serif-condensed rather than sans-serif. Ensure Platform.select({ android: 'sans-serif' }) is set or explicitly bundle typeface assets via expo-font.

Expected behavior

Typography on the Android native app should match the web client exactly:

  • Use standard proportional sans-serif letter-spacing and aspect ratios rather than condensed glyphs.
  • Bullet points, symbols, and glyph metrics should render identically to the web app (circular • bullets rather than vertically stretched ovals).
  • Visual and reading experience should maintain 1:1 parity between apps/mobile on Android and apps/web.
Actual behavior

On Android (tested on Google Pixel 9, Android 14/15), all typography across the mobile app—including navigation titles, timestamps, chat bubbles, markdown body text, and composer placeholders—renders in a horizontally condensed / squished font (sans-serif-condensed / Roboto Condensed). Circular bullet points (•) render as narrow vertical ovals (◦).

In contrast, the web app running on the same mobile device via Chrome/PWA renders standard proportional sans-serif fonts (Roboto / system sans-serif) with correct aspect ratios and standard circular bullets.

Impact

Cosmetic issue

Version or commit

Android App version 2.0.0

Environment

Android 14 / Android 15

Logs or stack traces
Screenshots, recordings, or supporting files

No response

Workaround

None

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
12h 40m
Merged PRs (30d)
322

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.