Satıyon mu? - Buy, Sell, Discover, Connect.
Marketplace platform built with listings, media, categories, search, favorites, messaging and Q&A modules. Product, backend architecture and user flow run as one.
Marketplace platform built with listings, media, categories, search, favorites, messaging and Q&A modules. Product, backend architecture and user flow run as one.
Satıyon mu? is a marketplace platform that covers listing creation, category management, media upload, search and filtering, favorites, messaging and listing Q&A flows. The product is built on a scalable monorepo with web and mobile in scope. It is still in active development.
A marketplace is not just a listing screen. Listing ownership, media handling, favorites behavior, messaging, Q&A, category structure, removed-listing behavior and user blocking all have to be solved well. If those are loose, the product falls apart fast. That is why I took product decisions and technical architecture together from the start.
I built the product on a modular marketplace spine. Auth, user management, listing creation, listing update, media upload, category structure, search, filtering, favorites, favorite collections, direct messaging and Listing Q&A are the core modules.
On the Listing Q&A side I wrote the business rules out. Only signed-in users can ask. Only the listing owner can answer. Q&A is public. A question publishes directly. The owner can hide a question. The asker can delete their own. The owner can edit the answer, and the edit timestamp shows in the UI. When a listing goes inactive, existing Q&A stays readable but new questions are closed.
On the technical side I worked on a monorepo running Next.js, Expo, NestJS, PostgreSQL, Redis, Prisma and Docker Compose. Migration, validation, backend endpoints, repo root, CI/CD and GitHub Actions logic are part of project discipline.
Satıyon mu? moved past being a listing site idea. It became a technical product architecture covering real marketplace modules: auth, listings, media, categories, favorites, messaging and Q&A. Product decisions were defined alongside the edge cases.
Product scope, module prioritization, user flows, backend architecture, data model, business rules, edge-case decisions, technical development direction, and setting up the marketplace product logic from front to back.