Selected work / 05

Case Studies

Products I worked on, the problems I helped solve, and the decisions behind what shipped.

01react / styled-components

Hapvida Design System

Internal React component library for healthcare product teams at Brazil's largest health operator.

My role

Co-created and maintain the library: component APIs, Storybook documentation, design-system adoption, and production UI consistency across squads.

reactstyled-componentstypescriptstorybook

CompanyPrivate internal library

Context & technical decisions

Problem

Multiple healthcare squads needed to ship consistent flows without rebuilding the same inputs, tables, layout primitives, and visual states in each product.

Constraints

Private healthcare context, multiple product surfaces, legacy screens, and incremental adoption without disruptive breaking changes.

Technical decisions

Designed typed component APIs that remove choices instead of adding configuration noise
Used styled-components and design tokens to keep theming predictable
Documented usage patterns in Storybook so teams could self-serve

02react-native / typescript

Azul Airlines App

Consumer-facing React Native app for Azul Linhas Aéreas, with 10M+ combined downloads.

My role

React Native engineer shipping customer-facing features across check-in, boarding pass, loyalty, post-flight, and release polish.

react-nativetypescriptredux

Public app, client-owned store listingsPrivate client code

Context & technical decisions

Problem

Airline mobile flows need to be fast, clear, and resilient because users often interact with them under time pressure at the airport.

Constraints

Large consumer app, airline domain complexity, private client code, and production expectations across both mobile platforms.

Technical decisions

Kept screens predictable with typed navigation and reusable UI patterns
Balanced product polish with reliability in travel-critical flows
Handled Android and iOS differences during implementation and release cycles

03react-native / llm

AzulGPT

Internal mobile assistant for Azul employees, built with a custom React Native shell on top of LLM APIs.

My role

React Native contributor focused on the mobile shell, interaction quality, and the constraints of bringing LLM features into an internal employee tool.

react-nativellmtypescript

Internal employee toolPrivate client code

Context & technical decisions

Problem

Employees needed a practical way to access AI-assisted internal workflows from mobile without losing the clarity and guardrails expected in enterprise tools.

Constraints

Internal-only product, evolving LLM APIs, enterprise expectations, and sensitive workflow context.

Technical decisions

Kept the interface focused on task completion instead of chatbot novelty
Used React Native patterns that could fit existing mobile delivery processes
Treated loading, error, and empty states as core product states

04nextjs / react

DomPixel Checkout

Next.js checkout flow with credit-card processing, shipped end-to-end in a small-team environment.

My role

Frontend developer responsible for implementing the checkout UI, integrating payment flows, and supporting release to production.

nextjsreact

Private commercial code

Context & technical decisions

Problem

The business needed a reliable web checkout flow that could handle payment steps clearly and reduce friction for customers.

Constraints

Small team, payment complexity, customer trust requirements, and limited room for unclear error states.

Technical decisions

Used Next.js and React to keep checkout screens fast and maintainable
Made form states explicit for validation, loading, and payment feedback
Kept release work close to implementation so production issues could be handled quickly

05In my day-to-day work

Skills & Tools

See how I build the skills and tools I use in my work.

Explore Skills & Tools