Web apps

We build web apps that your staff and customers sign in to and work in every day: dashboards for your operations team, portals for your customers and internal tools that replace spreadsheets. We build with React and Next.js, and with Angular, all in TypeScript. The same app supports Arabic and English from the start, and it goes through automated tests before release.

Who it is for

Businesses whose daily work is spread across spreadsheets, chat groups and phone calls, and that need one system their staff, partners or customers sign in to. It also fits startups building the first version of a web product, and companies with a mobile app that need the web dashboard behind it. If you need a few pages about your company, or a standard online shop with no custom workflow, a ready-made website or store platform will cost you less, and that is what we will suggest.

What we build

• Operations dashboards. One place to manage appointments, assignments, staff and documents, with live maps when your work happens in the field, and reports you can export.
• Admin panels for mobile apps. The control centre for your customer and driver apps: approve accounts, check uploaded documents, follow activity as it happens and deal with issues.
• Customer and learner portals. People sign in to enrol in programmes, pay, reach their content and follow their progress, while your staff decide who sees what.
• Internal tools that replace spreadsheets. Requests, approvals and records in one system you can search, with permissions for each team and a log of who changed what, and when.

How we build it

We write TypeScript in strict mode. Public pages that need to be found in search use React with Next.js, which generates them on the server. Signed-in dashboards and back offices use React or Angular, chosen to fit your team and the shape of the app.

Layouts are built to follow the direction of the language, so tables, side menus, forms and charts switch between Arabic and English without a separate stylesheet for each language.

Releases go through automated tests in CI before they reach your users, and permissions are checked on the server, not only hidden in the interface. The tests cover the journeys that matter most, such as signing in, permissions and sending forms.

Our accessibility target is WCAG 2.2 level AA, checked with automated scans and then by hand with a keyboard and a screen reader, in both languages. For speed, we measure Core Web Vitals with Lighthouse on the staging site before launch.

We deploy to the hosting that suits the app, such as Cloudflare, Vercel, or Docker containers on AWS or Google Cloud, in a region you choose from those the provider offers.

Timeline and cost

Time and cost depend mostly on:

• roles and permissions: an admin and a user is simpler than permissions that differ per branch or per organisation;
• dashboards and reports: live charts, bulk imports from Excel, and PDFs or invoices generated on the server;
• connections to your ERP, CRM, accounting system or payment gateway;
• moving your existing data from spreadsheets or an old database into the new system;
• Arabic and English in the same app, with right-to-left layouts.

After the free call, you get a written scope with the timeline and the price, before you pay any deposit.