Flows, roles, states, edge cases, policy rules.
About Me
AI-collaborative product builder across idea, interface, system, and operation.
I turn rough ideas into product structure, then use AI-assisted building to move through design, frontend, backend, data, deployment, and operation as one connected workflow.
Interfaces, interaction, visual systems, accessibility.
Apps, web, APIs, data, AI workflows, admin tools.
Deployment, billing states, histories, reports, migration.
I started from engineering and design, then expanded into full end-to-end delivery: mobile apps, web services, APIs, admin tools, database-backed workflows, AI products, and production deployment.
I am also a severely visually impaired builder. That lived experience makes accessibility, dignity, and product desirability part of my design and engineering standards.
Platform Range
Websites, mobile apps, tablet tools, and the systems between them.
Websites & SaaS
Responsive service sites, dashboards, reports, landing systems, and admin surfaces.
Smartphone Apps
Flutter-style mobile flows, onboarding, creation screens, histories, settings, and paid states.
Tablet Operations
Store, staff, field, kiosk-like, and owner tools designed for wider touch surfaces.
Connected Systems
Auth, data models, reports, billing states, deployment, and admin controls behind the UI.
Working Strengths
The strength is not a tool list. It is turning product intent into a working system with AI as a serious collaborator.
Firebase Auth, Hosting, Cloud Functions, React, Flutter, Unity, SQL, and similar tools matter when the product needs them. They are supporting choices, not the main story.
AI Collaboration
AI-first planning, implementation, review, and iteration
I use AI as a daily development partner while keeping product intent, structure, taste, and final responsibility human.
Product Architecture
Flows, roles, states, data rules, permissions, and edge cases
The valuable work starts before code: turning a vague idea into a system that can be designed, built, tested, and operated.
Mobile Products
Flutter, iOS/Android thinking, WebView flows, app UX
Mobile work is framed around real app behavior: onboarding, creation, history, settings, paid states, and return visits.
Web Products
Responsive interfaces, SaaS dashboards, reports, service sites
React, JavaScript, HTML, CSS, and static builds are used when they help turn a service into a usable web surface.
Backend & Data
APIs, SQL, Firestore, generated results, histories, reports
Auth, storage, functions, and databases are treated as product infrastructure: useful because they support accounts, rules, data, and operations.
Operations
Deployment, admin tools, billing states, policy controls, migration
Shipping does not end at the UI. The product needs admin surfaces, logs, reports, recovery paths, and people who can operate it.
Design Judgment
Interaction design, accessibility, visual systems, product dignity
Screens, labels, states, hierarchy, and motion should make the system easier to understand and more respectful to use.
Past Range
Commerce, Firebase, React-style web, Unity experiments, legacy systems
Some tools are deep production experience and some are experiments. I separate the two instead of pretending every tool is the headline.
Product planning
I reduce vague ideas into flows, roles, data structures, edge cases, operating rules, and screens people can actually use.
Design and implementation
I care about how a product looks and feels, but I also build the frontend, backend, APIs, data rules, admin tools, and deployment path behind it.
Operational judgment
I pay attention to policy changes, payment states, duplicate requests, migration risk, logs, and the people who must operate the system after launch.
Delivery Model
The useful part is connecting the visible product to the hidden system.
Instead of showing more project images here, this section explains the working model: translate an idea into interfaces, APIs, data rules, admin controls, and deployment paths that can actually be operated.
Clarify the problem, target user, product promise, and scope.
Design screens, states, flows, copy, and interaction behavior.
Connect APIs, data models, permissions, AI logic, and admin rules.
Ship, monitor, adjust policy, manage billing states, and support growth.
Philosophy
The interface and the hidden system are one product.
Ideas need structure.
A good product begins when an idea becomes flows, states, permissions, data, and clear operating rules.
Design is product judgment.
Interface decisions should clarify behavior, reduce friction, and respect the person using the product.
Systems are part of the experience.
Data, APIs, admin tools, billing, reports, and deployment all shape whether a product can actually be trusted.
Experience
25+ years building web, app, data, and operational systems.
A career across production commerce, mobile apps, backoffice systems, legacy migration, AI services, and independent product launches.
Habit Labs · Development Team Lead
Leading product implementation across app, web, backend, and AI-assisted development workflows.
Plan B Commerce · Director
Worked on live commerce systems, app/API integration, admin operations, SQL Server-backed business logic, and service migration.
Urban Dictionary · Co-founder
Built and operated web services where product decisions, interface design, backend logic, and business operations had to stay connected.
Freelance Developer
Delivered websites, business systems, community services, and legacy improvements across varied stacks and client environments.
Full-stack product delivery
Planning, UI, frontend, backend, database, deployment, and operation handled as one product responsibility.
Production system judgment
Experience with payments, settlement, policy rules, admin workflows, migration risk, and data consistency.
Modern build workflow
Uses AI to move faster while keeping architecture, product intent, and final engineering judgment accountable.