github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-09 16:21:19 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[GH-ISSUE #5327] [PM-22477] UI/UX inconsistency: Only in the Android app, some date formats are different from the other apps (PS: and I found some more inconsistencies regarding "date formats"...) #109136

New Issue
Open
opened 2026-06-06 03:23:28 -05:00 by GiteaMirror · 16 comments
GiteaMirror commented 2026-06-06 03:23:28 -05:00
Owner
Copy Link

Originally created by @pamperer562580892423 on GitHub (Jun 8, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5327

Steps To Reproduce

  1. Open the Android mobile app.
  2. Go to a login item
  3. Open "View login" for that login item.
  4. Scroll down to the "Item history". (PS: Already the first inconsistency: the label "Item history" is missing only in the Android mobile app)

Expected Result

The field should show the date in a format, that all other BW apps show -- in the browser extension, desktop app and web vault, it looks like this:

Image

Actual Result

Only the Android mobile app shows the date in a different format than all other BW apps -- on Android, it looks like this:

Image

Differences:

  • date format itself: "06/07/25" only in the mobile app --> "Jun 7, 2025" in all other BW apps
  • the mobile app doesn't show the "Created" date
  • the mobile app uses "Updated" as a term, but all other BW apps use "Last edited" (PS: at the least the desktop app also uses "Updated" as a term")
  • the label "Item history" is missing on the Android app

Screenshots or Videos

(already included)

Additional Context

Besides the issue of inconsistent UI between the different Bitwarden apps, as a "German" I consider this also as a serious UX problem, since seeing the month as e.g. "Jun" (for June) is far less ambiguous as "06/07/25", as we in Germany are used to DD-MM-YY (and I think we are not the only country in the world, which is not used to MM-DD-YY" and always have to think twice, what the month and what day would be "this time"!).

PS:

  1. All BW apps I mentioned are on current 2025.5.x versions.

  2. Another UI/UX inconsistency: All "passkey field" dates in all BW apps ("06/07/25") are inconsistent with the date format in all other BW apps (where "Jun 7, 2025" is used instead):

Image

(this screenshot is from the web vault, and there you can see both date formats - "Passkey field" and "Last edited/Created" - in comparison)

At least the passkey field of all other BW apps is for one thing "consistent" with the passkey field date form in the mobile apps:

Image

  1. Speaking of "all the date sections": Unfortunately, there is another inconsistency regarding "date formats": even in the browser extension (following screenshot), the "Last synced" date is also in the old date format (and therefore inconsistent with e.g. the date format of the "Last edited/Created" dates in the browser extension - please check the other apps for that inconsistency as well)

Image

  1. As an Android user, I can't say if the iOS mobile app has the same "inconsistency issue" as now described for Android - please check that also, if you can.

Build Version

2025.5.0 (Android Mobile App)

What server are you connecting to?

EU

Self-host Server Version

(not self-hosting)

Environment Details

  • Fairphone 5
  • Android 14

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @pamperer562580892423 on GitHub (Jun 8, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5327 ### Steps To Reproduce 1. Open the Android mobile app. 2. Go to a login item 3. Open "View login" for that login item. 4. Scroll down to the "Item history". (PS: Already the first inconsistency: the label "Item history" is missing only in the Android mobile app) ### Expected Result The field should show the date in a format, that all other BW apps show -- in the browser extension, desktop app and web vault, it looks like this: ![Image](https://github.com/user-attachments/assets/2de1f28c-c8d4-4a74-9b6f-0ab8ee0a21ae) ### Actual Result Only the Android mobile app shows the date in a different format than all other BW apps -- on Android, it looks like this: ![Image](https://github.com/user-attachments/assets/de677877-cfef-4e05-ba33-d05dd11fe2e1) **Differences:** - date format itself: "06/07/25" only in the mobile app --> "Jun 7, 2025" in all other BW apps - the mobile app doesn't show the "Created" date - the mobile app uses "Updated" as a term, but all other BW apps use "Last edited" (PS: at the least the desktop app also uses "Updated" as a term") - the label "Item history" is missing on the Android app ### Screenshots or Videos (already included) ### Additional Context Besides the issue of inconsistent UI between the different Bitwarden apps, as a "German" I consider this also as a serious UX problem, since seeing the month as e.g. "Jun" (for June) is far less ambiguous as "06/07/25", as we in Germany are used to DD-MM-YY (and I think we are not the only country in the world, which is **not** used to MM-DD-YY" and always have to think twice, what the month and what day would be "this time"!). PS: 1. All BW apps I mentioned are on current 2025.5.x versions. 2. Another UI/UX inconsistency: All "passkey field" dates in all BW apps ("06/07/25") are inconsistent with the date format in all other BW apps (where "Jun 7, 2025" is used instead): ![Image](https://github.com/user-attachments/assets/8993b891-af9c-4b22-8d9a-3d8c9f71aa35) (this screenshot is from the web vault, and there you can see both date formats - "Passkey field" and "Last edited/Created" - in comparison) At least the passkey field of all other BW apps is for one thing "consistent" with the passkey field date form in the mobile apps: ![Image](https://github.com/user-attachments/assets/8d3bbac4-eb49-41ba-b1e6-98f0d32cabdc) 3. Speaking of "all the date sections": Unfortunately, there is another inconsistency regarding "date formats": even in the browser extension (following screenshot), the "Last synced" date is also in the old date format (and therefore inconsistent with e.g. the date format of the "Last edited/Created" dates in the browser extension - please check the other apps for that inconsistency as well) ![Image](https://github.com/user-attachments/assets/d3b6f6be-3480-4c54-98f5-397a554793a7) 4. As an Android user, I can't say if the iOS mobile app has the same "inconsistency issue" as now described for Android - please check that also, if you can. ### Build Version 2025.5.0 (Android Mobile App) ### What server are you connecting to? EU ### Self-host Server Version (not self-hosting) ### Environment Details - Fairphone 5 - Android 14 ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the app:password-managerbug labels 2026-06-06 03:23:28 -05:00
GiteaMirror commented 2026-06-06 03:23:29 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jun 8, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-22477

<!-- gh-comment-id:2953279610 --> @bitwarden-bot commented on GitHub (Jun 8, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-22477
GiteaMirror commented 2026-06-06 03:23:30 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jun 9, 2025):

PS: Sorry for that chaotic "bug report"... I just wanted to report "one thing" - and it ended up being many things, I just became aware of while I compared more... So, I hope you see through that "chaos" - and see the UI/UX inconsistencies, that should indeed be improved! 😉 (and please forward all consistencies to the teams, that develop the other BW apps, since not only the Android app has "issues" here...)

<!-- gh-comment-id:2954412121 --> @pamperer562580892423 commented on GitHub (Jun 9, 2025): PS: Sorry for that chaotic "bug report"... I just wanted to report "one thing" - and it ended up being many things, I just became aware of while I compared more... So, I hope you see through that "chaos" - and see the UI/UX inconsistencies, that should indeed be improved! 😉 (and please forward all consistencies to the teams, that develop the other BW apps, since not only the Android app has "issues" here...)
GiteaMirror commented 2026-06-06 03:23:30 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Jun 9, 2025):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

<!-- gh-comment-id:2954454711 --> @rmcdowell-bitwarden commented on GitHub (Jun 9, 2025): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
GiteaMirror commented 2026-06-06 03:23:30 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jun 13, 2025):

@rmcdowell-bitwarden I just saw the linked Pull Request... And I don't know how far reaching that PR is, but there is an image for the "Send" component's date format, and right, I forgot that...

As my bug report was a bit chaotic, here a summary:

  • e.g. in the item history, the mobile apps have an inconsistent date format (06/07/25 instead of Jun 7, 2025)
  • in the mobile apps, the label "Item history" is missing
  • in the mobile apps, in the Item history, the "Created" dates are missing
  • in the mobile apps, in the Item history the term "Updated" is used instead of "Last edited"
  • the desktop app also uses "Updated" instead of "Last edited"
  • all passkey fields in all apps have an inconsistent date format (06/07/25 instead of Jun 7, 2025) in comparison with the item history fields in most other BW apps
  • the "Sync" dates are inconsistent with the new date format used in the "Item history" of most other BW apps
  • and indeed -- I didn't list that before -- e.g. in the "Edit" mode of Sends, e.g. the "Deletion date" field shows also an inconsistent date (06/07/25) in comparison with the Item history fields show in most other BW apps (Jun 7, 2025)

(I hope I didn't forget anything now... and I hope you (BW) check on everything on here 😉)

<!-- gh-comment-id:2970290636 --> @pamperer562580892423 commented on GitHub (Jun 13, 2025): @rmcdowell-bitwarden I just saw the linked Pull Request... And I don't know how far reaching that PR is, but there is an image for the "Send" component's date format, and right, I forgot that... As my bug report was a bit chaotic, here a summary: - e.g. in the item history, the mobile apps have an inconsistent date format (06/07/25 instead of Jun 7, 2025) - in the mobile apps, the label "Item history" is missing - in the mobile apps, in the Item history, the "Created" dates are missing - in the mobile apps, in the Item history the term "Updated" is used instead of "Last edited" - the desktop app also uses "Updated" instead of "Last edited" - all passkey fields in all apps have an inconsistent date format (06/07/25 instead of Jun 7, 2025) in comparison with the item history fields in most other BW apps - the "Sync" dates are inconsistent with the new date format used in the "Item history" of most other BW apps - and indeed -- I didn't list that before -- e.g. in the "Edit" mode of **Sends**, e.g. the "Deletion date" field shows also an inconsistent date (06/07/25) in comparison with the Item history fields show in most other BW apps (Jun 7, 2025) (I hope I didn't forget anything now... and I hope you (BW) check on everything on here 😉)
GiteaMirror commented 2026-06-06 03:23:31 -05:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Jun 16, 2025):

We've made some changes to update the date formatting as well as added the creation date to the VaultItemScreen in this PR. Additionally, the date and times displayed throughout the Android app should now use the format-style associated with the locale the app is currently using. This change was made here.

These should address the majority of the issues described above and will be included in the next release of the app.

<!-- gh-comment-id:2977590979 --> @david-livefront commented on GitHub (Jun 16, 2025): We've made some changes to update the date formatting as well as added the creation date to the `VaultItemScreen` in [this PR](https://github.com/bitwarden/android/pull/5352). Additionally, the date and times displayed throughout the Android app should now use the format-style associated with the locale the app is currently using. This change was made [here](https://github.com/bitwarden/android/pull/5333). These should address the majority of the issues described above and will be included in the next release of the app.
GiteaMirror commented 2026-06-06 03:23:31 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jun 18, 2025):

@david-livefront Thanks for those changes!

Will the passkey fields also show the dates like "Jun 18, 2025" then (instead of the current "06/18/25")?

<!-- gh-comment-id:2983627703 --> @pamperer562580892423 commented on GitHub (Jun 18, 2025): @david-livefront Thanks for those changes! Will the passkey fields also show the dates like "Jun 18, 2025" then (instead of the current "06/18/25")?
GiteaMirror commented 2026-06-06 03:23:31 -05:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Jun 18, 2025):

@pamperer562580892423 It will not be in the upcoming release but I was able to run it by the design team for approval, it was approved and will be in the following release. The changes for that particular date can be found here.

We appreciate the attention to detail in this and the rest of your recommendations! I've handed the rest of your notes off to the product team. They will work to prioritize an audit of date formatting and consistency across platforms alongside the other efforts we have currently in-flight.

<!-- gh-comment-id:2985495693 --> @david-livefront commented on GitHub (Jun 18, 2025): @pamperer562580892423 It will not be in the upcoming release but I was able to run it by the design team for approval, it was approved and will be in the following release. The changes for that particular date can be found [here](https://github.com/bitwarden/android/pull/5386). We appreciate the attention to detail in this and the rest of your recommendations! I've handed the rest of your notes off to the product team. They will work to prioritize an audit of date formatting and consistency across platforms alongside the other efforts we have currently in-flight.
GiteaMirror commented 2026-06-06 03:23:31 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jun 18, 2025):

@david-livefront Thank you very much for that detailed update - that's great news! 👍

If the product team is going to review those, I may have one more recommendation - but I'm aware that this would go a few steps beyond my current UI/UX inconsistency issues and indeed would be a "feature request": very recently, on the Community Forum, the discussion about customizing date & time format (regarding time: e.g. a 24-hour-clock) came up again: https://community.bitwarden.com/t/customize-date-and-time-formats/51673 😉

<!-- gh-comment-id:2985559493 --> @pamperer562580892423 commented on GitHub (Jun 18, 2025): @david-livefront Thank you very much for that detailed update - that's great news! 👍 If the product team is going to review those, I may have one more recommendation - but I'm aware that this would go a few steps beyond my current UI/UX inconsistency issues and indeed would be a "feature request": very recently, on the Community Forum, the discussion about customizing date & time format (regarding time: e.g. a 24-hour-clock) came up again: https://community.bitwarden.com/t/customize-date-and-time-formats/51673 😉
GiteaMirror commented 2026-06-06 03:23:32 -05:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Jun 18, 2025):

@pamperer562580892423 The PR mentioned above does address this to some extent. The locale set for the app via the Language setting, found in Settings -> Appearance, will determine the date and time format style used. This will handle things like AM/PM verse 24-hour time settings. You can see this in action by changing the language between English and English (British).

<!-- gh-comment-id:2985594820 --> @david-livefront commented on GitHub (Jun 18, 2025): @pamperer562580892423 The [PR mentioned above](https://github.com/bitwarden/android/pull/5333) does address this to some extent. The locale set for the app via the Language setting, found in Settings -> Appearance, will determine the date and time format style used. This will handle things like AM/PM verse 24-hour time settings. You can see this in action by changing the language between `English` and `English (British)`.
GiteaMirror commented 2026-06-06 03:23:34 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jun 18, 2025):

@david-livefront Ah... indeed, I already saw in this PR a mention of "locale style" - but to prevent possible disappointment, I tried not to interpret too much into it. Until now. 😉👍

<!-- gh-comment-id:2985646478 --> @pamperer562580892423 commented on GitHub (Jun 18, 2025): @david-livefront Ah... indeed, I already saw in this PR a mention of "locale style" - but to prevent possible disappointment, I tried not to interpret too much into it. Until now. 😉👍
GiteaMirror commented 2026-06-06 03:23:34 -05:00
Author
Owner
Copy Link

@jidanni commented on GitHub (Jun 29, 2025):

English and English (British).

While you are at it, shouldn't that be

English (United States) and English (British)

I mean how would you feel if the choices were

English and English (United States)

as if one was the real English. Even "British" is bad:

Play it safe with https://www.andiamo.co.uk/resources/iso-language-codes/ and names.

<!-- gh-comment-id:3016471251 --> @jidanni commented on GitHub (Jun 29, 2025): > `English` and `English (British)`. While you are at it, shouldn't that be > `English (United States)` and `English (British)` I mean how would you feel if the choices were > `English` and `English (United States)` as if one was the real English. Even "British" is bad: Play it safe with https://www.andiamo.co.uk/resources/iso-language-codes/ and names.
GiteaMirror commented 2026-06-06 03:23:34 -05:00
Author
Owner
Copy Link

@closebot-bw commented on GitHub (Feb 11, 2026):

⚠️ Stale Issue Notice

This issue has been automatically marked as stale due to inactivity. It will be closed in 2 weeks (February 25, 2026) if no further activity occurs.

If this issue is still relevant and you would like to keep it open, please:

  • Comment on this issue to show continued interest
  • Provide any additional information or updates
  • Confirm that the issue still exists in the latest version

Thank you for your contribution to this project! 🙏

<!-- gh-comment-id:3886594228 --> @closebot-bw commented on GitHub (Feb 11, 2026): ⚠️ **Stale Issue Notice** This issue has been automatically marked as stale due to inactivity. It will be closed in **2 weeks** (February 25, 2026) if no further activity occurs. If this issue is still relevant and you would like to keep it open, please: - Comment on this issue to show continued interest - Provide any additional information or updates - Confirm that the issue still exists in the latest version Thank you for your contribution to this project! 🙏
GiteaMirror commented 2026-06-06 03:23:35 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 11, 2026):

I just compared with Android app 2026.1.1 and would say that most (or all?!) things are implemented now on the Android app. - But as I e.g. can't say it for all "locale styles" (or rather I can't assess their implementation) I think you should decide if it's consistent now across all "locations" (in all apps).

<!-- gh-comment-id:3887644397 --> @pamperer562580892423 commented on GitHub (Feb 11, 2026): I just compared with Android app 2026.1.1 and would say that most (or all?!) things are implemented now on the Android app. - But as I e.g. can't say it for all "locale styles" (or rather I can't assess their implementation) I think you should decide if it's consistent now across all "locations" (in all apps).
GiteaMirror commented 2026-06-06 03:23:35 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 12, 2026):

Ah, I now found at least one current inconsistency - regarding the "item history":

The Android app (2026.1.1)...

Image

 

... still misses the sub-title "Item history" - and has a different order here than I see in the web vault (2026.1.1) and in the browser extension (2026.1.0):

Image

(screenshot from the browser extension)

 

Android app:

  1. Created
  2. Last edited
  3. Password last updated
  4. Password history

Browser extension & web vault:

  1. Last edited
  2. Created
  3. Password updated
  4. Password history

(You can see one other minor difference here: the Android app calls it "Password last updated", while the other apps just seem to call it "Password updated". And another difference: what is indeed nicer in the Android app: it shows "Password history: x", while the other apps just show "Password history".)

<!-- gh-comment-id:3893442351 --> @pamperer562580892423 commented on GitHub (Feb 12, 2026): Ah, I now found at least one current inconsistency - regarding the "item history": The Android app (2026.1.1)... <img width="600" height="383" alt="Image" src="https://github.com/user-attachments/assets/13e56208-fc88-457f-b869-df78ddf85ab8" /> &nbsp; ... still misses the sub-title "Item history" - and has a different order here than I see in the web vault (2026.1.1) and in the browser extension (2026.1.0): <img width="610" height="230" alt="Image" src="https://github.com/user-attachments/assets/1272ce75-38ea-47e7-8ca8-464a71757b6b" /> (screenshot from the browser extension) &nbsp; Android app: 1. Created 2. Last edited 3. Password last updated 4. Password history Browser extension & web vault: 1. Last edited 2. Created 3. Password updated 4. Password history (You can see one other minor difference here: the Android app calls it "Password last updated", while the other apps just seem to call it "Password updated". And another difference: what is indeed nicer in the Android app: it shows "Password history: x", while the other apps just show "Password history".)
GiteaMirror commented 2026-06-06 03:23:35 -05:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Feb 17, 2026):

@pamperer562580892423 The order of the dates and some of the copy has been updated on Android here and iOS should be coming soon.

Our Design team has decided that the item history header and and such will not be changing for mobile. So we will not be making any updates there.

<!-- gh-comment-id:3915442694 --> @david-livefront commented on GitHub (Feb 17, 2026): @pamperer562580892423 The order of the dates and some of the copy has been updated on Android [here](https://github.com/bitwarden/android/pull/6544) and iOS should be coming soon. Our Design team has decided that the item history header and and such will not be changing for mobile. So we will not be making any updates there.
GiteaMirror commented 2026-06-06 03:23:35 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 17, 2026):

Thanks again, @david-livefront! For implementing it - and for the update here. 👍

<!-- gh-comment-id:3916003200 --> @pamperer562580892423 commented on GitHub (Feb 17, 2026): Thanks again, @david-livefront! For implementing it - and for the update here. 👍
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#109136
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?