← Selected work
2024·Sequence · Archived

Marketplace Boilerplate

White-label marketplace starter powered by Sequence

The Marketplace Boilerplate turned Sequence's marketplace stack into a working application surface that integrators could clone, configure, and customize instead of starting from an empty Next.js project.

MarketplaceCollection

What it is

This repository was a white-label marketplace starter for Sequence integrators. Teams configured a Sequence project and access key, then used the application as the starting point for a custom marketplace experience.

The pinned repository is now archived and points developers to a newer Sequence marketplace boilerplate. I keep this version pinned because it represents the generation of the product I worked on directly.

My work

I worked across marketplace product surfaces and SDK integration: filters and inventory, listing and offer flows, buy and sell interactions, transaction-state refactors, cancellation flows, chain-specific behavior, and the supporting test and frontend infrastructure.

Why the boilerplate mattered

The useful output of an SDK is not only its exported API. A working integration gives teams a reference for state management, wallet interaction, transaction flows, environment configuration, and the edge cases that appear when those pieces meet in a real product.

Architecture

01

Sequence Builder project configuration

02

Marketplace environment and access keys

03

Next.js application shell

04

Sequence Marketplace SDK integration

05

Listings, offers, inventory, and transaction surfaces

06

Customizable white-label product experience

Engineering notes

01

Ship an executable reference

A working product surface makes SDK integration behavior concrete and gives integrators a place to start modifying real flows rather than reconstructing them from isolated snippets.

02

Keep product flows close to SDK development

The boilerplate exercises marketplace behavior through the same kinds of listing, offer, inventory, and transaction interactions that downstream integrators need to implement.

← Back to all work