Active client project · Live2026

PulseMobile

Digital service platform for patient transport

My role

Product Strategy · UX/UI · Full-stack · CMS · Deployment

Visit live project

01

Project overview

PulseMobile is a mobile-first website for a German patient transport company, designed to make services, transport types and pricing understandable before a customer makes contact.

A conditional form prepares a structured WhatsApp enquiry for personal confirmation, while Sanity Studio lets the business update services, prices and content without code changes.

02

Real product screenshots

Only real product screenshots will be placed here—no mockups or stock imagery.

01

Homepage and service presentation

Screenshot

02

Interactive transport pricing

Screenshot

03

Structured trip request flow

Screenshot

04

Sanity content-management panel

Screenshot

03

System architecture

Customer experience

Services · Pricing · Cost coverage · Legal clarity

Next.js application

Responsive UI · Conditional forms · Theme · PWA metadata

Sanity content layer

Studio · Structured content · 60-second revalidation · Local fallback

Contact handoff

Phone · Prefilled WhatsApp · Personal confirmation

04

Project status

Built

  • Mobile-first responsive customer journey
  • Interactive pricing for seated, wheelchair and carrying-chair transport
  • Conditional insurance and self-pay request logic
  • Structured WhatsApp enquiry generation
  • Embedded Sanity Studio with editable services, prices, FAQs and images
  • Typed fallback content when Sanity is unavailable
  • SEO, PWA metadata, German legal pages and Vercel deployment

In active development

  • Real production screenshots and ongoing content updates

Planned

  • Optional direct booking backend when the operating process requires it
  • Consent-aware conversion analytics

05

Engineering decisions

Why does an enquiry open WhatsApp instead of creating an automatic booking?

Every trip needs personal verification. A structured handoff gives the operator complete information without promising availability or storing sensitive enquiry data in an unnecessary backend.

Why combine a CMS with local fallback data?

The business can update services, prices and content independently, while the public website remains usable if Sanity is missing or temporarily unreachable.

Why was the experience designed mobile-first?

Customers mainly need to understand the service, call or send an enquiry quickly, so the interface prioritizes legibility and low-friction contact.

06

Challenges solved

  • 01Turning a trust-based offline service into a clear digital journey
  • 02Generating a complete WhatsApp request from conditional form state
  • 03Merging CMS content with strongly typed fallback data
  • 04Balancing conversion-focused calls to action with legal and operational clarity

07

Technology stack

Application

  • Next.js 15
  • React 19
  • TypeScript
  • Tailwind CSS 4

Content

  • Sanity Studio
  • GROQ
  • next-sanity
  • Typed fallback data

Experience

  • Responsive UI
  • Conditional forms
  • WhatsApp deep links
  • PWA manifest

Production

  • Vercel
  • ISR / revalidation
  • SEO metadata
  • German legal pages

08

What it demonstrates

PulseMobile demonstrates how I turn a local service into a clear, maintainable customer journey with business logic, editable content and production delivery.

Who this is relevant for

Relevant for local service businesses, healthcare providers, transport companies and small teams that need a fast customer-facing platform, independently editable content and a structured lead or enquiry workflow.