000
Compiling the experience

Chapter 03 — Jan 2021 — Dec 2021

Mars Innovation Technology.

Owning a booking platform from first screen to production.

Role
Frontend Developer
When
Jan 2021 — Dec 2021
Where
UAE · Remote
Product
Beljwar, a booking platform for venues, restaurants, rooms and halls

( 01 ) — The context

At Mars Innovation Technology I held primary end-to-end frontend responsibility for Beljwar, a multi-category booking platform, taking it from implementation through production delivery. The biggest wins weren't visual: they were the steps I took out of the way between finding a place and reserving it.

  • 20+

    Figma & Adobe XD screens to production

  • 10+

    booking & business websites delivered

  • Beljwar

    booking platform owned end to end

( 02 ) — The role

What I owned.

Frontend Developer · UAE · Remote

  1. 01

    Held primary end-to-end frontend responsibility for the Beljwar platform, from implementation through production delivery.

  2. 02

    Translated 20+ Figma and Adobe XD screens into responsive, production-ready interfaces, with implementation and UX improvements where appropriate.

  3. 03

    Restructured booking flows to reduce unnecessary steps and create a more direct path from discovery to reservation.

  4. 04

    Built interactive React and Material UI dashboards for data management and reporting.

  5. 05

    Delivered 10+ booking and business websites.

JavaScriptReactMaterial UIjQueryMetronicAOS

( 03 ) — Stories

What happened.

6 stories from Mars Innovation Technology: the problem, what I did, what came of it.

Owning Beljwar end to end

Ownership

The problem

Beljwar covered bookings for venues, restaurants, rooms and halls, and its frontend needed one owner from implementation to production.

What I did

I held primary end-to-end frontend responsibility, taking the frontend from implementation through production delivery and resolving the technical and user-experience challenges along the way.

Result

A booking platform delivered to production, and alongside it 10+ booking and business websites.

Ownership means the edge cases are yours too.

The biggest UX win wasn't visual

UX & product

The problem

Date, time, space and confirmation were separate screens between finding a place and reserving it.

What I did

I merged date and time into the space page and restructured the booking flow to remove unnecessary steps.

Result

A more direct path from discovery to reservation.

The call

Cut steps out of the booking flow

Instead of: Keeping one screen per field

Each extra screen between discovery and reservation is a place to drop off.

Every extra screen in a booking flow is another chance to lose the user.

Designs are the start of the conversation

UX & productCollaboration

The problem

20+ Figma and Adobe XD screens had to become production UI.

What I did

I treated the designs as the starting point, not a pixel-by-pixel spec, and introduced implementation and UX improvements where they made sense.

Result

Responsive, production-ready interfaces built from the designs, improved where it mattered.

The call

Treat designs as a starting point

Instead of: Copying every pixel as a fixed spec

Implementation reveals UX problems a static screen can't show.

Good handoff is a conversation.

The states the designs forgot

CollaborationUX & product

The problem

Designs often had no empty, error or long-text states.

What I did

I listed the missing states and agreed them with the designer before coding.

Result

Less rework.

Agree on edge cases before the first line of code.

Dashboards that keep up as data grows

PerformanceArchitecture

The problem

Large dashboard tables loaded everything at once.

What I did

I moved them to server-side pagination and filters, in the React and Material UI dashboards I built for data management and reporting.

Result

The tables stayed usable as the data grew.

Build for next year's data, not today's.

One stylesheet, two directions

Architecture

The problem

The platforms needed right-to-left Arabic and left-to-right English.

What I did

I used direction-aware layout, so one stylesheet served both.

Result

No separate RTL copy of the UI to maintain.

Solve it in the system, not in a copy.

What I took from it: Every extra screen in a booking flow is another chance to lose the user.

Next chapter · 01

Konin Cloud→