Add an option to change all extreme bright blue UI elements to a more comfortable blue color

Willie · 2023-07-05T05:12:20+00:00

There was an error rendering this rich post.

The high contrast extreme bright blue color now used throughout the program is very uncomfortable for my eyes. This UI change was introduced in software version 26 and is causing me to experience eyestrain. Other users have expressed similar concerns. Please see this thread: https://community.logos.com/forums/t/216724.aspx .

Specifically, I am referring to the uncomfortable bright blue now used in the Logos logo as well as the results and headings of Searches, Guides, Documents, and Tools (including the Factbook). It is also used in toolbar buttons, library filter results, various other buttons, the command box, resource navigation boxes, and other parts of the program.

Please add an option for a user to change all UI elements currently using the extreme bright blue color back to the more comfortable blue color used prior to software version 26. One way this might be accomplished would be to add two choices under the Accessibility section of the Program Settings, one for “normal” and one for “bright”.

Having this option will provide relief to those of us who are experiencing eye discomfort and pain from the current extreme bright blue UI elements but will also accommodate users who suffer from vision loss and might require UI elements this bright.

Find more posts tagged with

Features

Under consideration

Desktop App

Status: Under Consideration

Comments

Jordan Kurecki

Agreed

Anderson Abreu

I found the change in the shade of blue horrific. I hope Faithlife returns to the previous shade of blue. I utter the more minimalist air of yesteryear not to mention the eye problem of too bright a color.

unknown

Why not add an option for us to select what color we want it to be? Personally, I'd like a greenish color.

unknown

I like very much the new blue, it is more vibrant. Just wanted to provide this other point of view too.

Christian Alexander

Agree

Anderson Abreu

I would very much like to see the next version with the user interface elements using the current dark blue of the 37 beta 3 startup instead of the current bright blue which is tiresome.

b5c7daa23524cd21e98cb66ceddad05775d2c202_azull.png

Willie

I submitted the Feedback suggestion reflected above in July 2023, and within a short time, its status was upgraded to “under consideration” which I interpreted as a positive sign. Unfortunately, since that time, the problem has only gotten worse with even more use of excessively bright and vivid blue UI elements in both existing areas of the application and new ones such as the dynamic resource toolbar.

The worst example yet has been the recent change in version 41 to painfully bright and vivid blue footnote indicators, verse references, and other links in bibles and non-bible books. Prior to version 41, a comfortable and non-distracting dark navy blue was used to identify these items within bibles and non-bible books.

I remain hopeful Logos will adopt this Feedback suggestion. When that occurs, within the suggested program settings option, I request they especially prioritize the ability for a user to change the current bright and vivid blue footnote indicators, verse references, and other links in bibles and non-bible books to the previous blue that was used.

These intensely bright and vivid blue UI elements located directly within the text of bibles and non-bible books are intolerable for my eyes. They quickly cause eyestrain and adversely affect my use of Logos like no other change has ever done.

Mike Knapp

To add insult to injury, they've now made the footnotes that same color. This bright blue is so distracting that I contacted customer support to try to download an earlier version. They don't allow this. I wouldn't mind not having product support for my previous version, but again, this isn't allowed. I find it immensely distracting. Very poor UX choice. I've disconnected mine from internet access; no further updates or downloads for me.

I don't have eye problems, but I went on the PC yesterday for the first time in ages, and downloaded some updates. Good grief! Even I felt distracted by the bright neon blue verse numbers scattered all over the Bible. I just shut it down. I rarely use the PC anyway, so going back to the calm-looking web app is no hardship for me. Olive Tree lets you choose your own colours for all these text elements, so it can't be too hard to let people customise their interface, surely?

Quick Links

Product Feedback

Recent Ideas

Allow us to override Logos bias by attaching n - using the creation stories of Genesis as an example
Because of its reference to image, I prefer to use the Genesis 1 reference for the creation of mankind rather than Genesis 2. This is especially important to me in the current political environment as Genesis 1 has an androgynous Adam rather than a male Adam. However, Logos not only makes Genesis 2 the primary text, it…
Reading Plan for Print Library Books
Can we add functionality so that Logos can help me keep track of reading books in my print library? It probably would need a final page number field to be entered to confirm which edition or a book (even if it's just equally dividing raw page numbers).
Drag and drop for Shortcut folders
Auto Translate: Add navigation buttons in the translation tool
Please improve navigation in the Auto Translation tool. When a book is translated in the right column, the scrolling of the texts is confusing and the point of the text we are reading is often lost. There could be buttons to "forward" and "backward" by paragraph or "N" set of words, while keeping the two texts (original…
Increase the automatic translation panel in the mobile app
Please improve the translation panel in the mobile app so that it shows all the translated text without having to open the panel in full screen. Currently the translation panel is very small and only shows a small part of the text. Not even when you open it in split tab can you see all the translated text. To see it, I…