Fizzara - Zero Sugar Soda Concept
← All projectsProject description
- Interactive hero with a 3D can that tilts toward the cursor, floating fruit that parts around the pointer, and rising bubbles
- Five flavor themes: one click morphs the background, spins the can, swaps its label, and trades the fruit models
- Can modeled in Blender with generated label artwork; fruit models created with an AI image-to-3D pipeline and optimized for the web
- Scroll sections, story pages, and a Google Maps store locator with custom fruit markers and animated info cards
- Dedicated phone layout with a bottom pill nav; built with Next.js, TypeScript, GSAP, and model-viewer as a static site on Netlify
Overview
Fizzara is a concept brand site for a zero sugar sparkling soda. It is built around a real-time 3D can that reacts to the cursor, one-click flavour themes, and a store locator with fruit markers.
The problem
Drink brands live on shelf appeal, and a flat product photo loses most of it online. The brief was a site that feels like picking up the can: playful, tactile and quick to switch between flavours.
What I built
- Interactive hero with a 3D can that tilts toward the cursor, floating fruit that parts around the pointer, and rising bubbles
- Five flavour themes: one click morphs the background, spins the can, swaps its label and trades the fruit models
- Can modelled in Blender with generated label artwork; fruit models made with an AI image-to-3D pipeline and optimised for the web
- Scroll sections, story pages and a map-based store locator with custom fruit markers and animated info cards
- Dedicated phone layout with a bottom pill navigation
Architecture
A static Next.js and TypeScript site on Netlify. model-viewer renders the 3D can and fruit, GSAP drives the motion, and a maps service powers the store locator.
A high-level view. Endpoints, hosts and security details are left out on purpose.
Key decisions
- 01
One click changes the whole scene
Why: Background, label and fruit all swap together, so each flavour feels like its own world instead of a colour filter.
Trade-off: Every flavour needs its own label and fruit assets.
- 02
model-viewer for the 3D
Why: A ready web component handles loading and rendering, which keeps the custom code focused on interaction.
Trade-off: Less low-level control than a hand-built WebGL scene.
- 03
A separate phone layout
Why: A bottom pill navigation suits thumbs better than a shrunken desktop header.
Trade-off: Two layouts to maintain.
Links
The source code is private. I'm happy to walk you through the code and design in a call.