000
Compiling the experience

Chapter 02 — Jan 2022 — Dec 2023

The Sailors.

A World Cup deadline, traffic spikes and a 55% app.

Role
Senior Frontend Developer
When
Jan 2022 — Dec 2023
Where
Saudi Arabia · Remote
Product
Booking and e-commerce products, including the FIFA World Cup Qatar 2022 ticket booking

( 01 ) — The context

The Sailors builds booking and e-commerce products. There I built a FIFA World Cup Qatar 2022 ticket-booking experience on a fixed deadline, and took an application from about 55% to 95%+ on Lighthouse.

  • $20K

    approx. revenue per World Cup match event

  • 55→95%+

    Lighthouse performance

  • 95%+

    on every Lighthouse category for the storefronts

( 02 ) — The role

What I owned.

Senior Frontend Developer · Saudi Arabia · Remote

  1. 01

    Built and launched a high-traffic FIFA World Cup Qatar 2022 ticket-booking experience, supporting about $20,000 in revenue per match event.

  2. 02

    Proposed building it inside the existing platform instead of a separate website, reducing scope under a highly constrained timeline.

  3. 03

    Took an application from about 55% to 95%+ through rendering optimization, code splitting, caching and asset optimization.

  4. 04

    Delivered e-commerce storefronts at 95%+ across performance, accessibility, SEO, best practices and PWA readiness.

  5. 05

    Contributed to the product and UX design of an interactive venue seat-selection experience.

ReactTypeScriptMaterial UIReduxLighthousePWASEO

( 03 ) — Stories

What happened.

7 stories from The Sailors: the problem, what I did, what came of it.

Building the World Cup booking inside the platform

ArchitectureOwnership

The problem

The Sailors needed a FIFA World Cup Qatar 2022 ticket-booking experience for high traffic, under a highly constrained timeline.

What I did

I proposed integrating it into the company's existing platform rather than launching a separate website, then built and launched it with React, TypeScript and Material UI.

Result

Less to build and test under a very tight timeline, and the experience supported about $20,000 in revenue per match event.

The call

Integrate World Cup booking into the existing platform

Instead of: Launching a separate website

It reduced the implementation scope, so there was less to build and test before a deadline that could not move.

When the deadline is fixed, reuse is an engineering decision.

Read the full case study→

When match tickets opened, traffic spiked

Performance

The problem

Booking traffic spiked every time World Cup match tickets opened.

What I did

I kept the booking path minimal, cached match information and lazy-loaded the heavy parts.

Result

Booking stayed usable during the peaks.

Design for the busiest minute, not the average day.

Read the full case study→

From about 55% to 95%+ on Lighthouse

Performance

The problem

An application was stuck at about 55% on Lighthouse performance.

What I did

Starting from the Lighthouse results I found three causes: unoptimized images, a large JavaScript bundle (whole icon packages imported at once) and render-blocking fonts. I fixed the imports, split the routes, sized the images and changed font loading: rendering optimization, code splitting, caching and media and asset optimization.

Result

About 55% to 95%+ on performance.

Measure before you optimize. Images are often the cheapest win.

Read the full case study→

A fast storefront slows down one feature at a time

PerformanceQuality

The problem

New features slowly pulled the storefronts' Lighthouse scores down.

What I did

I started checking Lighthouse before merging, not after launch.

Result

The storefronts stayed at 95%+ across performance, accessibility, SEO, best practices and PWA readiness.

The call

Check Lighthouse before every merge

Instead of: Auditing after launch

Scores drift as features land. Catching a regression in review is cheaper than finding it in production.

Performance is a merge requirement, not a launch task.

Read the full case study→

Picking a specific seat, online

UX & productCollaboration

The problem

Customers wanted to choose a specific seat in a cafe, a hall or another venue.

What I did

I contributed to the product and UX design of an interactive seat-selection experience, working with product, design, management and backend, and balancing delivery speed, UX requirements, technical complexity and commercial objectives.

Result

Customers could select specific seats within venues.

Drawing seats is easy. Making availability and the chosen seat obvious is the work.

One seat changed, the whole map re-rendered

Performance

The problem

Selecting one seat re-rendered the whole seat map, which was slow on low-end phones.

What I did

I made each seat its own memoized component, so only the seats that changed re-rendered.

Result

Selection became smooth on phones.

Profile on the phone your customers actually use.

Server data is not UI state

Architecture

The problem

API data copied into the Redux store went stale and caused bugs.

What I did

I separated server data from UI state.

Result

Fewer stale-data bugs.

Keep one source of truth for data that lives on the server.

What I took from it: When the deadline is fixed, reuse is an engineering decision, not a shortcut.

Next chapter · 03

Mars Innovation Technology→