Mobile UI
Mobile UI: Design touch-first screens with readable hierarchy. Review the target devices, OS versions, app lifecycle, permissions, navigation, and network behavior and produce a mobile UI specification and prototype.
--- name: mobile-development-mobile-ui description: Use for mobile ui when asked to design touch-first screens with readable hierarchy; produce a mobile UI specification and prototype. license: MIT metadata: author: Thrive category: mobile-development --- # Mobile UI ## When to use Use this skill for mobile ui when you need to design touch-first screens with readable hierarchy. The expected result is a mobile UI specification and prototype. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect the target devices, OS versions, app lifecycle, permissions, navigation, and network behavior. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Map navigation, app lifecycle, permissions, backgrounding, offline use, and platform-specific controls on target devices. 2. **Decide.** Design the smallest native-feeling flow with offline and interruption states. 3. **Produce.** Build a mobile UI specification and prototype from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Choose shared behavior only where Android and iOS expectations agree; isolate native differences explicitly. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Respect platform navigation, safe areas, accessibility settings, and permission timing. - Account for backgrounding, flaky networks, and store submission constraints. ## Verification Check touch targets, text scaling, and interrupted flows. Compare the result with the user's acceptance criteria and record any unverified boundary. Provide a device matrix and test foreground, interrupted, denied-permission, and poor-network flows. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide a mobile UI specification and prototype. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->