A farm-operations dashboard design keeps field conditions, equipment activity and daily priorities connected in one responsive workspace.
Digital product design for teams in Singapore
For a Singapore product team, I can design the agreed user flows and interface remotely from Tehran. We review roles, content and technical constraints before extending the screens. Multiple language or data states are defined in the scope, and the handoff explains expected behaviour to developers without claiming that a prototype is a deployed product.
What you receive
- Role-based flows and information views
- Shared components and restricted states
- Prototype and developer documentation
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.
Different roles should see an understandable view
We map the task and information available to each role using rules approved by your system owner. Shared components keep the interface coherent, while restricted or unavailable actions receive appropriate treatment. Permission enforcement is a development responsibility, not something visual design alone can provide. A disabled action includes an explanation when users need to understand why it is unavailable.
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 genomic-workspace design keeps sample context, variant detail and illustrative drug-gene relationships connected during research exploration.
Before we start
Can you design permission-related screens?
Yes, based on access rules supplied by your team. I document the intended views and actions; engineers implement and test the actual permissions.
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.