Skip to content
axelseyer
enes

Case studies

Projects shaped by product constraints, not just technology choices.

The work here is presented the way it happens in practice: business context, implementation decisions, and the frontend details that changed the outcome.

2025

Commerce frontend refresh

Rebuilt the purchase path for a high-traffic commerce experience where speed, trust, and clarity directly affected conversion.

Featured case

Context

The product had fragmented flows, uneven UI quality, and measurable friction during the first-time purchase journey.

Approach

I introduced a modular React architecture, hardened the design-system surface, and prioritized sequence-level improvements instead of isolated UI tweaks.

Why it matters

Representative of the kind of work where frontend quality is tied to business outcomes, experimentation, and cross-functional decision-making.

Key decisions

Performance

Deferred non-critical analytics, reduced hydration surfaces, and optimized image delivery around the most conversion-sensitive screens.

UX

Simplified decision points, improved hierarchy, and added clearer feedback around pricing, validation, and checkout progression.

Accessibility

Improved focus management, error semantics, and keyboard handling for modal and step-based interactions.

Tech stack

  • Next.js
  • TypeScript
  • Design Systems
  • Analytics

Signals

  • LCP -34%
  • Conversion +11%
  • CLS 0.02

2024

Platform observability dashboard

Designed an internal operational UI for teams making time-sensitive decisions from noisy multi-source data.

Featured case

Context

Operators depended on disconnected dashboards with inconsistent terminology and slow workflows during incidents.

Approach

Restructured the information model, created reusable dashboard patterns, and aligned engineering and design around operator priorities.

Why it matters

Shows how product thinking, accessibility, and system design influence enterprise-grade interfaces beyond marketing surfaces.

Key decisions

Performance

Virtualized dense tables, introduced request prioritization, and moved derived calculations out of the render path.

UX

Separated monitoring from action-oriented states so the interface could support both quick scanning and deeper diagnosis.

Accessibility

Added non-visual state announcements, improved chart descriptions, and hardened color-independent status communication.

Tech stack

  • React
  • Node
  • SQL
  • Data Viz

Signals

  • TTI -28%
  • Task time -22%
  • Audit score 100

2026

Interactive brand experiment

Built an experimental interaction prototype to explore how motion and depth can strengthen storytelling without degrading performance.

Featured case

Context

The challenge was balancing expressive visuals with production discipline and accessible fallbacks.

Approach

I isolated the experience from the primary application shell, used progressive enhancement, and treated motion as content rather than decoration.

Why it matters

Captures the intersection of product polish, technical rigor, and curiosity for emerging interfaces.

Key decisions

Performance

Kept WebGL isolated, code-split the scene, and avoided shipping heavy experimental code to the main portfolio routes.

UX

Used motion to guide attention and reinforce hierarchy instead of competing with the message.

Accessibility

Preserved readable static context, resilient contrast, and meaningful content outside the animated layer.

Tech stack

  • React Three Fiber
  • GSAP
  • WebGL
  • Motion Design

Signals

  • Lazy loaded
  • Reduced JS on main route
  • Motion safe