
Saudi Platforms Code: The Practical Implementation Guide
Saudi Platforms Code is the open-source national design system launched by the Digital Government Authority on 17 November 2024, and the national reference for designing and building government platform interfaces. This guide covers what it actually contains, where the real files live, and what the Authority has published about its certificate. and what it has not.
Most of what is written about Saudi Platforms Code paraphrases the launch announcement: unified system, consistent experience, digital transformation. All true, and none of it helps the person who has to ship.
The working question is different. You own a live government platform and it has to become compliant. What exactly do you import? What has to change in the code that changing Figma will never fix? And how do you know when you have arrived?
We build and run design systems for our clients. We did not author this system and we do not grant its certificate. What follows reads the official publications as an implementer would, and draws a clear line between what the Authority has stated and what it has not.
What is Saudi Platforms Code, and who issued it?
Platforms Code is the open-source unified design system for Saudi Arabia, developed by the Digital Government Authority (DGA) in partnership with Azm X, and officially launched on 17 November 2024. It serves as the national reference for designing and developing government platform interfaces across the Kingdom.
At launch, DGA Governor Eng. Ahmed Alsuwaiyan described it as aligned with local and international digital-index standards, and as one of the initiatives supporting digital transformation across government entities.
The difference between this and a conventional government brand manual is structural: you call this system rather than read it. It ships guidelines, code snippets and design assets, and it runs on React on the code side and Figma on the design side. Anyone treating it as a PDF has already got half the implementation wrong before starting.
Is Platforms Code compliance mandatory?
The official launch describes it as the national reference for designing and building government platform interfaces, and no published text makes applying it a legal obligation. What is announced is that the Digital Government Authority awards a Platforms Code implementation certificate to the government entities that adopt it.
That changes what kind of decision this is inside an entity. A standard read as a recommendation competes with other priorities and slips a quarter at a time. A standard with a published certificate against it becomes a line item with an owner and a date. The practical difference is that it gets a budget and a named owner, rather than someone who will "pick it up later."
Worth stating plainly: the code is aimed at government platforms. Private companies fall outside its scope, though some read it anyway. it is open source and built on explicit accessibility standards, which makes it a useful reference for any team building Arabic interfaces.
Platforms Code components: what is actually in it
The published figures give an honest sense of the scope of work:
| Element | Published count |
|---|---|
| User-solution components | more than 33 |
| User-experience variables | 4,650 |
| Patterns aligned with the official identity guide | 100 |
The number that surprises teams is not the component count. It is 4,650 variables. Variables, design tokens, are the primitives behind every screen: colour steps, type sizes, spacing units, corner radii, shadows. A count that size means the system does not merely describe the finished appearance. It defines the vocabulary. Real compliance therefore starts with replacing your hard-coded values with its variables, not with making your screens resemble its examples.
This is where shallow implementations fail first. A team redraws screens to look like the official examples while the code underneath still carries its old colours and spacings, written by hand. The appearance converges, the system is absent, and the first update to the reference exposes the gap.
Typography and Platforms Code colours
The system uses two typefaces: IBM Plex Sans Arabic and the Saudi font. That carries a direct engineering cost. Swapping the typeface on a live platform is not a file replacement. It forces a review of every line height, every spacing value and every text box built around the metrics of the previous face. Arabic interfaces feel this hardest, because they were set on a font with different proportions.
The colours arrive inside the variable system rather than as a standalone swatch list, and they align with the official identity guide. The correct way to take them is to import the variables from the official source at design.dga.gov.sa, not to eyedrop hex codes from a screenshot. The reason is practical. In a mature design system a colour carries a role rather than a value: primary, surface, text-on-surface, error state. Copy the step without the role and you get the right colour in the wrong place.
One point teams routinely miss: contrast is an accessibility requirement, not a visual preference. Substitute a "close enough" step and you break a tested contrast ratio. It ranks among the most common findings in the accessibility reviews we run on existing interfaces.
Where to get Saudi Platforms Code
The single official source is design.dga.gov.sa, available in Arabic and English, carrying the guidelines, the design assets and the code snippets.
Alongside it sits the Components Library – Platforms Code file published on the Figma community, which is the practical starting point for a design team because it duplicates straight into your workspace.
A warning worth making explicit: community open-source projects have appeared that re-express the system's components for other frameworks, including a library built on shadcn/ui carrying the system's tokens with full right-to-left support, targeting Next.js, Vite and Astro. These are technically useful. But the Digital Government Authority does not publish them, they do not replace the official reference, and they never stand alone as evidence of compliance. Check the domain before you build on it.
Many people search for a "Platforms Code PDF", and the impulse is understandable, one file you can circulate in a meeting. But the assessment measures your build against the live variables and components in the reference. Any static file you download today starts going stale tomorrow.
Platforms Code certification: what is published, and what is not
The Digital Government Authority launched an implementation certificate for entities complying with the code's rules and standards, and has granted it to several since launch. Among those announced:
| Entity | What was reported |
|---|---|
| Real Estate Development Fund | among the first to implement, on its Real Estate Advisor platform and service |
| General Authority for Statistics | applied it across its new unified web portal |
| Human Resources Development Fund | recognised for implementing the code |
| Qassim University · Bisha University | received the implementation certificate |
| National Events Center · Ministry of Environment, Water and Agriculture | received the implementation certificate |
Here is what we could not find published: the detailed assessment criteria, the stages of review, how long the certificate remains valid, and whether it is renewed. The announcements report the outcome. None of them publishes the ruler.
We say this because the market fills an information vacuum quickly. Firms already sell "guaranteed certification" as a service, and they profit from the fact that nobody knows the criteria precisely. The sound position for your entity is to request the criteria from the Digital Government Authority directly, and to treat any third-party guarantee of the outcome with caution, nobody outside the granting body can promise its decision.
The implementation mistakes that keep recurring
Our experience here is not in awarding the certificate; it is in building design systems and keeping them alive inside real products. When we built a full design system with a documented component library for the eaalim learning platform, the expensive lessons were the same ones we see repeated in compliance projects.
The system lives only in Figma. Designers work against the library while developers rebuild each component by hand. The result is a platform that looks compliant in a slide deck and is not compliant in a browser. Both halves of the system, design library and code library, have to move together.
Copying the component instead of calling it. A team copies the system's button into its own repository and tweaks it for one special case, and is cut off from every future update. Special cases are handled with a documented extension, not a detached fork.
Ignoring the unhappy states. Teams apply the system to the primary screens and leave error messages, empty states and loading states on their old design. Those are precisely the screens a citizen meets at their worst moment, and their effect on trust outweighs the homepage.
No owner after launch. Compliance is not a project that ends. The reference gets updated and the platform adds services. Without an internal owner tracking the drift between your build and the reference, divergence starts with the first new feature.
Accessibility is load-bearing here, not decorative
The system rests on explicit accessibility standards, and on a government platform that is not a finishing touch. A government service is not optional for the citizen. Someone who cannot use the employment portal does not switch to a competitor. they lose the service. That sets a higher bar than a commercial site has to clear.
In practice, three things fail first. Keyboard-only navigation, where a journey cannot be completed without a mouse. Focus indication, where the user cannot see which element currently has focus. And error association, where the message sits loose on the page instead of being tied to its field, so a screen reader announces it without context.
None of these three shows up in a screenshot, and a visual design review will not catch them. That is exactly why they survive to launch and then surface in review.
The working rule: walk every service journey end to end with the keyboard alone before you submit anything. A journey you cannot finish without a mouse is incomplete, however closely its screens match.
What this means for your entity in practice
If you own a government platform, the order we would recommend: start by inventorying what you actually have, how many button variants and how many colour steps does your platform use today? That audit alone sizes the work more accurately than any estimate does. Then replace hard-coded values in the code with the system's variables before touching a single screen, because everything after that becomes close to automatic. Then move screen by screen, starting with the most-used services rather than the homepage.
And finally: ask the granting body for the criteria in writing before you buy a promise about them from anyone else.
Related reading: ux design, ui/ux design.
Core Web Vitals reference: Google web.dev — Core Web Vitals.
Similar News
View All News


Hiring a UX Design Agency: What You Actually Get, and How to Measure the Return
resourcesCommon Questions
Saudi Platforms Code is the open-source unified design system for the Kingdom of Saudi Arabia, developed by the Digital Government Authority in partnership with Azm X and launched officially on 17 November 2024. It is the national reference for designing and developing government platform interfaces, and it ships guidelines, Figma design assets and React code snippets.
No. The code is aimed at government platforms, and the Digital Government Authority awards an implementation certificate to the government entities that adopt it. Private companies fall outside its scope, though the fact that it is open source and built on explicit accessibility standards makes it worth reading for any team building Arabic interfaces.
The certificate is granted by the Digital Government Authority to entities complying with the code's rules and standards, and has gone to bodies including the Real Estate Development Fund, the General Authority for Statistics, the Human Resources Development Fund and Qassim University. The detailed assessment criteria, review stages and validity period are not something we found published publicly, so the correct route is to request them from the Authority directly rather than through an intermediary.
The colours are part of the system's variable set and align with the official identity guide, and the authoritative source is design.dga.gov.sa. Import them as variables rather than copied hex values, because every colour in the system carries a defined role, primary, surface, text-on-surface, error state, and taking the step without the role puts the right colour in the wrong position and breaks the contrast ratios accessibility depends on.
The system uses IBM Plex Sans Arabic and the Saudi font. Changing the typeface on a live platform is not a file swap: it forces a review of line heights, spacing and text containers that were built around the metrics of the previous face, and it is a line item routinely estimated below its true cost.
The published figures are more than 33 user-solution components, 4,650 user-experience variables and 100 patterns aligned with the official identity guide. The variable count matters most in practice, because it means compliance begins with replacing your hard-coded values with the system's variables rather than imitating the look of its screens.
No. The Figma library serves the design side only, and if developers are left to rebuild components by hand you get a platform that presents as compliant and is not compliant in the browser. A serious implementation runs through both halves of the system, design assets and code components, and every update to the reference has to reach both.
You can benefit from them technically, but carefully. Community projects exist that re-express the system's components for other frameworks; they are not published by the Digital Government Authority and they do not replace the official reference. Check the domain, and keep design.dga.gov.sa as the source every other library is measured against.