Application Hub — Domain model and MVP scope
A personal application hub concept that unifies public profile publishing, CV PDF generation, portfolio management, and private job-application tracking in a single-user admin product.
const project = {
title: "Application Hub — Domain model and MVP scope",
year: 2026,
tech: ["Domain Modeling", "Product Design", "MVP Scoping", "Information Architecture", "Typescript", "React Router - Framework mode", "PostgreSQL", "Supabase"],
};Problem
The product mixed public profile presentation, private admin workflows, and AI-assisted job application drafting. The challenge was defining a clear domain model and explicit MVP scope to align product decisions with implementation, while avoiding common pitfalls like leaky abstractions, ambiguous terminology, and feature creep.
Solution
I produced a domain language and relationship map that defined canonical entities (Profile, Draft Profile, Published Profile, CV PDF, Job Application, Application Draft, Sent Application Email, Portfolio Item, Media Asset, and more), documented explicit avoid-terms, and clarified public/private behavior. I also captured flagged ambiguities and resolved them into concrete MVP rules to align product decisions with implementation.
Outcomes
- Established one canonical Profile as source of truth for both Public Website and CV PDF
- Defined clear publish workflow: draft content stays private until explicit publish
- Separated rich Portfolio Items from compact CV-oriented profile content
- Specified flexible Application Status board states without strict transition enforcement
- Scoped MVP around a single private admin user and excluded multi-tenant complexity
- Documented privacy boundaries for job applications, drafts, notes, and temporary AI output
- JIRA like board with flexible status columns and drag-and-drop without strict workflow rules to allow users to define their own process while still providing structure and visibility into application stages