Skip to content
ERErick Rodovalho

Frontend & CRO Development

I turn Figma files and CRO hypotheses into fast, accessible storefronts and product UIs — on Shopify, WordPress and Webflow, or custom-built in React and Next.js.

  • CRO Development
  • Shopify
  • WordPress
  • Webflow
  • React
  • Next.js
1{%- liquid2  assign tiers = product.metafields.custom.bundle_tiers.value3-%}4<bundle-selector data-product-id="{{ product.id }}">5  {%- for tier in tiers -%}6    <label class="tier">7      <input type="radio" name="tier" value="{{ tier.qty }}"8        {% if forloop.index == 2 %}checked{% endif %}>9      <span>{{ tier.title }}</span>10      <span>{{ tier.price | money }}</span>11    </label>12  {%- endfor -%}13</bundle-selector>
Real patterns from my day-to-day: a metafield-driven bundle selector, an experiment hook and an ISR product page.

What I deliver

The pieces of a store that move revenue.

Product pages

Hierarchy, trust, variant logic and sticky add-to-cart — PDPs engineered to answer objections before they're asked.

Bundle builders

Mix-and-match, tiered discounts and quantity breaks driven by metafields, not hard-coded markup.

A/B test variants

Clean, isolated variant code for Intelligems, VWO, Convert or Optimizely — no flicker, no broken controls.

Cart drawers & upsells

Free-shipping bars, rewards and one-click upsells that lift order value without adding friction.

Subscription flows

Recharge and native subscriptions: subscribe-and-save UX, prepaid plans, swaps and portals.

Landing & advertorials

High-intent pages built around the ad's promise, ready for paid traffic and testing on day one.

The frontend stack

Six platforms. One standard of craft.

Pick a technology to see what I use it for and the libraries behind it.

CRO Development

Hypothesis-driven builds: A/B and multivariate tests, PDP and funnel experiments, clean variant code that never breaks the control.

Libraries & tools I use

  • Intelligems
  • VWO
  • Convert
  • Optimizely
  • Shoplift
  • GA4
  • Google Tag Manager
  • Hotjar
  • Microsoft Clarity
  • Triple Whale

Non-negotiables

What every frontend I ship has in common.

A performance budget

LCP under 2.5 s, CLS under 0.1, and JavaScript that earns its bytes. Measured on real mobile devices.

Accessibility

Semantic HTML, keyboard paths, visible focus and WCAG 2.1 AA contrast — good for people, good for SEO.

Design fidelity

Pixel-accurate to Figma, with the judgment to flag what won't work on a 375 px screen.

Open to full-time & contract roles

Need a frontend that pays for itself?

Hiring for a role or scoping a project? I reply within one business day.

esc

⌘K to open anywhere

Hiring? Let's talk

This page is also available in Portuguese.