Allow the system-wide typeface to be utilised, instead of Bitwarden's choice

Feature Requests Password Manager
,
1

Currently, versionCode=20994, of com.x8bit.bitwarden, overrides the android:fontFamily. However, this is a significant accessibility regression. An example of why is 0 appearing to be O, [1] but also consider anyone who utilises a dyslexia-specific typeface OS-wide. [2] Many corroborate that this is problematic for them, [3] including me. This is true for AOSP and mobile Darwin-based OSes (iPhoneOS, iPadOS, and VisionOS), and is the primary purview of this request.

Tangential

However, this is true alongside macOS, Linux-based OSes, and Windows > 10:

Albeit, likely merely due to adherence to sans-serif, rather than system.

  1. reddit.com/r/Bitwarden/comments/1pe66ce/comment/nsa5i09 ↩︎

  2. reddit.com/r/AndroidQuestions/comments/abeyl7/comment/nss1nut ↩︎

  3. reddit.com/r/Bitwarden/comments/1pe66ce/comment/nsh0gkj ↩︎

2 Likes
2

If it is a regression (i.e., if this feature was available in an earlier version), then you might consider reporting this as a bug on Github (assuming that what you are asking for here is beyond what has been reported in #15737).

1 Like
3

@grb, the old multi-platform mobile client codebase did, but the new /android one doesn’t. Does that count as a regression?

What I’m asking for here is for the new, native, mobile clients to support it. That cited issue deals with the desktop client.

4

I wholeheartedly agree with this. Not only is the font that is currently used hard to read, it also clashes with any OS font making the application look inconsistent as well as, quite frankly (and subjectively of course), rather ugly.

Having a “use system font” option in the settings of the respective client would be greatly appreciated!

1 Like
5

If it was me, I would report it as a bug in the Android repo. Make it clear in your description that this did use to work in the old mobile app (show evidence of this, if possible).

You can also this feature request open, but I would recommend not mentioning the feature request thread in your Github issue. OTOH, if Bitwarden does leave your Github issue open on triage, please link the Github thread here.

1 Like
6

@grb, in retrospect, an issue already exists:

A shame that we trust BW’s triage team so little. :laughing: [1]

  1. meta.discourse.org/t/390636 ↩︎

2 Likes
7

In my experience, the quality of triage varies significantly from person to person, so it can be hit-and-miss whether a new issue is deemed to be a feature request rather than a true bug, or worse, closed as not reproducible. Some of the triage staff don’t even have any Bitwarden affiliation shown in their Github profiles, so I don’t know where these individuals came from!

Therefore, it is best to make an airtight case when creating a new issue report.

2 Likes