One Mobile Studio

Three forcing functions shaped every design call: shorten timelines for delivery-heavy projects, lower the resource bar for lean teams, and lift quality for developers new to mobile.

• Faster — collapse project timelines for apps that need little customisation.
• Cheaper — let small teams ship without scaling headcount.
• Better — give developers new to mobile a safety net of standards baked into the tool.

Studied the most frequently used screen layouts, interaction models and components across Android and iOS to propose a reusable, standardised template set. Reusable assets only work when they cover enough real-world variation without breaking platform conventions.

• 10+ screen layout families benchmarked across mobile and tablet.
• 200+ templates generalised into a reusable library.
• Standardised iconography drawn against Android and iOS guidelines.

Mapped four distinct archetypes — each with their own goals, fluency and failure modes — so the builder could speak to all of them without flattening the experience.

• Mobile app developers — fluent, want speed and control.
• Developers new to mobile — need guardrails and platform defaults.
• Non-technical users (e.g. sales) — want a working prototype, not an IDE.
• Enthusiasts — exploring what's possible, low tolerance for friction.

Asked the harder question first: what does a user think a 'no-code' builder will do for them? Mapped task flows around user goals across more channels and touchpoints than a single-screen tool would assume.

Evaluated prototypes against a focused set of heuristics so reviews stayed grounded and consistent across the team.

• Visual hierarchy — does the design guide users to the most important elements?
• Consistency — is the design system applied consistently across the app?
• Navigational clues — cues that help users find their way through the interface.
• Heuristic checks — user control and freedom, error prevention, and help/documentation.

Designed immediate, clear responses to user actions so people could refine and complete tasks without second-guessing the tool. Small loops, consistently applied, did more for confidence than any onboarding tour.

• Strong CTAs — Link, Publish, Save — drew immediate attention.
• Sidebars and toolbars became the primary hotspots users returned to.
• Visual cues (color, animation, tooltips) surfaced important features.
• Onboarding flows that highlighted hotspots lifted early engagement.
• Forgiving interfaces — undo and auto-save — let users experiment without fear.

• Users explored data logic and database features only superficially.
• Teams that planned on paper first finished faster than teams that jumped straight into the tool.
• Critical-but-underused features needed in-product assistance, not docs.
• Complex task setup lacked support and worked examples.
• Some template names were misleading and needed more generic, recognisable naming.

Cross-functional team across user experience, visual design and market research — co-owning research, IA, visual language and benchmarking over the life of the project.

• Anjani Varma — User Experience Designer, User Researcher and Usability Evaluator (1 year).
• Sagar Irukula — Visual Designer and Visual Design Strategist (1.5 years).
• Vikas Kumar — Design Market Researcher, template benchmarking (4 months).