Available for remote workGaza, Palestine
Laravel · PHP · MySQL · Vue 3
I build the whole system,and test it before you see it.
I build booking systems, online stores and admin dashboards in Arabic and English, with Laravel and MySQL on the back end and Vue 3 on the front.
- Database
- Server & API
- Interface
- Tests
- Security
Why me
Most problems on a website never show on the screen. They show when two people buy the last piece in the same second, or when a visitor in another country books at the wrong hour. That is where I start: I write the rule first, then the test that proves it, then the screen that carries it.
The work
Five projects, five real problems
Each one started with a plain question from the people it was for. Here are the questions, and how I answered them.
Diwan·2026
Arabic-first furniture store for the Saudi marketIndependent project · open source
Every piece tells the buyer, before they pay, if it fits the room and gets through the door.
The problemFurniture is where buying online fails most: a centimetre figure means nothing for the buyer’s room, so the piece arrives and does not clear the door.
- Laravel 12
- PHP 8.2
- MySQL
- Blade
Waeda·2026
Appointment booking for service businessesIndependent project · open source
Customers book from their phone with no account, and an appointment guard keeps booked times from going empty.
The problemThe real loss for a business is not too few bookings but no-shows: a booked time left empty because the customer did not come.
- Laravel 12
- MySQL
- Vue 3.5
- Vite 6
Opsight·2026
Operations and business intelligence for Gulf businessesIndependent project · public repository
Your orders, stock and expenses in one place, and their figures against the period before.
The problemOrders in one place, stock in another, expenses in a spreadsheet, so nobody knows what last month’s profit was or why it moved.
- Next.js 16
- React 19
- Tailwind 4
- TanStack Query
Takharruj·2026
Graduation project management platformIndependent project · open source
A graduation project from first idea to final grade, in one place for the student, the supervisor and the department.
The problemThe information lives in spreadsheets, WhatsApp and email, so nobody can quickly say which groups have no supervisor, which milestones are late, or who changed a grade.
- Laravel 12
- PHP 8.2
- MySQL
- Blade
Lamma·2026
Orphan sponsorship platformIndependent project · open source
Sponsor a named child within their own family, and see where your money went.
The problemMost donation sites ask you to trust them: you give to an anonymous cause and never see what arrived and what was spent.
- Laravel 12
- PHP 8.2
- MySQL
- Blade
Services
What I can build for you
Pick the one that sounds like your project. Next to each is a real project where I’ve done exactly that, so you don’t have to take my word for it.
E-commerce
A complete Arabic store: catalogue, stock, cart, orders and invoices. Stock is settled in the database, so the last piece never sells twice.
- For
- A shop that sells online, especially in Arabic.
- You get
- A storefront, cart and checkout, stock, orders and invoices, and an admin panel.
Booking systems
Booking from a phone with no account, times worked out from your real hours, and two people never get the same slot.
- For
- Clinics, salons, training centres: any business that runs on appointments.
- You get
- A booking page for your customers, a console for your team, and times worked out from your real hours.
Business systems and dashboards
Roles, permissions and workflows, with tables that stay fast at thousands of rows.
- For
- A business where several roles work on the same data.
- You get
- Roles and permissions checked on the server, workflows, and tables that stay fast at thousands of rows.
Work on an existing project
I finish or fix an app that already exists: I read the code first, then make the smallest change that solves it.
- For
- An application that already exists and needs finishing, fixing or a new feature.
- You get
- A small, readable change that solves it, and a test that keeps it solved.
Delivered in Laravel · PHP
Also
I also take on , , and .
A schema that stops the mistake before it happens, and a documented API held up by tests.
Built in LammaI turn your design into a front end that actually works: responsive, in Arabic and English, true to the spacing and type you chose.
Delivered in Vue 3 · Next.js · Tailwind CSS
Automated tests for an existing Laravel app, so a bug we fixed stays fixed after the next change.
Built in WaedaI connect a model like Claude to your app’s own data and rules: an assistant that answers from your real data, text drafted from your records, held to what actually exists and covered by tests.
Problems and solutions
Problems I ran into, and how I solved them
The hardest part of any project never shows on the screen. These are real situations from my projects: the problem, the decision I made, and the test that keeps it from coming back.
Waeda
Two customers ask for the same slot at the same moment.
How I solved it
The API locks the resource row before testing for an overlap, inside the transaction that writes the booking.
passed
ConcurrentBookingTestView the code on GitHubDiwan
Two customers buy the last piece in stock at once.
How I solved it
Checkout locks the product row with lockForUpdate inside the transaction that writes the order.
passed
StockTestView the code on GitHubDiwan
Retiring a piece used to erase it from every past order.
How I solved it
The columns release instead of cascading, and a name and image snapshot travel with the line.
passed
OrderHistoryTestView the code on GitHubLamma
One person records a disbursement and signs it off themselves.
How I solved it
The policy checks that in code rather than in the interface, and an approved record is reversed with a counter-entry rather than edited.
passed
DisbursementRecordTestView the code on GitHubOpsight
A cost hidden on screen is still there for anyone who opens the browser’s tools.
How I solved it
A field a role may not see is left out of the API response itself, not hidden in the interface.
passed
FieldRedactionTestView the code on GitHubDiwan
A sofa that fits the room sticks in the lift or at the turn of the stairs.
How I solved it
The way in is walked step by step with a 2 cm margin a side; the worst step decides, and an unmeasured one stays unchecked.
passed
PassageTestView the code on GitHubLamma
The page that finds the least-funded children slowed down as more were added.
How I solved it
Both sort directions were made the same so the engine reads the index backwards, served by an index on (status, funded_percent, id).
passed
OrphanGridSortTestView the code on GitHub
Behind the screen
What you don’t see on the screen is what protects it.
Scroll to see what happens behind a single button: a request through the server and the database, the tests that guard it, and a layer that turns away anyone who has no business being there.
Interface
Arabic and right to left from the first line, telling people in their own language what is happening and what to do next.
Server & API
Prices, stock and permissions are settled on the server, inside one transaction. Nothing that matters is left to what the browser sends.
Database
I design the tables so the schema itself stops the mistake before it happens, instead of us finding it after it has cost you.
Tests
Every rule your business depends on is guarded by a test that runs on every change, so a bug we fixed never quietly comes back.
Security
A request with no right to be there is turned away at the server’s door, not by hiding a button. Your customers’ data stays theirs.
Engineering rules
Six rules I don’t bend
Each one came from a real problem in an earlier project, which is why I don’t leave them to chance in yours.
The tools
What I work with, and where
No stars, no percentages. Each coloured dot means the tool is actually used in that project, and you can open it and see.
| Diwan | Waeda | Opsight | Takharruj | Lamma | ||
|---|---|---|---|---|---|---|
| Backend & databaseBusiness logic, permissions and transactions on the server, on MySQL schemas designed from scratch. | ||||||
| Laravel | Diwan | Waeda | Opsight | Takharruj | Lamma | |
| PHP | Diwan | Waeda | Opsight | Takharruj | Lamma | |
| MySQL | Diwan | Waeda | Opsight | Takharruj | Lamma | |
| REST API | not used | Waeda | Opsight | not used | Lamma | |
| Frontend developmentVue or React, chosen per project: a Vue console, a Next.js app. | ||||||
| Vue 3 | not used | Waeda | not used | not used | Lamma | |
| React | not used | not used | Opsight | Takharruj | not used | |
| Next.js | not used | not used | Opsight | Takharruj | not used | |
| UI developmentResponsive interfaces in Arabic and English, right to left and left to right. | ||||||
| Tailwind CSS | Diwan | Waeda | Opsight | Takharruj | Lamma | |
| Engineering & testingPHP tests for the rules, Vitest for the interface logic, Playwright in the browser. | ||||||
| Pest | Diwan | not used | Opsight | not used | Lamma | |
| PHPUnit | not used | Waeda | not used | Takharruj | not used | |
| Vitest | not used | Waeda | Opsight | not used | Lamma | |
| Playwright | not used | Waeda | Opsight | not used | Lamma | |
| AI integrationModels like Claude wired to the app’s own data and rules, with answers held to a fixed shape and read-only tools. | ||||||
| Claude API | Diwan | not used | not used | not used | not used | |
How I work
From your first message to handover
Five stages, so you know what happens after you write to me and what you receive at each one.
Understand what you need
You describe the project in your own words; no technical spec needed. I reply within a working day with the questions that pin down the scope and its hardest part.
Agree the scope and the plan
A written scope: the screens, the roles, the data and the rules. The price is fixed once the scope is agreed.
Build it in stages
The work is split into milestones, and payment follows them: a part at the start, then a part as each stage is delivered.
Test the rules that matter
Prices, stock, permissions and bookings are guarded by automated tests that run on every change, so a bug we fixed stays fixed.
Review, then hand over
You try the working application before handover. Support after delivery is agreed in the proposal.
Behind the camera

Ahmed Al-Hawajri
Laravel & PHP Developer · Gaza, Palestine
I don’t start from the screens. I start from the rules.
I’m Ahmed, a developer from Gaza. I build complete web applications on my own, and what I care about most isn’t how a screen looks but what happens when people actually use it.
The rules I work by weren’t decided in advance; each one came from a mistake. In Diwan, removing a product from the catalogue used to erase it from every past order, until I understood that a record of what happened doesn’t follow what’s on sale today. Since then it’s a written rule, with a test beside it.
- Multiple yearsbuilding web applications
- 5projects shipped with code
- 113app screens captured
The next project starts with a question from you. Tell me what’s getting in your way at work today, and we’ll work out how to fix it together.
Let’s start your project
Write in your own words; you don’t need a technical spec. I’ll reply within a working day with questions that pin down what we’re building and its hardest part.
What happens next
- You describe the projectA blank page or an existing codebase, however rough the idea is.
- I reply within a working dayWith the questions that pin down the scope and the hardest part.
- We agree, then startA clear scope and steps before the first line of code.
Or directly