Policy documents and a React Native claims flow

Customers needed a polished multi-page policy document after purchase, with pet details, the coverage they bought and benefits that vary by sales channel, matching the creative team's design. Separately, the member app needed a claims experience that people could finish on a phone, with photos and records.

• Document generation: React and Tailwind templates rendered to PDF from the creative team's design, packaged as a library with cloud-infrastructure assets and a single facade over the PDF service. Eight releases in about ten weeks moved PDF rendering out of the funnel and into the core API.
• Kept a Canada-market fallback document alive and shipped a same-day priority fix to partner member-card data, coordinating changes across the funnel, core API and library.
• React Native (Expo) claims for iOS, Android and web: claim detail screens with status-specific layouts, a claims index and an add-a-pet flow.
• A feature-flagged six-step claim submission flow, delivered as stacked pull requests: a state-machine store, routing, a tile picker, camera and file upload with OCR, then story, records and direct-deposit steps. Plus an iOS combobox and cross-platform QA on desktop, mobile web, iOS and Android.
• Mobile UX fixes across iPhone and iPad: currency masks, tablet select widths, iOS input zoom and scroll-on-error.

The document library is largely my work by commit history (14 of 19 commits), and PDF rendering now sits in the core API rather than the funnel. The claim flow was delivered behind a feature flag as reviewed, stacked pull requests.

No usage or conversion figures are claimed.