UX structure & user flows
Map the actions users need to complete, the information they need at each step, and the route through your app. For an existing product, use available analytics and feedback to identify journeys worth investigating.
Let’s talk MOBILE APP UX/UI DESIGN
Asol Design designs and redesigns iOS and Android apps for founders and product teams. We connect the interface with the decisions that matter: what users do first, why they return, and when paid value becomes clear.

SCOPE & DELIVERABLES
A mobile app design engagement can cover a new product, a core redesign, or one journey that needs attention. We agree on the platform, audience, product stage, and priority flows before defining the scope. The result is an editable design foundation your team can use to build and test the experience.
Map the actions users need to complete, the information they need at each step, and the route through your app. For an existing product, use available analytics and feedback to identify journeys worth investigating.
Develop the visual direction and agreed iOS or Android screens. Include relevant empty, loading, error, and success states so the experience remains understandable beyond the ideal path.
Deliver editable Figma designs, reusable components, and agreed prototypes. Document the intended behavior and discuss implementation questions with your team. Deliverables are defined in the proposal.
A full redesign is one option. You can also focus the engagement on onboarding and the first session, a subscription paywall, personalization, or a retention journey. Each starts with a specific problem and a behavior to evaluate after release. Visual polish and business priorities belong in the same conversation.
HOW WE WORK
Share the app or prototype, target audience, current challenge, and available evidence. We clarify what is in scope and where a diagnostic consultation would help.
Align on the UX structure and visual direction before expanding to the agreed screens. The proposal defines deliverables, revision rounds, and collaboration points.
Develop the approved flows, interface, states, and components. Review decisions in context so your team can connect individual screens to the complete journey.
Organize the Figma work and agreed behavior notes for development. Define what the team will measure after release; a design hypothesis becomes evidence only when tested.
EXPERIENCE & CONTRIBUTION
For ECOS, Anna’s mobile UX/UI redesign connected the map, scooter details, pricing, and booking actions. For dotdays, the work included the brand palette and product structure. Each product story separates the contribution from what the product’s team later launched or changed.
Yes. We agree on the target platforms and account for their interaction conventions. Supporting two platforms may change the screens, states, and handoff requirements in the scope.
Yes. We can work on a focused flow or a broader redesign and coordinate design handoff with your development team. Share the existing app, design files, and implementation constraints when enquiring.
Pricing depends on the journeys, platforms, screen and state coverage, and depth of strategy required. We confirm scope and price after reviewing the brief. A focused onboarding or paywall project can be scoped separately.
Development is a separate scope and is included only when explicitly agreed. A design engagement defines the UX/UI and deliverables your team receives; it does not automatically include implementation.