Your question is Driving Clarity From Ambiguous Requirements. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Tell me about a time you were asked to build or change a mobile feature with unclear or poorly defined requirements. How did you create clarity, decide what to do first, and move the work forward without waiting for perfect information?