Custom PHP and MySQL application development in Nantes

Why this matters for France specifically

The CNIL enforces cookie rules more aggressively than most EU regulators, and "refuse all" must be as easy as "accept all". A French site running a standard one-button banner is carrying a known, fineable defect.

Why Nantes sites are built to be edited by you

A site you cannot update is a site that decays. Prices go stale, staff leave, the opening hours are wrong for six months. So the parts of a Nantes build that change often — text, images, prices, opening hours, team members — are editable by you without touching code or paying me.

That is a design decision with a cost: it takes longer to build an editable block than a hard-coded one. It is worth it because the alternative is a maintenance dependency that benefits me and not you, and a developer whose income depends on you being unable to change your own opening hours is not aligned with your interests.

Education and training providers in Nantes

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 Nantes 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 Nantes

• I have no office, postal address or phone number in Nantes
• I cannot meet you in person, and if that is a requirement you should hire locally
• I am not claiming existing clients in Nantes 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 Nantes — common questions

What payment methods can my Nantes checkout accept?

For France: Cartes Bancaires, Stripe, Lydia, and PayPal. 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 long does a Nantes 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 hours will you be available to us in Nantes?

My working day lands at 06:00–15:00 in your time, which is roughly 6 hours inside a normal Nantes 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.

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.

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.

Will the site actually rank in Nantes search results?

The build handles what is technically controllable: crawlable HTML, correct headings, structured data, fast pages, a clean sitemap and Search Console set up on day one. Ranking also depends on your competitors, your domain's age and the links pointing at you, which no developer controls. Anyone guaranteeing a position is guessing or lying.

What happens if I am not happy with the result?

Work is delivered in milestones against a written scope, and you review each one on a staging URL before it is paid for. If the delivered milestone does not match the scope, it gets corrected before anything moves forward. That structure exists so disagreement is resolved at the stage it happens rather than at the end when it is expensive.