Zero Lice
A bilingual healthcare platform for UAE families, designed around reassurance and action with live pricing, WhatsApp-first booking, RTL Arabic, and a Laravel-managed blog built to earn search traffic in both languages.
- Role
- Technical lead · Next.js development & API integration · DevSparks team delivery
- Services
- Bilingual UX architecture (EN/AR) · UI design system · Next.js 15 development · Laravel + MySQL backend · Dynamic pricing API integration · Blog & offers CMS · Bilingual technical & content SEO · Analytics & WhatsApp tracking
- Stack
- Next.js 15 · Laravel · MySQL · TypeScript · next-intl · SCSS · MUI · REST API
- Client
- Zero Lice UAE
- Industry
- Healthcare
- Timeline
- 10 weeks · 2024
01 / Business context
The Problem to Solve
Finding lice treatment can be stressful and stigmatized for families. Zero Lice needed a bilingual web presence that could explain the service clearly, reassure parents, and make pricing and booking easier to access in English and Arabic.
Zero Lice is a lice removal service for UAE families with in-home and in-clinic options. Because the subject can be stressful and stigmatized, the brand needed a bilingual web presence that feels clear, reassuring, and easy to act on — and one that families could actually find, since parents research this problem privately through search long before they call anyone. We delivered a Next.js 15 front end over a Laravel and MySQL backend, with RTL Arabic support, dynamic pricing, WhatsApp-first booking, and a bilingual blog built as a search-acquisition channel.
02 / From Scope to Launch
How the Work Moved
The work became clearer through decisions, working increments, and feedback—not a long wait for a final reveal.
06 Steps
Step 01
We started with stakeholder discovery and empathy mapping around a sensitive buying moment; the copy, colors, and flows were designed to reduce uncertainty before asking families to book.
Step 02
We designed bilingual-first rather than treating Arabic as a translation pass: both layouts were shaped together with RTL-mirrored grids, Cairo and Poppins typography, and a calm teal palette balancing credibility with warmth.
Step 03
We built the backend on Laravel and MySQL, holding services and pricing, blog posts and their per-locale metadata, marketing offers, and enquiries, and exposed it to the site as a REST API the marketing team administers directly.
Step 04
We built on Next.js 15 with next-intl routing, connected the pricing experience to that API, added the blog, and shaped a WhatsApp-first path for time-sensitive enquiries.
Step 05
We treated search as a delivery requirement rather than a launch checklist: server-rendered pages per locale, hreflang pairing between the Arabic and English versions of every page, localized slugs and metadata, structured data, and generated sitemaps — then built the blog as the surface that answers what parents actually search for.
Step 06
At launch we wired GTM and GA4 across the primary actions and tuned the experience for mobile booking journeys.
03 / Decisions that shaped the product
Key Product Decisions
Bilingual-first design, not a translation pass
- Business context
- Arabic support could have been bolted on after the English site was finished, which typically produces broken RTL layouts and awkward typography.
- Decision
- We designed both language experiences together from day one: RTL-mirrored grids, locale-aware routing via next-intl, and dedicated Arabic typography (Cairo alongside Poppins).
- Why
- For a UAE family audience, Arabic is a primary experience, not an afterthought. The testimonial confirms the payoff: the RTL build was flawless on the first pass.
WhatsApp-first booking with a form fallback
- Business context
- Families may arrive with a time-sensitive need, and a traditional multi-step booking form adds friction at an already stressful moment.
- Decision
- We made WhatsApp the primary contact path, backed by a form fallback, and optimized the flow for quick mobile contact.
- Why
- The familiar contact path reduces unnecessary steps, while event tracking lets the team understand how visitors move toward booking.
A Laravel content API instead of hardcoded content
- Business context
- The team needed to publish SEO blog posts and rotate marketing offers regularly, and shipping a deploy for every content change would have created a bottleneck. Pricing and services also had to stay editable without a developer.
- Decision
- We built the blog, offers, services, and pricing in a Laravel admin over MySQL and served them to the Next.js front end as a REST API, so the site consumes content headlessly rather than storing it in code.
- Why
- The marketing team can publish and launch offers without re-deploys, which keeps the SEO engine running independently of the development cycle — and keeping content in the same backend as pricing and enquiries meant one system to run the site rather than a CMS subscription bolted onto a separate API.
SEO as the acquisition channel, designed in from the start
- Business context
- Parents research head lice privately, in both Arabic and English, well before contacting a clinic. Paid ads for this category are expensive and reach people only while the budget runs, so the site had to earn that search demand itself — and a bilingual site gets this wrong easily, with the two languages competing for the same queries or the Arabic pages never being indexed properly.
- Decision
- We built the SEO foundation into the platform rather than adding it afterwards: server-rendered locale-specific pages, reciprocal hreflang between every Arabic and English page pair, per-locale canonical URLs, localized slugs, titles and descriptions editable per post from the Laravel admin, structured data for the local business, articles, and FAQs, generated per-locale sitemaps, and a blog architecture where posts answer real parent questions and link into the service and pricing pages.
- Why
- Search is where this audience starts, and content is the only channel that keeps working after the campaign budget stops. Building it into the platform means every new post inherits correct metadata, language pairing, and internal linking by default, instead of depending on someone remembering the SEO checklist each time.
04 / The product in use
What Was Built
Real interfaces across the customer and operational experience.
05 / How it was built
Engineering Decisions
Fully bilingual EN/AR platform on Next.js 15 with next-intl locale-aware routing, mirrored RTL layouts, and Arabic typography (Cairo + Poppins).
Laravel API over MySQL (be.zerolice.ae) holding services and pricing, blog posts with per-locale slugs and metadata, marketing offers, and submitted enquiries, administered by the marketing team without developer involvement.
Dynamic pricing engine pulling real-time prices from that REST API, with an in-salon vs. home-service toggle and group discounts.
Pages are server-rendered per locale for SEO and efficient mobile delivery, with Core Web Vitals tuned for mid-range phones.
Bilingual SEO built into the routing layer: reciprocal hreflang between every EN/AR page pair, per-locale canonical URLs and localized slugs, and generated sitemaps per language so neither version competes with or hides the other.
Structured data for the clinic as a local business, for blog articles, and for FAQ sections, with per-post titles, descriptions, and social preview metadata editable from the Laravel admin.
Blog architecture shaped around what parents search before booking — treatment questions, school notices, prevention — with posts linking into the service and pricing pages so content traffic has a path to an enquiry.
GTM, GA4, and event tracking wired across CTAs to measure booking conversion end-to-end, plus a dedicated partnership funnel for schools, nurseries, and groups of 10+.
06 / What changed
Delivered Outcome
Zero Lice launched with a consistent bilingual presence designed to make a sensitive service easier to understand and book.
English and Arabic journeys, live pricing, and WhatsApp-first booking were delivered as one coherent experience.
The team can update blog content, offers, services, and pricing from the Laravel admin without changing application code.
The site launched with its bilingual SEO foundation already in place — indexable server-rendered pages, correct EN/AR language pairing, structured data, and sitemaps — so publishing is the only ongoing work required to grow search presence.
Delivered in 10 weeks across two languages (EN/AR).
“They understood a family-facing healthcare brand instantly. The Arabic RTL build was flawless on the first pass.”
Facing a similar product challenge?
Bring the problem, the current state, and the outcome you need. We can turn that context into a clear product direction and a workable path to launch.