Skip to content

[Bug] Different view on Pixel and Samsung phones #32

Closed

Description

@elenaeastwest-collab

What happened?

The Storage looks different on Pixel and Samsung

How do we make it happen again?

  1. Open the app.
  2. Go to Storage.

What did you expect instead?

I expected the same lettertype and size.

Screenshot or screen recording

Image Image

Which build are you on?

v0.1.6 (bottom navigation bar)

Phone and Android version

Pixel 7 Pro Android 16

Does it happen every time?

Every time

Anything else?

No response

Activity

  1. self-assigned this
    on Jul 12, 2026
  2. modified the milestone: v0.1.7 on Jul 12, 2026
  3. spdotdev commented on Jul 12, 2026

    @spdotdev
    Owner

    Investigated on a Pixel 7 Pro (Android 16). Good news: the app isn't using two different fonts. Both phones render the same typeface (Plus Jakarta Sans) from the same build — what differs is the text weight, and that's coming from an Android accessibility setting that's switched on for one of your phones and off for the other.

    What I found

    Android has a "Bold text" setting. When it's on, the system makes every app's text heavier — it isn't something the app chooses. I reproduced both of your screenshots on one phone, on one build, by toggling only that setting:

    Nothing else changed between those two — same app, same screen, same phone. So the two phones aren't showing different fonts; one of them has Bold text enabled.

    That also explains the "size" part: heavier letters genuinely read as bigger, even at the same font size.

    Where to check it on each phone

    Pixel 7 Pro and Pixel 10
    Settings → Accessibility → Display size and text → Bold text toggle.
    (The same screen has the Font size and Display size sliders — worth comparing those between the phones too, since they also change how big things look.)

    Samsung Galaxy S24
    Settings → Display → Font size and style → Bold font toggle.
    (Samsung's display-size equivalent is Settings → Display → Screen zoom.)

    Menu wording shifts a little between Android and One UI versions, so the quickest route on any of them: open Settings, use the search box at the top, and type bold.

    What would help

    Could you check that toggle on both phones and let us know which one has it turned on? If it's on for one and off for the other, that's the whole explanation and we'll close this — the app is deliberately respecting whatever each phone's accessibility settings ask for, and forcing both to look identical would mean ignoring a setting you (or someone) intentionally turned on.

    There is a fair point buried in here: with Bold text on, our headings and body text end up looking equally heavy, so the design loses some of its structure. We'll look at that separately.

    Unrelated, but from your other reports

    Both of these are fixed on the development branch and will be in the next build you get — they're not on your phone yet:

    • [Bug] The text is not visible correctly #31 — product names are no longer squashed; each name now gets its own full line (and the Dutch "Verplaatsen" no longer squeezes them).
    • The "Sorte…" cut-off label you can see in the screenshot above — the sort control now wraps instead of being chopped.

    Thanks for the detailed screenshots on these, they made it much faster to pin down.

  4. spdotdev commented on Jul 12, 2026

    @spdotdev
    Owner

    Follow-up on the investigation above — a note on process, for future reports.

    This one took an expensive detour on our side. Chasing it, I measured the type on a test phone, saw every font weight come back with identical metrics, and concluded the app's font was broken — I had replacement font files generated and the theme rewired before I ran the control that showed the original font was fine all along. The real cause was a single accessibility toggle on the phone. That was my miss: the device's display settings should have been the first thing I ruled out, not the last.

    The lesson is that "looks different on phone A vs phone B" is almost always worth reasoning about per device before touching any code — comparing two phones' settings takes a minute, and it's the cheapest possible first step.

    So for anything visual, it helps enormously to have, for each phone:

    • Model + Android version — e.g. "Pixel 7 Pro, Android 16" / "Galaxy S24, One UI 7"
    • Which screenshot came from which phone. The screenshot here and the ones on [Bug] The text is not visible correctly #31 turned out to be from different phones, which took a while to untangle.
    • The display/accessibility settings, since these change how everything renders:
      • Pixel 7 Pro / Pixel 10: Settings → Accessibility → Display size and text → Bold text, Font size, Display size
      • Samsung Galaxy S24: Settings → Display → Font size and style (Bold font), and Settings → Display → Screen zoom
      • On any of them, the quickest route: open Settings, use the search box at the top, and type bold or font size.

    Those few lines up front would have turned this issue into a two-minute answer instead of a long investigation.

    To be clear: the report itself was good. The screenshots were clear, the difference was real, and it was worth flagging. It's the device context that was missing — and that's the template's fault more than yours, since it never asked. #39 fixes that: the bug form now asks which phone, whether Bold text is on (with the exact path for Pixel and Samsung), the font/display size settings, and — when a report compares two phones — which screenshot is which.

  5. spdotdev commented on Jul 12, 2026

    @spdotdev
    Owner

    reopening the issue as it was closed by PR merges

  6. spdotdev commented on Jul 13, 2026

    @spdotdev
    Owner

    @elenaeastwest-collab can this issue be closed now?

  7. spdotdev commented on Aug 11, 2026

    @spdotdev
    Owner

    Closing — this was the phone's Bold text accessibility setting, not an app bug. See investigation above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions