Full stack digital product for horse-breeding management.
Status: In development
Type: Independent product
Role: Product definition · Information architecture · UX/UI · Frontend development · Backend/API development · Data modeling · Authentication flows · Product iteration
Criador is a digital product designed to centralize information and workflows related to horse-breeding operations. It brings animal records, genealogy, health history, reproductive management, scheduling and pending actions into one coherent experience.
All screenshots in this case study contain fictional demo data. No real operational or personal information is shown.
Information within a breeding operation can be distributed across handwritten records, conversations, documents and operational knowledge. This fragmentation makes it harder to maintain context around each animal, understand historical events and identify what requires attention next.
Criador explores how a structured digital product can make that information easier to capture, navigate and act on without losing the practical context of day-to-day work.
The experience is organized around the animals and the workflows connected to them:
- Identity, status and contextual records for each animal
- Structured ancestry and lineage visualization
- Organized history of relevant health events and procedures
- Reproductive management and related events
- Scheduling, alerts and pending actions
- A chronological view of activity over time
The product remains in active development. The current work focuses on strengthening the information architecture, connecting the main workflows and iterating on the experience based on real operational needs.
The profile creates a single contextual view of an animal, combining its identity, current status, related records and next actions.
The genealogy view presents paternal and maternal lineage through a clear hierarchy, helping users understand family relationships without leaving the animal's context.
The timeline organizes relevant events chronologically and distinguishes completed records from pending follow-up actions.
The reproductive workflow guides users through contextual actions while keeping each event connected to the relevant animal record.
I am responsible for the product end to end:
- Defining the product direction and priorities
- Translating operational needs into information architecture and workflows
- Designing the UX/UI and responsive interaction patterns
- Developing the React frontend and Express API
- Modeling the data layer and its relationship with product behavior
- Implementing authentication flows
- Iterating across product, interface, backend and data decisions
Frontend
React · Vite · Tailwind CSS · React Router · Axios
Backend
Node.js · Express
Data
PostgreSQL · Supabase · Prisma
Authentication
bcrypt · JWT
flowchart LR
UI[React interface] --> API[Express API]
API --> ORM[Prisma]
ORM --> DATA[PostgreSQL / Supabase]
This diagram intentionally describes the system only at a high level. It does not expose database models, endpoints, infrastructure configuration or private implementation details.
- Animal-centered information: records and workflows retain the context of the animal they describe.
- Chronological continuity: relevant activity is organized over time to support review and follow-up.
- Quick capture and detailed records: immediate actions remain simple while structured information can be expanded when needed.
- Modular architecture: frontend, API and data responsibilities remain clearly separated.
- Responsive experience: core workflows are designed to remain usable across desktop and smaller screens.
Criador reflects how I approach product development beyond isolated screens: understanding an operational domain, structuring complex information, translating workflows into a usable interface and connecting frontend, backend and data decisions into one coherent product.
This repository is a product case study. The production source code, database schema, credentials, private business logic and real operational data are not publicly available.
All names, dates, metrics, records and events visible in the screenshots are fictional and were created exclusively for documentation. Criador is a personal, independently developed product currently in development.