Speedi Website

A bilingual landing site that sends Saudi grocery shoppers to the Speedi app.

Online Grocery · Landing Website · Saudi Arabia

·

Abdullah Al Othaim Markets

Scroll to explore

var(--variable-lVkmgb23s)

Speedi Website

A bilingual landing site that sends Saudi grocery shoppers to the Speedi app.

Online Grocery · Landing Website · Saudi Arabia

·

Abdullah Al Othaim Markets

Scroll to explore

var(--variable-lVkmgb23s)

Scroll to explore

Speedi Website

A bilingual landing site that sends Saudi grocery shoppers to the Speedi app.

Online Grocery · Landing Website · Saudi Arabia

·

Abdullah Al Othaim Markets

var(--variable-lVkmgb23s)

Speedi Website

A bilingual landing site that sends Saudi grocery shoppers to the Speedi app.

Online Grocery · Landing Website · Saudi Arabia

·

Abdullah Al Othaim Markets

Scroll to explore

var(--variable-lVkmgb23s)

PROJECT OVERVIEW

CLIENT

Abdullah Al Othaim Markets

MY ROLE

Design Lead, via Plexable

SCOPE

A long home page and five policy pages, each in Arabic and English, at desktop and mobile size.

VALIDATION

No analytics or user testing sits in the record. What can be checked is the published site: both language versions, every page, live at speedi.sa.

TIMELINE

2019 design, full site live by mid 2020

TEAM

Delivered through Plexable with the Abdullah Al Othaim Markets team

The context

Speedi is Abdullah Al Othaim Markets' online grocery in Riyadh, and it sells inside its apps rather than on the web.

So the website had a narrow job. Explain the service in seconds, show that this is a real Saudi business, and send people to download.

My responsibility

This was studio work: Plexable designed the site and its developers built it, in both languages and at both sizes. The design calls on it were mine.

The scope came from Othaim Markets, a landing site for an app that was already selling groceries in Riyadh.

Every page here is judged by one thing: whether a visitor leaves it with the app. That keeps design arguments short, because the question is never which section looks best.

Holding that line across six pages and two languages was the work. A landing site drifts the moment each page starts serving its own purpose.

01

What I owned

Two things were mine to settle: the page design and the type scale. The same Speedi faces had to carry a big headline and a long page of terms, in Arabic and in English.

01

What I owned

Two things were mine to settle: the page design and the type scale. The same Speedi faces had to carry a big headline and a long page of terms, in Arabic and in English.

02

How I led

Running the two versions as one piece of work kept the sections, the food photos and the app buttons identical. The Arabic pages carried the same weight as the English.

02

How I led

Running the two versions as one piece of work kept the sections, the food photos and the app buttons identical. The Arabic pages carried the same weight as the English.

CONSTRAINTS & TRADE-OFFS

One page that has to read in both directions rules out things a single-language site can afford. A hero that leans one way does not survive the flip, and neither does art that only resolves left to right.

The plainer the structure, the cheaper the second version. That trade bought a site that reads well in Arabic and gave up some of the visual play a one-direction page could have used.

01

The constraint

There was a rename to absorb. Marty became Speedi, and the layout, the grid and the section order all had to survive a new wordmark.

01

The constraint

There was a rename to absorb. Marty became Speedi, and the layout, the grid and the section order all had to survive a new wordmark.

02

The trade-off

What changes between the two versions is the reading direction, the menu order and the typefaces. Everything else stays put, which rules out any layout that only works one way round.

02

The trade-off

What changes between the two versions is the reading direction, the menu order and the typefaces. Everything else stays put, which rules out any layout that only works one way round.

● RESEARCH & CONTEXT

The questions the site had to answer

No user research sits in the record. The pages answer the three things a first-time visitor asks: what this is, whether it delivers here, whether it can be trusted.

The hero answers the first, the coverage map the second, and the policy pages the third.

● PRODUCT DECISIONS

What the page says first

At the top, one line states the service, Pick whatever, we deliver, with the app on screen beside it. Someone who reads nothing else still knows what it does.

From there the page runs in the order a stranger needs, not the order a business would pitch. What it is, what it carries, where it reaches, how to ask a question.

01

The home page

Hero, about, features, product categories, a coverage map and a contact form, in one scroll.

01

The home page

Hero, about, features, product categories, a coverage map and a contact form, in one scroll.

02

The policy pages

Five of them in one simple layout, so shoppers can check the rules before they order.

02

The policy pages

Five of them in one simple layout, so shoppers can check the rules before they order.

03

Two languages

Arabic and English versions that mirror each other, with a language switch in the header.

03

Two languages

Arabic and English versions that mirror each other, with a language switch in the header.

● PROCESS & EVIDENCE

Both sides of every page are in the record: landing page, feature cards, category carousel, coverage map, FAQs.

Each page exists twice, once for each reading direction. There are no wireframes or research files here, only finished screens, on desktop and with the phone menu open.

01.

One job: get the app

The App Store and Google Play buttons sit in the hero and again just above the footer.

04.

Features at a glance

Four cards: every type of product, scheduled orders, an offers page, and search by keyword, label, barcode or category.

02.

Arabic and English as equals

Neither language is the fallback. The Arabic site is a design in its own right, not the English one with the words swapped.

05.

A coverage map

A map of Saudi Arabia marked with each city's status, so a shopper can see whether Speedi reaches them yet.

03.

Built for phones

Most visitors arrive on a phone, so every page was designed at mobile size too.

06.

One grid, mirrored

One grid serves both languages, mirrored for Arabic, so a section lands in the same place in either version.

01.

One job: get the app

The App Store and Google Play buttons sit in the hero and again just above the footer.

03.

Built for phones

Most visitors arrive on a phone, so every page was designed at mobile size too.

05.

A coverage map

A map of Saudi Arabia marked with each city's status, so a shopper can see whether Speedi reaches them yet.

02.

Arabic and English as equals

Neither language is the fallback. The Arabic site is a design in its own right, not the English one with the words swapped.

04.

Features at a glance

Four cards: every type of product, scheduled orders, an offers page, and search by keyword, label, barcode or category.

06.

One grid, mirrored

One grid serves both languages, mirrored for Arabic, so a section lands in the same place in either version.

01.

One job: get the app

The App Store and Google Play buttons sit in the hero and again just above the footer.

02.

Arabic and English as equals

Neither language is the fallback. The Arabic site is a design in its own right, not the English one with the words swapped.

03.

Built for phones

Most visitors arrive on a phone, so every page was designed at mobile size too.

04.

Features at a glance

Four cards: every type of product, scheduled orders, an offers page, and search by keyword, label, barcode or category.

05.

A coverage map

A map of Saudi Arabia marked with each city's status, so a shopper can see whether Speedi reaches them yet.

06.

One grid, mirrored

One grid serves both languages, mirrored for Arabic, so a section lands in the same place in either version.

01.

One job: get the app

The App Store and Google Play buttons sit in the hero and again just above the footer.

03.

Built for phones

Most visitors arrive on a phone, so every page was designed at mobile size too.

05.

A coverage map

A map of Saudi Arabia marked with each city's status, so a shopper can see whether Speedi reaches them yet.

02.

Arabic and English as equals

Neither language is the fallback. The Arabic site is a design in its own right, not the English one with the words swapped.

04.

Features at a glance

Four cards: every type of product, scheduled orders, an offers page, and search by keyword, label, barcode or category.

06.

One grid, mirrored

One grid serves both languages, mirrored for Arabic, so a section lands in the same place in either version.

THE ENGLISH SITE

ABOUT ME

null
null
null
null
null
null
null

THE ARABIC SITE

ABOUT ME

null
null
null
null
null
null
null

COVERAGE

ABOUT ME

null
null
null

THE POLICY PAGES

ABOUT ME

null
null
null

ON THE PHONE

ABOUT ME

null
null
null
null

VISUAL LANGUAGE

ABOUT ME

null

THE ENGLISH SITE

ABOUT ME

null
null
null
null
null

THE ARABIC SITE

ABOUT ME

null
null
null
null
null

COVERAGE

ABOUT ME

null
null

THE POLICY PAGES

ABOUT ME

null
null

ON THE PHONE

ABOUT ME

null
null
null

VISUAL LANGUAGE

ABOUT ME

null

OUTCOMES

Where the site stands now

speedi.sa went from a coming soon page in 2019 to the full landing site by mid 2020. It is still Speedi's home online today.

It has stayed in service far longer than a launch page usually does.

2

Languages

Arabic and English, both full versions of the site.

6

Pages

The home page plus privacy, terms, returns, VAT registration and FAQs.

2

Screen Sizes

Desktop and mobile, the two sizes every page had to work at.

WHAT I’D IMPROVE

What I would change

The coverage map names the cities that are coming soon but not when, which is the next question a shopper asks.

The five rule pages hang off the footer with no ranking, so the FAQs a shopper actually wants sit level with the VAT registration.

WHAT I LEARNED

What it taught me

Online stores in Saudi Arabia need their terms in plain view, so policy pages are not filler. They are part of why a new grocery brand looks credible.

A rename is a layout problem as much as a brand one. A wordmark that has to drop into a finished header limits how tight that header can be.

HIRING A HEAD OF PRODUCT DESIGN?