Giovanni Suarez

Web developer. Ecommerce systems and digital products.
Code, Interfaces, and Expression — Past, Present, Next.

About

I build web systems that ship, scale, and evolve.

My work is centered on ecommerce, especially Shopify, but extends naturally into digital products, catalogs, personal sites, and lightweight web applications. I focus on how systems are built, how interfaces behave, and how code holds up over time.

I’ve been building on the web long enough to have seen multiple platform shifts — I’m exploring, testing, and building toward what’s next.

What I work on

Most of my work falls into a few overlapping areas.

Ecommerce systems

Shopify-based systems designed to sell, scale, and adapt.

Platforms & tools:

Shopify, checkout flows, Rebuy, Klaviyo, subscriptions, analytics integrations

Digital products

Web-based products, tools, and internal systems.

Technologies:

React, Next.js, lightweight web apps, interactive tools, product interfaces

Front-end development

Interfaces that feel fast, clear, and intentional.

Focus areas:

HTML, CSS, JavaScript, component-driven UI, interface logic, user experience

System design

Structure that holds up over time.

Principles & concerns:

Performance, accessibility, maintainability, scalability, long-term evolution

Platforms & workflows

Modern tooling for building and shipping on the web.

Stack & process:

GitHub, Vercel, AI-assisted development (Cursor), iterative and component-based workflows

Content & CMS work

For projects where content and editorial structure matter.

Platforms:

WordPress, custom themes, CMS-driven sites, migrations and long-term maintenance

Code, interfaces, and expression

I see the web as both a technical platform and a creative medium.

Code defines structure.
Interfaces shape behavior.
Good systems connect structure and behavior into experience.

Past, present, next

Past

Around 12 years old, a black-and-white TV and a Sinclair ZX-81

became my first development environment. Writing BASIC, I discovered that logic could shape outcomes — that a simple rule could decide what was possible and what wasn't. That's when code stopped feeling abstract and started feeling fun.

That curiosity turned into my first professional work building educational games for McGraw-Hill in Bogotá, Colombia. Interactive CD-ROMs shipped with textbooks, designed to teach math and history through play. It was an early lesson in software as both system and creative medium.

From there, I moved into agency work and later into freelancing, collaborating with teams and clients across the US, Latin America, and Europe. Over time, the work grew from individual projects into larger systems — and from local work into global collaboration.

Present

I build and maintain production ecommerce systems and digital products.

This work lives where decisions matter: storefronts, checkout flows, catalogs, and applications. Performance, UX, and reliability aren't abstract — they're felt immediately.

Much of my work is with CPG brands, many based in California. Small teams. Real products. Clear intent. I stay close to the code and close to the product, shaping systems that are designed to evolve.

I've worked with brands like Waay, Grüvi, Dermasensa, Mālie, Just Ice Tea, and Westcove among others — building digital foundations that match the brand, not the hype.

AI-native development.

Vibe-coding.
A technical background meeting intuition and flow in code.

Tools that collapse the gap between idea and execution.
A developer's role defined less by syntax, more by architecture and insight.

Ibelieveinvibe—notassomethingvagueoraesthetic,butasintuitionandflowwhilebuildingcode.

How I work

◆

Clear structure over noise

◇

Small, composable systems

○

Code that survives iteration

△

Interfaces that respect users

Collaboration and teamwork

I've worked across agencies, product teams, and direct client relationships. That range made collaboration a core part of how I work.

I'm comfortable joining existing teams, sharing context early, and keeping communication close to the work. Most collaboration happens where the work lives — in Slack for day-to-day flow and GitHub for code, reviews, and iteration.

The goal is simple: reduce friction, keep momentum, and build systems together.