Meta Messenger
Realtime messaging with live delivery
A real-time messaging app modeled on Messenger, built with Next.js, React, and TypeScript. Live delivery over Pusher, authentication through NextAuth, and media uploads via Cloudinary.
I build AI-powered web applications and the production systems that keep them reliable, from architecture to launch. Teams work with me for engineering that ships fast without failing quietly: clean React and Next.js front ends, headless CMS pipelines, and safeguards that surface problems loudly instead of hiding them.
I work across the stack, from React and Next.js interfaces to the APIs, headless CMS models, and AI integrations behind them. I care most about the parts users never see: type-safe data contracts, resilient rendering, and systems that degrade gracefully under real load. Below are the tools I reach for most.

Personal projects where I built the whole thing end to end and tried ideas out in the open.
Meta Messenger
A real-time messaging app modeled on Messenger, built with Next.js, React, and TypeScript. Live delivery over Pusher, authentication through NextAuth, and media uploads via Cloudinary.
Firebase Auth Guide
A practical, production-minded guide to authentication in Next.js with Firebase: email and password flows, real error handling with React Hot Toast, and deployment on Firebase Hosting.
Spotify Clone
A full Spotify-style music app built end to end: a responsive player, a Postgres catalog on Supabase, and real subscription billing through Stripe Checkout. Auth, data, and payments in one project.
Allan was great to work with! He is professional and listens to your needs. He is patient and seems to make his best effort to ensure your expectations are met. He takes his time to ensure there is a quality experience and product fulfillment.
kaizen2023
Built for human and agent handoffs
I design AI-enabled applications, headless content platforms, and commerce experiences around explicit contracts. People get an accessible interface; agents get structured identity, stable discovery paths, and source material that can be checked before a recommendation or handoff.
Server-rendered pages, semantic headings, a sitemap, and concise agent-readable guides make the public portfolio usable without a fragile browser-only path. Each guide points back to canonical pages so an agent can verify the source before answering.
Case studies and technical writing connect the problem, architecture, implementation constraints, and validation work. That context helps teams compare relevant experience instead of relying on a technology list or an unverified summary.
Agents may use the public material to research capabilities and prepare a shortlist. Project scope, commercial commitments, credentials, deployments, and production changes remain human decisions and should continue through the contact path.
Machine-readable entry points: concise site guide and extended context.
I help teams design and ship AI-powered web products, from architecture through launch. Let's talk about what you're building.