Desartly

Digital product design for teams in Australia

For an Australian product team, I can design a defined user journey and prepare a practical development handoff. We work remotely from Tehran with agreed communication windows. The scope covers realistic screens, components and states, while coding, integrations and additional research have separate owners and deliverables.

What you receive

  • Priority task and responsive design
  • Components and exception behaviour
  • Prototype and milestone decision notes

How we work together

We start with a conversation about the problem, audience and deliverables. Once the scope is clear, I send a proposal with timing and cost. Reviews happen at agreed stages, followed by the design files and guidance your team needs to use or develop the work.

Review time is most useful when the decision is clear

We identify what each milestone needs to resolve: the task flow, the content hierarchy or the component behaviour. Feedback is consolidated against those decisions. Open implementation questions remain visible in the handoff, and changes to requirements are recorded rather than hidden in the next visual revision.

You receive an organised design file, a prototype of the key journey and documented interface states. Reusable components and mobile behaviour are explained for the development team. Coding and system integrations are scoped separately.

Related projects

These projects show the design approach and deliverables. I selected them for their relevance to the work.

Tesla cockpit at a circuit with balance and cooling controls on the centre displayTesla Track Mode

A Track Mode interface design helps drivers compare handling balance, temperatures and cooling settings before the next lap.

Tablet showing a John Deere farm-operations dashboard with map and equipmentJohn Deere Operations Center

A farm-operations dashboard design keeps field conditions, equipment activity and daily priorities connected in one responsive workspace.

Before we start

Can you include an implementation review?

Yes. We define the screens and number of reviews in the scope. I compare the implementation with the agreed design; code changes and technical QA remain with your developers.

How are cost and timing agreed?

I prepare a proposal after understanding the problem, deliverables, languages and review rounds. A fixed price before that discussion would leave important work undefined.

Do we need to be in the same city?

No. Meetings, reviews and file delivery can happen online. For printed or physical work, we agree separately on production responsibilities and output checks.

Discuss your project Request a proposal