Desartly

Digital product design for teams in Bahrain

For a Bahrain website or app, I design the agreed flows around realistic content and the roles using the product. Collaboration is remote from Tehran. We check Arabic–English layouts, responsive behaviour and exception states, then document the interface for developers; integration and permission enforcement are separate implementation responsibilities.

What you receive

  • Role-based journey and data states
  • Responsive and bilingual components
  • Prototype and behaviour 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.

Incomplete information should not look like a finished result

We define how missing data, loading and unsuccessful actions appear. Users need to understand what is available and whether they can continue. Status labels and follow-up messages reflect the actual process confirmed by the system owner, rather than invented assurances.

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.

A traveller connects two destinations through Flightio’s circular portalFlightio · Travel in One Clear Flow

Flightio’s circular symbol becomes a destination portal, connecting travel campaigns, transport services and a coordinated booking-interface study.

Glass-office scene and a BaseSpace genomic research interfaceIllumina BaseSpace

A genomic-workspace design keeps sample context, variant detail and illustrative drug-gene relationships connected during research exploration.

Before we start

Can components be shared with another product?

Yes, after reviewing the tasks and constraints. Shared components support consistency where behaviour matches; different needs are documented instead of being forced into one pattern.

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