Live testing and refinement

[sadiksojib35]

Once again: the dark theme is not a whim of aesthetes, but an important feature for the user. He uses it in specific cases. As soon as you understand in which ones, you can move on to testing.

Make a list of conditions for testing the dark theme . Think about when the user uses this feature and what surrounds them at that moment: lighting, time of day, location, what they click on, and what they swipe or scroll.

Create a separate analytics chat . Send all bugs, reflections and features for improvement there. If you see that certain elements are hard to read in daylight, send them to the chat with screenshots.

Refine . Send the list of ideas for improvement back to the latvia whatsapp phone number designers and developers, and test again after returning.

We ran live tests in TestFlight and gave ourselves time to get used to the dark theme. The whole team, including the CEO, literally lived with it: went to coffee shops, stared at screens at home, rode the subway, and so on.

Feedback from colleagues during the dark theme testing phase

This was the essence of the testing: we found that the same screens are read differently depending on external conditions, the color rendering of the devices, and the state of the screens. For example, it turned out that on OLED screens, some elements were shaking when scrolling. We had to reduce the contrast.



Step 4: Write color variables in the application code
This will help you quickly change the colors of certain elements of the application in one place without having to open each application file to register new colors and shades.

How it happens :

Each element of the application is assigned a variable: for a call button, for example, it will be call_button.
Inside each variable, two color options are specified: one for the light theme, the second for the dark theme.
All variables with their color values ​​are collected in a separate file. This will help in the future to change the colors of application elements much faster than manually.
It takes time and resources to adapt to variables. However, the effort pays off and saves the company money in the future.



Summary: A Quick Checklist for Dark Theme
Create a color profile . Don't rush to use something standard in the public domain and think about depth rules, starting colors for the background and different elements, hierarchy of shades and contrast.

Transfer the dark theme to real layouts . To do this, break the application into locations and main elements: background, text, icons, dividers, shadows, actions, forms, buttons, progress bars and loaders. Divide the layout team into iOS and Android systems, and also into mobile and desktop versions.

Conduct live tests and refine the mockups . Consider different lighting, locations, times of day, actions, and user vision. Give the dark theme a chance to take hold: let the team test it for a week and throw ideas for refinement and bugs found into a separate chat.