Projects

The problem, what I built, the result

Eight systems in daily use by the people who paid for them. Each one written the same way: what was blocking the work, what I built, and what changed afterwards.

30+

Projects delivered

Years of experience

Sectors served

1 day

Reply time

Waiter mobile appReal-time ordersStation printingPoint of sale

Paresta

The problem: The order was written on a pad and then repeated three times — to the kitchen, to the bar, to the till — and a busy service lost lines on every trip.
What I built: A phone app for the waiters and a desktop POS that is also the server: the order is taken at the table, reaches the cash desk in real time, and prints at the station that has to make it.
The result: One order, entered once: the kitchen and the bar start while the waiter is still at the table, and the day’s takings add up from the same records.

Read the case study

Dark editorial illustration of the Paresta café point-of-sale workspace with table controls, order lanes and a product grid.

Browser extensionTest dataQA toolingChrome, Edge & Firefox

DevFiller

The problem: Testing a form means typing the same fake name, email and address again and again — and generic autofill guesses from the field name alone, ignores validation rules, and breaks on French or Arabic forms.
What I built: A browser extension that reads every field before filling it, generates one consistent fictional identity that passes each field's rules, and shows its reasoning in a side panel with an undo.
The result: One click fills a real-world form correctly 93.5% of the time, on Chrome, Edge and Firefox, with nothing leaving the browser.

Read the case study

ShopifyE-commerceLiquidUX

Léonie Maroquinerie

The problem: A curated collection from fifteen designer houses with nowhere to sell it: buyers asked for pieces by message, prices were quoted per conversation, and stock lived in a spreadsheet.
What I built: A quiet, deliberately plain storefront that lets the pieces carry the page, with checkout in four currencies, thirty-day free returns, and a golden-ticket campaign that gives people a reason to come back.
The result: The collection sells online in four currencies, and returns and stock are handled by the shop rather than by hand.

Read the case study

The Léonie storefront showing designer leather goods laid out on a plain background

Next.jsNestJSReactCMS & Roles

Irched & Islah

The problem: News, activities and branch details lived with whoever happened to type them, volunteer and donation requests arrived as messages, and changing a single line on the site meant waiting for a developer.
What I built: An Arabic public site for the association’s work, and a back office where a super-admin grants each staff member their own modules — so the news editor edits news and nothing else.
The result: The association publishes everything itself across sixteen modules, and volunteering and donations arrive as reviewable requests instead of messages.

Read the case study

TypeScriptCanvas 2DWebRTC Co-opWeb Audio

Life Quest

The problem: Browser platformers ship megabytes of sprites and audio before the first frame draws, and online play usually needs a server somebody has to pay for.
What I built: A game with no assets and no backend: the 1930s rubber-hose art is drawn live on a canvas every frame, every sound is synthesized, and co-op runs peer-to-peer over a four-letter code.
The result: Four hand-drawn multi-phase bosses, two switchable art styles and online co-op — with not one image or audio file in the repository.

Read the case study

Life Quest in its hand-drawn Cuphead art style, mid-fight against one of the four bosses

The JF LAROSE storefront showing the product range and the cash-on-delivery checkout

Next.jsNestJSE-commerceFR + AR (RTL)

JF LAROSE Laboratoires

The problem: Every order arrived as a phone call or a private message, and the delivery price for the buyer’s own commune had to be looked up by hand each time. Nobody could say afterwards what had been shipped where.
What I built: A shop in French and Arabic where the customer pays on delivery, the price for their exact commune is already known, and the team runs the catalogue, the orders and the courier paperwork from a back office.
The result: Customers across all 58 wilayas order for themselves in the language they read, and the courier slips print instead of being written out.

Read the case study

ReactLaravelB2B BookingRole-based Access

DenizTrip

The problem: Partner agencies checked what was available by phone and message. Confirming one booking and issuing its voucher and invoice could eat a full day of back-and-forth, and the same seat occasionally got sold twice.
What I built: A portal where each agency sees live availability and its own pricing, books in a few clicks, and downloads the voucher and invoice — while the Deniz team runs trips, hotel allotments, transfers and announcements from one back office.
The result: Agencies book against real availability, sold-out departures disappear on their own, and paperwork that used to be manual is generated the moment a booking is confirmed.

Read the case study

The DenizTrip agency portal showing available trips with live seat counts and per-agency pricing

Your project starts with one message

First call is free, 20 minutes

Write what is eating your time or losing you money. I reply within one working day with a plan and a price — and if I am not the right person, I will say so.

01: You send the message; I reply within a working day with a few questions.
02: A 20-minute call to understand what you actually need.
03: A written plan with a clear price and timeline, no commitment.

Tell me what you need

← Back to the site

Projects

The problem, what I built, the result

Eight systems in daily use by the people who paid for them. Each one written the same way: what was blocking the work, what I built, and what changed afterwards.

30+

Projects delivered

Years of experience

Sectors served

1 day

Reply time

Waiter mobile appReal-time ordersStation printingPoint of sale

Paresta

The problem: The order was written on a pad and then repeated three times — to the kitchen, to the bar, to the till — and a busy service lost lines on every trip.
What I built: A phone app for the waiters and a desktop POS that is also the server: the order is taken at the table, reaches the cash desk in real time, and prints at the station that has to make it.
The result: One order, entered once: the kitchen and the bar start while the waiter is still at the table, and the day’s takings add up from the same records.

Read the case study

Browser extensionTest dataQA toolingChrome, Edge & Firefox

DevFiller

The problem: Testing a form means typing the same fake name, email and address again and again — and generic autofill guesses from the field name alone, ignores validation rules, and breaks on French or Arabic forms.
What I built: A browser extension that reads every field before filling it, generates one consistent fictional identity that passes each field's rules, and shows its reasoning in a side panel with an undo.
The result: One click fills a real-world form correctly 93.5% of the time, on Chrome, Edge and Firefox, with nothing leaving the browser.

Read the case study

ShopifyE-commerceLiquidUX

Léonie Maroquinerie

The problem: A curated collection from fifteen designer houses with nowhere to sell it: buyers asked for pieces by message, prices were quoted per conversation, and stock lived in a spreadsheet.
What I built: A quiet, deliberately plain storefront that lets the pieces carry the page, with checkout in four currencies, thirty-day free returns, and a golden-ticket campaign that gives people a reason to come back.
The result: The collection sells online in four currencies, and returns and stock are handled by the shop rather than by hand.

Read the case study

Next.jsNestJSReactCMS & Roles

Irched & Islah

The problem: News, activities and branch details lived with whoever happened to type them, volunteer and donation requests arrived as messages, and changing a single line on the site meant waiting for a developer.
What I built: An Arabic public site for the association’s work, and a back office where a super-admin grants each staff member their own modules — so the news editor edits news and nothing else.
The result: The association publishes everything itself across sixteen modules, and volunteering and donations arrive as reviewable requests instead of messages.

Read the case study

TypeScriptCanvas 2DWebRTC Co-opWeb Audio

Life Quest

The problem: Browser platformers ship megabytes of sprites and audio before the first frame draws, and online play usually needs a server somebody has to pay for.
What I built: A game with no assets and no backend: the 1930s rubber-hose art is drawn live on a canvas every frame, every sound is synthesized, and co-op runs peer-to-peer over a four-letter code.
The result: Four hand-drawn multi-phase bosses, two switchable art styles and online co-op — with not one image or audio file in the repository.

Read the case study

Next.jsNestJSE-commerceFR + AR (RTL)

JF LAROSE Laboratoires

The problem: Every order arrived as a phone call or a private message, and the delivery price for the buyer’s own commune had to be looked up by hand each time. Nobody could say afterwards what had been shipped where.
What I built: A shop in French and Arabic where the customer pays on delivery, the price for their exact commune is already known, and the team runs the catalogue, the orders and the courier paperwork from a back office.
The result: Customers across all 58 wilayas order for themselves in the language they read, and the courier slips print instead of being written out.

Read the case study

ReactLaravelB2B BookingRole-based Access

DenizTrip

The problem: Partner agencies checked what was available by phone and message. Confirming one booking and issuing its voucher and invoice could eat a full day of back-and-forth, and the same seat occasionally got sold twice.
What I built: A portal where each agency sees live availability and its own pricing, books in a few clicks, and downloads the voucher and invoice — while the Deniz team runs trips, hotel allotments, transfers and announcements from one back office.
The result: Agencies book against real availability, sold-out departures disappear on their own, and paperwork that used to be manual is generated the moment a booking is confirmed.

Read the case study

Your project starts with one message

First call is free, 20 minutes

Write what is eating your time or losing you money. I reply within one working day with a plan and a price — and if I am not the right person, I will say so.

01: You send the message; I reply within a working day with a few questions.
02: A 20-minute call to understand what you actually need.
03: A written plan with a clear price and timeline, no commitment.