Home › Projects › Abha Chamber: a bilingual platform

Abha Chamber: a bilingual platform

The Chamber's services, on a member's phone.

The Abha Chamber of Commerce offers investment advice, training, arbitration and research, but members couldn't reach any of it from a phone, and staff tracked requests without proper tools. We designed a member app and a staff back-office on one shared design system.

Client: Abha Chamber of Commerce, غرفة أبها
Role: Design lead
Team: Designers and a Visual Director
Status: Shipped

A lot of services and no easy way in.

The Chamber covers investment advice, small-business support, training, arbitration and research. Members had no modern way in on their phones, and staff ran operations without proper tools.

Business owners and Chamber staff.

A business owner wants to book an advisor or a training seat in a few taps. A staff member wants to approve purchase requests and see where each one is.

We built the system before either product.

I led the design system: navy and blue, a type scale that works in both languages, cards, inputs, tables and status chips. The member app and the back-office were then made from those parts.

Arabic first, English as the mirror.

Every component was drawn that way round. Icons, alignment and layout flip for English because the system expects it, so nothing had to be patched later.

What we settled before the screens.

These are why the app and the back-office look like one family.

Shared parts before products

Tokens and components came first, so the member app and the back-office were built from the same parts and never had to be made to agree.

Official, but current

Deep navy does the serious work: headers, main actions, the wordmark. Soft blue backgrounds and rounded cards keep it from feeling like an old government form.

Phone screens and dense tables, same tokens

The tokens stretch from a calm phone home screen to a busy operations table, which kept type sizes and contrast honest.

Where it stands.

2025 shipped: Both products live

The member app and the staff back-office went live on the same design system. No formal metrics were captured; member sign-ups and booking completion are what I'd measure first.

What I owned

The design system: tokens and components
Member app: services, advisors, booking
Staff back-office: requests and status tracking
Design direction across both products

Shipped, with gaps I can name.

Both products run on one system. The English version still trails, and some empty and error states aren't drawn yet.