UI/UX Design Services

Our design work is mostly for software people use all day: a helpdesk agent working a queue, a cashier at a repair shop, an inspector looking up a welding clause with one hand. In that kind of software, looking good matters less than whether the common task takes three taps or eight. We design the screens of our own products, FanDesk, Mobile Master, Probe361, Fidar MES and FanMail, and we bring the same approach to client projects.

Who this is for

Teams building or rebuilding a business application, a SaaS product or an internal tool, especially one that has to work in Persian or Arabic as well as English. It also fits if you already have a working system that people complain about and you want to know why before redesigning it.

We're not a branding agency. If you need a logo or a marketing campaign, we're the wrong call; if you need the screens behind the login to make sense, we're a good one.

How we work

1. Watch the current workflow. We sit with the people who'll use the software, or look at how they do the job today on paper, WhatsApp or spreadsheets. The goal is to find the few actions that happen dozens of times a day.
2. Screen map and wireframes. A list of screens and how you move between them, then rough layouts. Cheap to change, and this is where most of the decisions get made.
3. Clickable prototype in code. We build the key screens in React and Tailwind CSS with realistic data, in both directions. Because it's real code, the developers keep it, and you're reviewing something that behaves like the finished product.
4. Test with real users. A handful of people from your team try the tasks. We watch where they hesitate and fix it before full development.
5. Measure after launch. Lighthouse for speed, and session recordings and heatmaps (we use Microsoft Clarity) to see what people actually do.

Things we pay attention to

Right-to-left is designed, not flipped. Icons that imply direction get turned, numbers and English product codes inside Persian text still read correctly, and Jalali dates show where the user expects them. Every string goes through translation files; Fidar MES has no hardcoded interface text at all, and even error codes from the API map to a translated message instead of a raw English error.

Speed is part of the design too. On one of our own case-study pages, an 816 KB PNG hero image was pushing the largest-paint time past nine seconds in a mobile test, while a 100 KB WebP copy of the same image sat unused next to it. Switching to the WebP brought it to about 2.3 seconds and the Lighthouse performance score from 0.67 to 0.98. Small fix, big difference for anyone on a phone.

Work you can look at

In Mobile Master the point-of-sale screen is built around speed at the counter, with voice entry for the cashier and a public tracking link so customers stop calling to ask about their phone. Probe361 shows standards in English with Persian translation clause by clause, with a bottom navigation bar you can reach with one thumb. FanDesk puts the ticket queue, SLA timers and conversation on one screen, because agents switch between them all day.

Further reading

• Getting bilingual standards translation right in Probe361
• What running a repair shop on WhatsApp and a notebook really costs

Frequently asked questions

Do you deliver design files or working screens?

Mostly working screens. We do rough wireframes first, then build the prototype in React and Tailwind, so what you approve is close to what ships. If your team needs a separate design file for its own process, we can agree on that.

Can you redesign an app someone else built?

Yes. We start by reviewing the current screens and, if possible, watching a few users. The output can be a list of fixes your developers apply, or we do the frontend work ourselves.

How do you handle Persian and Arabic layouts?

Each screen is checked in right-to-left, not just flipped with CSS. That covers icon direction, mixed Persian-English text, number formats and dates. All three of our site languages, English, Persian and Arabic, run this way.

Do you do user research?

Yes, in a practical form: watching people do the task, short interviews and testing the prototype with a handful of real users. We don't sell large research studies as a separate product.

Is accessibility included?

The basics are part of how we build: readable contrast, keyboard access, real form labels and semantic HTML. If you need a formal audit against a specific standard, tell us at the start so we plan for it.

How long does a design phase take?

It depends on how many workflows there are. We give a timeline after the first workflow review, not before.