scndcorp
Available
Work
Colonna AssurancesFull-Stack Developer

Full platform and policyholder app overhaul for Colonna Assurances

Multilingual Next.js platform and mobile app for 200,000 policyholders, with integration of a partner reimbursement API.

Colonna Assurances

Challenge

Colonna Assurances had an outdated site: non-optimized use of its health reimbursement API, responsive and performance issues, an aging interface, no multilingual support, no personalization, no ownership on Colonna's side, and no mobile app. Qadence (in charge of Colonna's digital transition) commissioned a full overhaul.

Impact

  • 200,000 target policyholders covered by the platform
  • Configurable platform, alignable with Colonna's business logic: potentially infinite time savings
  • Multilingual from v1
  • Colonna ownership restored (vs. previous technical dependency)
  • Native mobile app available in addition to the web platform
1 / 6
Colonna Assurances · 1Colonna Assurances · 2Colonna Assurances · 3Colonna Assurances · 4Colonna Assurances · 5Colonna Assurances · 6

Also on mobile

Colonna Assurances · mobile 1
Colonna Assurances · mobile 2
Colonna Assurances · mobile 3

Context

Colonna Assurances is a health insurance player whose reimbursements rely on the engine operated by a technical partner. The overhaul, started in January 2026, is led on Colonna's side by Qadence, in charge of its digital transition.

The invisible constraint: no access to the API

The first month: no documentation. The second: no access. So I reverse-engineered how the partner API was used by other sites to reconstruct internal documentation, then built a MOCK_API=true mode based on MSW that faithfully reproduces the API's behavior. The result: we were able to develop in parallel while waiting, and today I have a better knowledge of this API than the partner's web service itself.

What was delivered

  • Multilingual Next.js 16 web platform, in-house design system on shadcn/ui
  • Native mobile app
  • NextAuth v5 auth coupled with the partner API (JWT)
  • Automated tracking of user procedures (useSeenDemarches hook)
  • PDF generation of third-party payment cards (pdf-lib)
  • Apple Wallet (PassKit) integration + QR codes
  • Reimbursements dashboards (Chart.js)
  • Contentful CMS for editorial content
  • OpenNext deployment on Cloudflare

Stack & ownership

Today, I have ownership of all the features of the platform and the app, even those I contributed to as part of a team.

Stack

The technologies used on this mission.

  • Next.js 16 (App Router)
  • TypeScript
  • Tailwind CSS v4
  • shadcn/ui
  • Partner health reimbursement API (REST)
  • Next.js Route Handlers
  • PostgreSQL
  • Drizzle ORM
  • next-intl (i18n)
  • NextAuth v5 (Auth.js)
  • MSW (mock API)
  • Contentful (CMS)
  • pdf-lib (PDF)
  • PassKit (Apple Wallet)
  • Chart.js
  • OpenNext + Cloudflare

A similar project in mind?

Let's talk through your challenges and see how to turn your vision into maintainable, tested technical reality.