THE BRIEF
FRAMER · CUSTOM CODE · GEOLOCATION
THE PROBLEM
BUG FIX · GEOLOCATION · CUSTOM COMPONENT
Peec.ai's pricing page had a custom component that was supposed to detect the visitor's browser locale and display the right currency — USD or EUR. It wasn't working reliably. The wrong price was showing for the wrong audience, which is exactly the kind of detail that kills conversion on a pricing page.
THE SOLUTION
Traced the bug into the custom code component powering the price cards. The geolocation logic was reading the browser locale incorrectly and failing silently — defaulting to the wrong currency without any visible error. Fixed the detection logic so USD and EUR display correctly based on where the visitor actually is.
Skeleton Loader
Currency detection takes a moment. Without a loading state the price cards flash the wrong value before correcting — a jarring experience on a page where trust matters most. Built a skeleton loader that holds the layout while the locale is resolved, so the correct price appears the first time, cleanly.
VISUAL SYSTEM & OUTPUT
The page looked fine — the bug was inside the custom Framer component code. Debugging someone else's custom component means understanding what it was trying to do before you can fix what it got wrong. The geolocation logic wasn't broken outright, it was reading the wrong browser property. One targeted fix, tested across browsers and locations with a VPN.
Everything new in Framer, monthly.
Product updates, fresh templates & components, and Berlin Framer meetups — one email a month, no spam.