Product venture
12 / 12
Heartnote
A launched consumer fragrance subscription with discovery, recommendations, checkout, recurring payments, and account lifecycle.
- Role
- Frontend Engineer · 2021 — 2022
- Problem
- The frontend had to make a physical, sensory product understandable while also carrying a complex subscription lifecycle.
- Strategy
- Discovery, recommendation, selection, checkout, and account management were designed as one journey. After launch, the interface expanded around the practical states users needed to manage an ongoing subscription.
- Outcome
- Shipped and operated a real consumer product beyond Web3.
Archived product · 2021–2022
01
Problem definition
Why this problem had to be solved
Heartnote was a consumer fragrance subscription that helped people discover and receive a selected fragrance each month.
What users and the system were facing
Fragrance discovery is personal and difficult to translate into an online flow.
A subscription spans recommendation, product selection, checkout, recurring payment, delivery, account changes, pause, and cancellation.
Consumer trust depended on clarity beyond the happy path.
Frontend ownership
I implemented and maintained the customer-facing frontend across discovery, subscription, payment, account management, and post-launch iteration.
Responsive product and marketing experience
Catalog, search, detail, taste quiz, and recommendations
Subscription calendar, checkout, and recurring payments
Account, orders, pause, resume, cancel, coupon, and referral flows
02
Solution strategy
A system strategy carried into production
Discovery, recommendation, selection, checkout, and account management were designed as one journey. After launch, the interface expanded around the practical states users needed to manage an ongoing subscription.
System model
The customer journey moves from fragrance discovery and a taste quiz to monthly selection, checkout, recurring delivery, and self-service account changes.
Product evidence
Selected product surfaces
Historical product interfaces. Values shown are captured UI states, not current TVL, APY, or performance claims.
Implementation decisions
Turned a fragrance catalog into search, discovery, and preference flows.
Connected subscription selection with payment and recurring account state.
Built self-service lifecycle actions beyond initial checkout.
Integrated consumer analytics and local commerce services.
03
Outcome
What changed—and what I learned
Shipped and operated a real consumer product beyond Web3.
Delivered the customer experience across discovery, commerce, and subscription lifecycle.
Learned to validate regulatory and operational constraints alongside desirability and technical feasibility.
Learning
A technically complete customer journey can still depend on operational and sector-specific constraints outside the interface.
Today
I would validate regulation and fulfillment constraints earlier, define subscription state as a formal domain model, and instrument each lifecycle transition without relying on unverified growth claims.
Built with
Public links
Work together