Design mobile interfaces

Design the core mobile interface for our main task: creating and sharing a 60-second interactive prototype on iOS and Android. Deliver the home screen, the composer, and the share sheet flows with touch targets, edge-case states (no network, low storage), and microcopy for the share link. Make the screens ready for handoff to engineering by next sprint planning.

Before finalizing the mobile UI, make it easy for engineers and beta users to approve: surface the expected performance costs up front, make the primary action discoverable with no more than two taps, and flag anything that would make an accessibility reviewer hesitate. Call out the single area where we should budget extra QA time.

Beta testers say the mobile composer feels slow and sometimes crashes on older Android devices. The mobile lead, QA engineer Carlos, and I are on a call tomorrow. I worry we shipped a heavy animation or memory leak. I cannot tell if the issue is rendering, background uploads, or a third-party library. Recommend the first three diagnostics to run, prioritized, and a quick mitigation to push to users tonight.

Over multiple mobile releases we add richer visuals and interactions, and crash rates on low-end devices creep up. This erodes trust among a significant user segment. Recommend a development habit change and the one performance budget metric designers and engineers must enforce on every release, plus how to track it automatically.