Product design

Make the important decisions before the build.

Turn an app idea into a clear flow, purposeful screens and a prototype you can put in front of people. Give the next stage of development a considered starting point.

Find the question the design needs to answer.

A product can look finished while its main task is still difficult to understand. We start by identifying the person using it, what they need to accomplish and the decision the next design round should resolve.

This can be a first app concept, a flow that has become confusing or an interface ready for a more consistent design. Share what already exists and where people get stuck.

Connect the journey to the details.

User flows show the steps and choices. Wireframes establish what each screen needs to communicate. Interface design then brings hierarchy, controls, content and visual identity together.

We consider the quieter states as well as the main screens: a new account with no content, a long title, an unavailable action or a mistake that needs correcting. These details make the handover more useful to the people building the app.

What a design engagement produces

  1. Feature 1

    A mapped journey for the agreed user tasks.

  2. Feature 2

    Wireframes and interface designs for the selected screens.

  3. Feature 3

    An interactive prototype for the questions being explored.

  4. Feature 4

    Shared styles, reusable design elements and behaviour notes as agreed.

Use a prototype to have a better conversation.

A prototype lets you step through the experience and discuss specific choices. Can someone find the next action? Does the language explain what will happen? Is there a clear way back?

We agree which journeys the prototype covers and how feedback will be gathered. If research sessions with customers are needed, participant access and research scope are planned separately.

Leave the next team with more than pictures.

A useful handover explains how the screens relate, which states belong to each interaction and which questions remain open. Design files and implementation notes should match the scope agreed for the project.

If Zynx is also developing the app, the design decisions carry into the build. If another team is developing it, we can discuss the review and handover support they need.

What a handover should include

  1. Feature 1

    How the screens relate to one another.

  2. Feature 2

    Which states belong to each interaction.

  3. Feature 3

    Which questions are still open.

  4. Feature 4

    Design files and implementation notes matching the agreed scope.

Common questions

Frequently Asked Questions

Can I commission product design without development?
Yes. A design engagement can cover an agreed set of flows, screens and prototype interactions, with handover materials for your development team.
Is an interactive prototype a working app?
A prototype demonstrates selected interactions. It does not by itself prove that data storage, payments, performance or other production features work.
What should I bring to the first conversation?
Bring your product goal, intended users, existing screens or sketches, brand materials and the decisions you are struggling to make. An unfinished idea is enough to begin the discussion.

Work with Zynx

Bring a brief, a prototype or an existing app.

We design and build apps for iPhone and iPad. Share where your project is now and we will discuss the people it serves, the work involved and a sensible next step.