Marketplace domains
Trades, collaborations, challenges, profiles, messages, reviews, and evidence have explicit service and data boundaries.
← Work / Active files
[ CASE FILE / TRADEYA ]
ActiveTradeYa
A live skill-trade marketplace being hardened from a broad web product into a maintainable foundation for mobile expansion.
TradeYaA live skill-trade marketplace being hardened from a broad web product into a maintainable foundation for mobile expansion.Live / Production
01
The messy workflow
Creative collaboration breaks when trust, scope, and exchange live in separate places.
People can offer useful skills and still struggle to find a fair counterpart, define the exchange, communicate through delivery, and preserve evidence of the result.
TradeYa puts discovery, trade proposals, collaboration, messaging, reviews, and community participation into one product while keeping the exchange centered on skills rather than cash.
02
Ownership boundary
A first-party product spanning interface, marketplace state, and production operations.
I direct and implement the product, including the React application, Firebase data paths, marketplace workflows, design system, tests, security checks, and deployment operations.
The current work is not a claim that every feature is finished. The facelift is paired with feature verification and maintainability work before mobile expansion.
Declared ownership
I own the product direction, interface, application architecture, Firebase integration, quality systems, deployment workflow, and current maintainability work. Firebase, React, and the other platform dependencies remain third-party technology.
03
System map
How the work moves.
- Input
Member identity
Authentication, profiles, skills, reputation, and availability establish who can participate.
- Output
Marketplace discovery
Trades, collaborations, challenges, builders, and community activity expose possible matches.
- State
Proposal state
Scope, participants, status, and evidence move through explicit marketplace records.
- Decision
Trust controls
Validation, Firestore rules, reviews, and moderation boundaries constrain unsafe transitions.
- State
Collaboration loop
Messaging, notifications, progress, and delivery evidence support the work after a match.
- Failure path
Verification and repair
Tests, production checks, and the current hardening pass return broken or inconsistent flows to implementation.
04
Hard calls
Decisions that changed the system.
05
Build record
Selected implementation record.
React product system
TypeScript, Vite, React Query, shared UI primitives, and feature modules form the client application.
Firebase production layer
Authentication, Firestore, Cloud Functions, storage, indexes, security rules, and migration tooling support production state.
Layered quality gates
Type checking, lint, unit tests, browser tests, security checks, asset budgets, and builds cover different failure classes.
06
Verification ledger
Claims with their edges left on.
HS-7VERIFIED RECORD
Live
Production
The marketplace is operating on its public custom domain while the current facelift and reliability pass continue.
SourcePublic production route and repository deployment configuration
HS-7VERIFIED RECORD
Trades + collaboration
Marketplace scope
The product covers skill trades, collaborations, challenges, profiles, messaging, reviews, and community activity.
SourceRepository AGENTS.md and feature-domain source structure
HS-7VERIFIED RECORD
Unit + E2E
Quality gates
The repository defines TypeScript, lint, Jest, Playwright, Firebase security, asset-bloat, and production build checks.
SourceRepository package.json scripts and AGENTS.md verification contract
LimitThe active hardening phase means individual features still require current verification before release claims.
07
Failure + iteration
What failed stays in the record.
monitoring
Feature breadth created maintenance debt
- Observed
- A large marketplace surface accumulated duplicate scripts, dependency age, and inconsistent implementation paths.
- Response
- The active phase pairs the facelift with explicit feature checks, shared primitives, dependency review, and maintainability gates.
monitoring
Visual polish could outrun functional proof
- Observed
- A facelift can make an unfinished flow look complete before its data and interaction paths are verified.
- Response
- Treat browser verification and feature behavior as release gates instead of accepting appearance alone.
open
Mobile parity was easy to describe too early
- Observed
- The roadmap names iOS and Android outcomes while the web foundation still requires stabilization.
- Response
- Label mobile as preparation and sequence it after web behavior and maintainability are verified.
08
Current status
Live, under active hardening, and preparing for mobile expansion.
TradeYa is live while the current phase refreshes the interface, checks feature behavior, and reduces maintenance risk. iOS development is the next platform direction, not a shipped capability.
Open to the right work
A useful system starts with the actual problem.
Full-time product, automation, and technical-operations roles are the priority. Select workflow and creative-technology projects are open.