Custom PHP and MySQL application development in Durban

Why this matters for South Africa specifically

Data cost and intermittent connectivity are real constraints for a large share of South African visitors, so page weight is a commercial metric here, not a vanity score. I build to a hard kilobyte budget on ZA projects.

What actually ships when a Durban project goes live

A handover for a Durban client is not a link and a login. It is the repository, the hosting account in your name, the domain registered to you, the payment provider account under your business, and a written record of every credential as it was created rather than dumped in one email at the end.

The test I apply is uncomfortable but correct: if I disappeared tomorrow, could another developer pick this up on Monday without calling me? If the answer is no, the handover is not finished. That standard is why the documentation takes a day I do not bill separately — it is part of the build, not an upsell.

Education and training providers in Durban

Course pages are the whole site. Each needs the outcome, the duration, the price, the prerequisites and the next start date visible without scrolling — and each needs to be its own indexable URL, because people search for the course, never for a training provider they have not heard of.

The recurring failure is a single "Courses" page listing twenty courses. It ranks for nothing because it is specifically about nothing. Twenty pages, each genuinely about one course, is more work and is the difference between a site that recruits and a brochure that sits there.

A mobile layout nobody tested on a real phone

Desktop-first builds fail in predictable places: a navigation menu that cannot be closed, a table forcing the whole page sideways, tap targets too close together, and a sticky banner sitting over the button. Each one is invisible on a laptop and each one loses customers.

Most visitors to a Durban small business site arrive on a phone, so I design at phone width first and widen from there. That ordering is not a stylistic preference — it is the only way the small screen gets the attention the majority of your traffic deserves.

What I am not claiming about Durban

• I have no office, postal address or phone number in Durban
• I cannot meet you in person, and if that is a requirement you should hire locally
• I am not claiming existing clients in Durban specifically — my live work is listed on the work page and you can check it
• Nothing on this page is a guarantee of search rankings, which no developer can honestly offer

Custom PHP and MySQL application development in Durban — common questions

Do you provide ongoing maintenance after launch?

Thirty days of snag fixes are included after launch at no extra cost — anything that does not work as specified gets fixed. Beyond that there are monthly plans for updates, backups, monitoring and small changes. They are optional and cancellable; a site handed over properly does not require a retainer to keep running.

Can you fix my existing site rather than rebuild it?

Often, yes, and it is usually the cheaper answer. Speed problems, a broken mobile layout, a form that silently fails or missing structured data are all fixable on the site you already have. I will tell you which of the two you need after looking, and a rebuild only gets recommended when the fix would cost more than starting again.

What hours will you be available to us in Durban?

My working day lands at 06:00–15:00 in your time, which is roughly 6 hours inside a normal Durban working day. In practice you can raise something in the morning and have it answered the same morning, and a scheduled call is easy to place at a civilised hour for both of us.

How long does a Durban project actually take?

Three days for a business site, seven for a store, ten for a custom application. That holds because the process is fixed rather than improvised and because your content exists on day one. What stretches a build is almost never the code — it is waiting for copy, logos and photographs, so those are requested before the clock starts.

What payment methods can my Durban checkout accept?

For South Africa: Stripe, PayFast, Yoco, Ozow for instant EFT, and SnapScan. The right combination depends on your average basket and your customers, and picking wrong is expensive — the payment method a buyer expects but cannot find is one of the most common reasons a checkout is abandoned at the final step.

How do you handle our customers' data under POPIA?

Your customer data is governed by POPIA, the Protection of Personal Information Act, and sending it to a developer in Pakistan is a restricted transfer. That is resolved by Section 72 of POPIA governs transfers abroad and the DPA records the lawful basis, published on this site and pre-signed before you send an enquiry — not drafted after you ask about it.

Who owns the website when it is finished?

You do, completely. The domain is registered in your name, hosting sits in your account, the code lives in a repository you control, and any payment provider account is opened in your business name. Credentials are handed to you as they are created rather than at the end, so you are never locked out of your own site.