Apps & software for the UAE, built in Lahore.

If your customers carry both iPhones and Android phones, the app has to be on both stores from launch. Two separate native teams means two backlogs, two sets of bugs and a feature that reaches Android a month after iOS, so we build mobile apps in React Native and TypeScript: one codebase, one release plan, and one team answering for both stores.

The app is only half of it. Every app talks to a backend, and we build that too, so the app and the system behind it agree on what an order, a booking or a course actually is. At the end of each slice you get an installable build, tested on real phones, older ones included, and we handle the releases to the App Store and Google Play.

The Bright Future student apps are the proof. They run on iOS and Android in Kuwait: students browse a catalogue, pay for enrolment inside the app and watch HD lessons that stay locked to the account that bought them.

A lot of UAE businesses outgrow WhatsApp groups and shared spreadsheets long before they outgrow their market. That is usually a web application problem: a customer portal, an order or booking system, or a dashboard that shows the owner what is happening without waiting for a weekly report.

We build those on Laravel, Node and React, with the admin screens your team lives in designed as carefully as the customer-facing ones. Bright Future’s admin dashboard is a good example: staff run enrolments, revenue, transactions, invoices, coupons and reports from one screen, every working day.

Where a process genuinely does not fit any packaged product, we build custom software around it, and where a package does fit, we will tell you to buy it. Alongside that we set up CRMs, automate repetitive admin with AI where it helps, and host the result in the cloud.

Checkout is where bugs cost money directly. We run MyFatoorah in production for Bright Future in Kuwait, KNET included, and Stripe for card payments for clients elsewhere, so we know the parts beyond the pay button: webhooks, retries, refunds and reconciliation against the invoice.

For a UAE business we would choose the gateway around your bank, your customers and the cards they carry, not around what we used last time. Every flow is tested end to end in the gateway’s sandbox, including failed, timed-out and duplicated payments, before a real customer sees it.

Instalments, coupons and down payments are part of the same job. On Bright Future, access follows the payment: content unlocks when a payment clears, and the record always agrees with the invoice.

Freight is one of our two specialisms. Cargonio, the freight ERP we built and own, runs air and sea jobs, export and import, master and house bills, billing, accounts, HR and payroll in one system, and its demo shipment runs from Karachi to Jebel Ali, a lane any Gulf forwarder will recognise.

Two forwarders in Pakistan run on Cargonio today. Its built-in tax reporting is written for Pakistan’s PRA and FBR, so for a UAE forwarder we would treat VAT invoicing as part of the scope rather than assume it is already done, and your tax adviser should confirm what your invoices need to carry.

If you want to understand the domain first, our freight forwarding software page covers how we think about jobs, documents and billing, and where a packaged system usually stops fitting.

We do not keep an office in the UAE and will not rent an address in a free zone to look local. UAE projects run remotely from our engineering office in Lahore, with the head office in Hobart: video calls, a shared project board you can open at any time, and a demo of working software at the end of each phase.

The UAE is on UTC+4 and Lahore on UTC+5, and neither changes its clocks, so Lahore is one hour ahead of Dubai all year. Since 2022 the UAE’s official working week has run Monday to Friday, the same days we work, so a call can sit almost anywhere in your day.

Nothing is built until the scope is written down and agreed. The work is then divided into phases, each with its own price and each ending in software you can use, so a large build never turns into a year of guesswork. The code and every account stay yours, with no lock-in.