WEB APPS · PORTALS · DUBAI
I'm Emad Yahya — a systems engineer in Dubai who builds custom web applications: portals, dashboards and workflow tools that live in the browser, with logins, roles and a real database behind them. Not a website that describes your business — an application your team runs it on.
Every system I have shipped is a web application: a full HR platform, a self-serve booking platform, an Arabic-first pharmacy POS, an IT asset manager tracking 150+ devices, and an AI SaaS product. Eight of them are in production inside Dubai businesses right now — opened in a browser every working day, no installs, no per-user license fees.
A website is pages people read: your story, your services, a contact form. A web application is software people work in: staff log in, data moves through workflows, managers read dashboards, and the business's day actually happens inside it. Same browser — completely different build.
That difference is my specialty. Plenty of Dubai developers build good websites; far fewer have shipped applications that teams depend on every working day. This page is about that second thing: logins, roles, records, approvals and reports — engineered like a product, not decorated like a brochure.
Builds are React/TypeScript with clean APIs — the same stack my systems run on in production today. By day I run enterprise IT for a Dubai real estate firm, so backups, permissions, security hygiene and performance budgets are defaults, not add-ons.
One engineer end to end: the person who scopes the application is the person who codes it, deploys it and answers the phone after launch. You review real working screens within days, not wireframes after weeks — and at handover you own everything: code, database, hosting and accounts, registered in your name.
It depends entirely on scope — a focused portal with logins and one workflow is a much smaller build than a full multi-role platform. Every project is priced per feature set, and you get a fixed written quote within 24 hours of the brief. No per-user license fees afterwards: you own the application.
A website presents information — pages, images, a contact form. A web application does work: users log in, create and edit records, follow workflows and read dashboards, all backed by a database. If your team would use it daily to run part of the business, you need a web application, and it has to be engineered like one.
The number of user roles usually decides it. One role, one workflow, a small set of screens — a portal a single team or your customers log into — takes 2–4 weeks. Several roles that each see different data and hand work to one another, the shape of the HR platform I built, takes 4–8 weeks depending on how many of those handoffs exist. Both windows come from applications now running in Dubai, not from a template estimate.
Yes, and the change is mostly structural. A shared sheet cannot tell you who changed a cell, and a chat thread cannot tell you the current status of anything. The first step is turning those columns into a real data model — records that have an owner, a status and a history — and then putting logins over it, so every edit is attached to the person who made it and earlier versions stay readable instead of being overwritten. Your current rows come in as the starting data rather than being discarded. The HR platform and the IT asset manager both began exactly like this, and both retired the spreadsheets they replaced.
Honest answer: for most business tools, a responsive web application is enough — it runs on every phone, tablet and desktop through the browser, with no app-store submissions and no forcing staff to install updates. Native apps make sense for consumer products that need push notifications or offline hardware access; for portals, dashboards and internal tools, the browser wins on cost and speed.
Yes. In an application the hard part of Arabic is not the wording, it is the interface: tables, forms, filters and navigation all have to run right-to-left and still stay readable when a manager is scanning a dashboard at speed. I lay those screens out for Arabic from the first draft instead of mirroring an English build at the end — the way the pharmacy POS I put into production was made. I am a native Arabic speaker, so the labels, buttons and messages inside the app are written rather than passed through a translator, and both languages ship in the same application, not as a second project.
The source repository, the database with every record in it, the hosting account, and the top-level admin login that sits above all the other user roles — all registered in your name at handover. Hand the repository to another developer whenever you decide to and the application keeps running exactly as it did. Maintenance is something you can choose to buy from me; it is never the thing keeping your access alive.
Emad Yahya — portfolio · emaadyahya4@gmail.com · WhatsApp +971 566 392 647