Product design is the work of deciding how software behaves before anyone builds it — what a user sees, in what order, and what happens when something goes wrong. Most of it is not the happy path. Most of it is the states nobody demos.
We design apps, internal dashboards, and SaaS products, and the engineers who build them sit in the same studio. That is the whole difference: Fluids Design is the design practice of Fluids Digital, so a decision made in a file is a decision an engineer can question on the same day rather than reinterpret three weeks later.
What does product design actually cover?
It covers the flows, the screens, and every state each screen can be in. A dashboard is not one design — it is the loaded view, the empty view, the loading view, the error view, the no-permission view, and the view with one row and the view with ten thousand.
Teams get burned when only the loaded view exists. The rest gets invented at a keyboard under deadline, by someone who was not in the room when the product was decided. That is not an engineering failure. It is a design file that stopped early.
What we deliver
- User flows and information architecture
- Every screen at every state — empty, loading, error, permission, offline
- Interaction and motion specs written as behaviour, not as decoration
- Bilingual English and Arabic layouts, RTL-correct from the first frame
- A component inventory the build can follow
How is this different from hiring a design agency?
A design agency hands you a file and stops. We hand you a file that has already survived contact with the people who have to build it. The difference shows up at the end, not the start — in how much of the design is still there once the product is live.
You are not locked in. The files are specced so another team can build from them, and we will say so plainly if taking them elsewhere is the right call for you. What we will not do is hand over a deck that only works if we are the ones interpreting it. More on why in design that survives the build.
Do you design for Arabic and English?
Yes, and we design them together rather than translating one into the other. Arabic is not English with the text flipped: line height, type scale, numeral form, icon direction, and the reading order of a form all change, and a layout that only works after a find-and-replace was never bilingual.
We are based in Saudi Arabia and most of the products we design ship to Saudi and Gulf users, so RTL is the default assumption in the file rather than a phase-two ticket.
What kind of products have you designed?
Consumer mobile apps and the admin systems behind them, mostly Arabic-first. Naqrah, a clinic finder with a live map and booking. T-CODE, an offers and store discovery app built around a map. جمعيتك, a savings-circle app that tracks contributions across members and months.
Screens from these are on the work page. We do not publish client outcome numbers we cannot evidence, so what you get is the design, shown as it shipped — not a case study with a percentage in it.
How long does a product design project take?
Four to six weeks for a full product, one week for a single scoped problem. Scope and price are agreed in week one and do not move afterwards unless you move them. You see work every week rather than at a reveal.
The four steps are Frame, Explore, Design, Ship, and each one has something you can look at. The process page walks through what happens in each, and how a design project should run explains why it is shaped that way.