Try it & make changes

The fastest useful loop is: describe a change, try it in the app, and check that it does what you meant.

Make feedback concrete

Instead of “the screen is confusing,” explain the action and outcome:

On the packing-list screen, I cannot tell which items are already packed.
Make packed items visually distinct, keep their text readable, and put
unpacked items first. Show me the result on the emulator.

Ask for one change at a time. If your viewer supports annotation, mark the element you mean; otherwise name the screen and visible text.

Try the app yourself

Ask your agent to show the device. Tap through the flow, then hand control back before the agent continues. Describe the starting state when reporting a problem:

After adding two items, I packed the first one and reopened the app.
Both items came back unpacked. Reproduce that exact sequence, inspect
why the state is lost, fix it, and repeat the sequence to verify it.

Olef can provide screenshots, structured screen information, logs, and debugger evidence. Your agent should use the evidence relevant to the problem.

Keep a working flow from breaking

In a viewer with recording support:

1. Open the app at the start of the flow.
2. Choose Record steps and interact with the app.
3. Use Check to identify a visible result that must hold.
4. Stop recording and choose Save as test.
5. Ask the agent to inspect the saved test and run it again.

Saving normally replays the flow to check it. It can interact with the app again, so use development data. The recording guide explains what is captured and the limits of generated checks.

Ask for a useful handoff

Summarize what changed, which app behaviors you checked on the device,
where the source and saved test are, and what remains unfinished.

You should finish with something you can try, a clear record of the result, and a next step. Publishing to the Play Store is not yet an automated Olef workflow.