From idea to production, cleanly.

Full-stack in Next.js and TypeScript. I focus on clarity, performance, and systems that hold up over time.

Calm design. Solid systems.

From zero to production.

Next.jsTypeScriptSupabaseOpenAIn8n

Quietly steady

Work

A focused selection — enough to show how I think and ship.

Uriach You — B2B platform for pharmacies

B2B platform for pharmacies: training, updates, analytics.

Context: A single place to educate, launch, and support pharmacy partners.

Constraints: B2B clarity, fast content updates, reliable delivery.

Role: End-to-end ownership: build, ship, iterate.

What I did

Next.js + TypeScript + Sanity foundation, deployed on Vercel.
Training areas for pharmacies and healthcare audiences.
Analytics and internal tooling to support adoption.

Next.jsTypeScriptSanityVercel

Demo

Yuma — ISDIN UI Kit & Design System

Design system and component library focused on consistency and accessibility.

Context: Shared UI base across multiple ISDIN products.

Constraints: Pixel-accurate UI, a11y, performance, smooth DX.

Role: UI components, architecture, and integration support.

What I did

Reusable components built with Styled Components.
Accessibility-first patterns and strict visual fidelity.
Support work for real adoption in production.

ReactStyled ComponentsDesign SystemAccessibility

Demo

Vinci — Web3 music funding with ERC-20 tokens

Web3 funding for artists with ERC-20 tokens and perks.

Context: Direct fan-to-artist funding with on-chain ownership.

Constraints: Low-friction UX, wallet auth, reliable contract reads.

Role: Frontend, Web3 auth, contract integration.

What I did

Wallet-based authentication and user flows.
Ethereum reads to unlock benefits by ownership.
Clean purchase and discovery experience.

ReactTypeScriptEthereumWeb3 Auth

Demo

Selfcare — Telecom customer management platform

B2B self-service portal for lines, subscriptions, and usage insights.

Context: Customers needed control without dependence on support.

Constraints: Dense data, predictable UX, maintainable UI at scale.

Role: Frontend delivery, shared libraries, platform stability.

What I did

Core flows for managing lines and subscriptions.
Improved data views with reusable UI patterns.
Contributed to shared libraries to reduce regressions.

ReactTypeScriptB2B PortalUI Libraries

Demo

Stack

A modular toolbox — chosen for speed, clarity, and long-term maintainability.

Next.js (App Router)

Server/client boundaries with predictable patterns
ISR and on-demand revalidation when content matters
Performance and accessibility by default

Next.jsApp RouterRSCISR

Vercel

Serverless deployments with previews by default
Secure by design: isolated envs, clean releases, easy rollbacks

VercelServerlessPreviewSecurity

shadcn/ui

Composable UI primitives with real control
Fast builds, consistent visual language

shadcn/uiRadixTailwindUI System

Sanity CMS

Structured content modeling
Editorial flow + webhook revalidation

SanityWebhooksContent

OpenAI (AI-assisted flows)

AI as an assistant inside product flows
Chunking, summarization, and structured outputs
Honest UX: assistive, not manipulative

OpenAIStructured outputUX

Supabase + Postgres

Relational schemas, constraints, ownership rules
Auth/storage patterns that ship fast
Pragmatic security boundaries

PostgresSupabaseRLS

Typesense

Fast, typo-tolerant search with instant results
Simple indexing and predictable relevance tuning

TypesenseSearchIndexingRelevance

n8n (Automation)

Automations and glue code without brittle scripts
Event-driven workflows

n8nWebhooksOps

Next.js (App Router)

Server/client boundaries with predictable patterns
ISR and on-demand revalidation when content matters
Performance and accessibility by default

Next.jsApp RouterRSCISR

Vercel

Serverless deployments with previews by default
Secure by design: isolated envs, clean releases, easy rollbacks

VercelServerlessPreviewSecurity

shadcn/ui

Composable UI primitives with real control
Fast builds, consistent visual language

shadcn/uiRadixTailwindUI System

Sanity CMS

Structured content modeling
Editorial flow + webhook revalidation

SanityWebhooksContent

OpenAI (AI-assisted flows)

AI as an assistant inside product flows
Chunking, summarization, and structured outputs
Honest UX: assistive, not manipulative

OpenAIStructured outputUX

Supabase + Postgres

Relational schemas, constraints, ownership rules
Auth/storage patterns that ship fast
Pragmatic security boundaries

PostgresSupabaseRLS

Typesense

Fast, typo-tolerant search with instant results
Simple indexing and predictable relevance tuning

TypesenseSearchIndexingRelevance

n8n (Automation)

Automations and glue code without brittle scripts
Event-driven workflows

n8nWebhooksOps

Systems

I think in constraints and trade-offs: maintainability, reliability, cost.

Architecture

Prefer composable modules over feature monoliths.
Make routing and content boundaries explicit.
Optimize for change: clear dependencies, minimal coupling.

Data

Relational first: Postgres schemas that tell the truth.
Indexes, constraints, ownership, and auditability.
Store what you can query; serialize what you must.

Reliability

Idempotent jobs, retries, and observable pipelines.
Separate coordination from compute.
Fail clearly; recover fast.

DX & Security

Typed interfaces, predictable environments, clean logs.
Server-side session integrity and conservative permissions.
Pragmatic threat modeling, not paranoia.

Writing

Notes on building systems, shipping work, and keeping complexity in check.

ISR with Sanity webhooks in Next.js

A practical pattern to revalidate pages while keeping the editorial flow intact.

Postgres schemas that stay readable

Constraints and ownership rules as part of the product — not an afterthought.

Automation pipelines: coordination vs compute

Scale workloads by separating cheap orchestration from heavy compute workers.

About

Craft over drama.

I'm a full-stack developer who values clarity over noise. I build systems that stay robust under change: clean boundaries, honest data models, and interfaces that don’t fight the user. I ship, then iterate with discipline.

Less friction, more flow.
Design is how it feels to use.
Build for iteration.

Contact

If you want to talk product, architecture, or execution with care, email me.

roberto@rrios.dev