Skip to content

NAVIGATION

LAB

EST. MMXXIV — RAJSHAHI / REMOTE

← ALL WORK
CASE STUDY — 05

Hootum

A collectibles marketplace with a digital vault behind every item.

Hootum connects a marketplace for collectibles with a secure wallet. Items can be verified, notarized, and held as digital tokens in a personal vault — two apps that have to feel like one trustworthy product.

ROLE
Frontend development · Product UI · Flow implementation
PRODUCT TYPE
Collectibles marketplace + digital wallet
MARKETPLACE
Next.js 14 · Tailwind CSS · Radix UI · React Hook Form + Zod · Framer Motion
WALLET
React · Redux Toolkit · MUI · Chart.js · Sentry

AT A GLANCE

2

Connected apps

Marketplace web app + wallet app

9

Marketplace sections

Categories, search, product, payments, profile, settings

15

Wallet components

Vault, passport, membership, transfers, history

7

Service modules

Auth, catalog, collectibles, notary, payments, vault, verification

01THE PRODUCT

Buying a collectible is only half the job. Proving you own it is the other half.

The marketplace handles discovery and purchase. The wallet handles what comes after: holding, protecting, and moving what you own.

A

Marketplace

  • Category browsing and search
  • Product detail pages
  • Checkout with payment confirmation
  • Profile with collections, carousels, and tabs
  • Account settings
B

Wallet

  • Vault for owned collectibles
  • Wallet passport and membership
  • Subscriptions and wallet store
  • Transaction history
  • Send reward points and transfer assets to contacts
02THE TRUST LAYER

Three systems that make ownership believable

Trust is not a badge on a card. In Hootum it is a set of real flows the interface has to make understandable.

VERIFY

Identity & collectible verification

  • Personal and address details
  • Document upload with preview
  • OTP verification
NOTARIZE

Notary requests & live sessions

  • Fee shown before the request
  • Notarization activity log
  • Clear success confirmation
TOKENIZE

Collectibles minted into the vault

  • Create or reconnect a wallet
  • Mint a collectible as a digital token
  • Transfer to contacts
03KEY FLOWS

From sign-up to a protected collectible

  1. 01

    Sign up

    Google OAuth or email login, confirmed with a one-time passcode.

  2. 02

    Onboard

    Personal details → address → document upload, sharing one step-form layout so progress always feels short.

  3. 03

    Secure the wallet

    A three-moment PIN flow: why it matters, create it, confirmation — instead of a buried settings field.

  4. 04

    Buy

    Browse or search → product detail → payment → success screen.

  5. 05

    Protect

    Request notarization with the fee shown up front, follow the log, then mint the item into the vault.

  6. 06

    Move

    Send reward points or transfer an asset to a saved contact from the wallet.

04DESIGN CONSIDERATIONS

Making high-stakes steps feel calm

01

Security as a guided moment

PIN creation is split into intro, input, and confirmation popups. Users understand why before being asked for something sensitive.

02

Costs before commitment

Notarization fees appear in their own step before a request is sent — no surprises after the user has already decided.

03

Steps, not a wall of fields

Verification is broken into personal, address, and document steps with a shared layout, so a long process reads as a short sequence.

05ENGINEERING

Two codebases, one product language

  1. 01  EXPERIENCE

    • Step-based trust flows

    Verification, PIN, and notarization split into short guided moments.

  2. 02  FRONTEND

    • Next.js 14 marketplace
    • React wallet app

    Tailwind + Radix on one side, Redux Toolkit + MUI on the other.

  3. 03  API LAYER

    • Shared API client
    • 7 domain service modules

    Auth, catalog, collectibles, notary, payments, vault, and verification.

  4. 04  INTEGRATIONS

    • Google OAuth
    • OTP verification

    Sign-in and one-time passcodes for identity checks.

  5. 05  DELIVERY

    • Docker
    • GitLab CI
    • Sentry

    Containerized builds, pipelines, and error monitoring.

ONE REQUEST, END TO END

  1. Owner requests notarization
  2. Fee shown up front
  3. Notary service module
  4. Shared API client
  5. Activity log updates
  6. Item minted into the vault
DESIGNED & BUILTCONFIGURED & INTEGRATED

MARKETPLACE APP

Next.js 14 (App Router)

Route groups separate landing and auth; category and product routes are dynamic.

UI SYSTEM

Tailwind · Radix UI · CVA

shadcn-style primitives, Embla and Swiper carousels, Framer Motion transitions, toast feedback.

FORMS

React Hook Form + Zod

Schema-validated forms for auth, onboarding, and payments.

WALLET APP

React · Redux Toolkit · MUI

Slice-based state for wallet and user data; Chart.js dashboards; PDF.js document preview.

DATA ACCESS

Service modules per domain

Auth, categories, collectibles, notary, payments, vault, and verification over a shared API client.

DELIVERY

Docker · GitLab CI · Sentry

Containerized builds, CI pipeline, and error monitoring on the wallet app.

NEXT CASE STUDY

Xinator Central →

Enterprise scheduling and operations

← All work