Hiring a UI UX designer in Rabat for a public service or govtech app? What to check in a portfolio, the Arabic RTL test, and why trust screens decide completion.
If you are looking for a UI UX designer Rabat teams can rely on, start by being honest about what you are building. Rabat is the capital, so a lot of the digital work here touches ministries, agencies, banks, universities and the startups that sell to them. That work has a different shape from a consumer app: long forms, documents, several languages, users who did not choose your product and cannot easily leave it. The designer you want is someone who can make a citizen or an employee finish a task without calling anyone, not someone who makes the prettiest Dribbble shot. In this guide I explain what that looks like in practice, what to check in a portfolio, how a remote designer from elsewhere in Morocco fits a Rabat team, and the design habits I would bring from projects where users were hard to reach. I work remotely from Morocco and have no office in Rabat; this is a guide, not a sales page.
Morocco's national strategy, Digital Morocco 2030, was launched in September 2024 with two axes: digitizing public services for citizens and businesses, and growing the digital economy through Moroccan tech solutions (CGEM's summary of the official launch). Much of the first axis is decided and built close to Rabat, because that is where the ministries sit.
You can already see what this looks like. idarati.ma, the national portal for administrative procedures run by the ministry in charge of digital transition and administration reform, lets people look up procedures, search for public services available online, rate an online service and send a complaint through Chikaya. That is a product. It has users, flows, empty states, error messages and trust problems, just like a fintech app.
Rabat also has a Technopark site, one of the network's locations alongside Casablanca, Tangier, Agadir and Essaouira (Technopark Morocco). Many startups there sell software to public bodies or to large companies. So when people search for a UI UX designer in Rabat, the real need is often "someone who can design a serious, form-heavy, multilingual product that ordinary people can finish".
I have not designed a Moroccan government service, and I will not pretend otherwise. But I have designed several products with the same underlying constraints, and those constraints are what a Rabat team should hire for.
Users who cannot be reached easily. At Accern, a no-code AI platform for finance, our users were large finance enterprises. Few of them were available for testing, so research had to run through the customer success team: interviews, a usability survey, personas built from what that team heard every day. Public sector products have a similar problem. The decision maker is a ministry or an agency, the user is a citizen or a civil servant, and the designer rarely gets to sit with either. A good designer finds the people who do talk to users (call centers, front-desk staff, the complaints channel) and turns them into a research panel.
Users who did not choose you. Nobody downloads a procedures app for fun. They arrive with a task, sometimes stressed, sometimes on a cheap phone with a weak connection. At Accern, 95% of users never used the product on their own; the customer success team built use cases for them. I wrote about how we changed that in enterprise UX design. Many public services are in the same place today: people go to an office or ask a relative because the digital path feels risky.
Language is a layout decision. Arabic reads right to left; French reads left to right; many users mix both. A design that was drawn in French and then "translated" usually breaks: icons point the wrong way, numbers and dates misalign, long Arabic labels overflow buttons. This needs to be designed from the first wireframe, not fixed at the end.
The single most useful pattern I can give a Rabat team comes from ViewStats, the creator platform built by the team behind MrBeast. Many creators signed up but never connected their YouTube channel. Research showed they did not understand what they would gain. We redesigned onboarding, empty states and prompts around one rule: show value first, ask for trust second. The channel connection rate went from 13% to 65%+. The full story is in onboarding UX best practices.
Public services ask for even more trust than a YouTube connection: a national ID number, a scan of a document, a phone number, sometimes a payment. Before that request, the screen should tell the person exactly what they will get, how long it takes, what they need on hand, and what happens to their data. A checklist at the start ("you will need your ID card and a recent bill, about 10 minutes") prevents more abandoned forms than any visual polish.
Rabat teams usually choose between four setups. None is right for everyone; the table shows the trade-offs I would weigh.
| Option | Best for | Watch out for |
|---|---|---|
| Full-time designer in Rabat | Long programs with many services and a design system to maintain | Slow to hire senior people; one person can get pulled into slide decks instead of product work |
| Local agency | Tenders, fixed scopes, teams that need a company contract | Design and research may be separated from build; check who actually does the work |
| Remote senior designer elsewhere in Morocco | Startups and product teams that need senior judgment fast, same time zone and languages | Needs a clear owner on your side and regular demos; on-site workshops must be planned |
| Remote designer abroad | Specific expertise you cannot find locally | Time difference, no Arabic or French, weak feel for local habits and paperwork |
For context on pricing and engagement models, my product designer in Casablanca hiring guide covers freelance, full-time and remote trade-offs in more depth. The logic is the same in Rabat, and many designers work for clients in both cities.
Most portfolios show finished screens. For institutional products, the finished screen is the least interesting part. Ask for these instead:
If a candidate cannot talk about these, they may still be talented, but they will learn the hard parts on your project.
Morocco runs on one time zone, so a remote designer in another Moroccan city works your exact hours and speaks the languages your users speak. The first two weeks I would spend on understanding, not drawing: read the current service end to end as a user, collect complaints and support questions, interview the staff who handle them, and map where people drop off.
Then I would design the riskiest flow first, usually the one that asks for documents or payment, and test it with a handful of real people before touching the rest. At Greenely, the Swedish energy app, users joined a Facebook group of 2,000+ members and even knocked on the office door to give feedback. A public service has its own version of that door: the complaints channel. Read it every week.
I also prototype in code when it helps. Some of my AI design experiments are full working builds made with Figma, Claude and the Figma MCP. For a Rabat team, that means a clickable, bilingual prototype on a real phone in days, which is far more convincing in a ministry meeting than a PDF.
Not usually. What you need is the same time zone, Arabic and French, and someone who can come for key workshops. A remote designer in Morocco covers that. Being physically in Rabat helps most when the work involves many in-person sessions with institutions.
Right-to-left layout, mirrored icons and navigation, mixed Arabic and Latin text in the same field, number and date formats, and how longer labels affect buttons and tables. Ask to see real RTL work, not a promise.
The methods are the same, the constraints are not. Users did not choose the product, the stakes of a mistake are higher, accessibility matters more, and decisions go through more people. I cover the basics in UI UX design explained.
Pick a few numbers before you start: completion rate of the main procedure, time to complete, number of complaints or support calls about it, and how many people still come to the office for something that exists online.
Write down the one procedure people abandon most, and what it asks them for. That is your first design project, whoever you hire. If you want a senior, remote designer who has worked through hard-to-reach users and trust-heavy onboarding, you can hire a product designer for your Rabat team and we can look at it together.
If you have a web or mobile app idea in mind or you need some advice about product design, feel free to get in touch ✉️