Reduced-motion / static banner
Profile · Work · Capabilities · Workflow · Evidence · Credentials · Connect
I’m a Toronto-based Product Designer focused on AI-enabled products, complex workflows, and implementation systems.
I turn ambiguous product problems into structured workflows, interaction states, accessible interfaces, working prototypes, and implementation-ready decisions. My strongest work sits where product design meets real system constraints: permissions, trust, state, design systems, mobile and web behavior, AI-assisted workflows, and design-to-code collaboration.
Implementation supports the product-design work. I use Figma, React Native, SwiftUI, React, Firebase, GitHub, Claude, and Codex to test decisions beyond static screens without repositioning the work as general software engineering.
Selected product work: Shiroe for human-controlled AI continuity and evidence; PerFin OS for collaborative mobile fintech and design-system work; For Rent for multi-role rental workflows in SwiftUI; and StreamNexus for role-based web workflows and release discipline.
I design and build systems that connect people to outcomes.
The profile is intentionally scan-first. Each project stays concise here, with deeper implementation and verification evidence in the repository.
01 · Shiroe — AI product design, continuity, trust, approvals, and failure recovery
Product statement: A local-first AI project memory and control runtime that keeps decisions, evidence, privacy rules, approvals, and handoffs inspectable across AI-assisted work.
My role: Independent product direction, workflow and interaction modeling, implementation, verification, and public evidence discipline.
Product focus: cross-session continuity, human control, contradiction handling, privacy, confidence/evidence boundaries, supervised automation, and failure recovery.
Current boundary: Shiroe is alpha software. Public claims stay bounded to current repository evidence; no external benchmark superiority claim is made.
02 · PerFin OS — mobile fintech, collaborative product design, and design-system implementation
Product statement: A collaborative React Native personal-finance product spanning activity, reports, insights, planning, and confirmed actions.
Team: Yash Kanadhia, Alexis Gorospe, and Sarmad Tariq. This profile does not imply solo ownership.
My contribution: Authentication and session ownership, finance-state separation, shared visual-token use, Firebase boundary cleanup, and reviewable pull-request delivery.
Product focus: financial workflow clarity, guest and authenticated states, semantic design systems, accessibility, implementation constraints, and responsible team attribution.
Current boundary: Public presentation remains a team-project contribution surface. Store release, adoption, behavior-change outcomes, and sole ownership are not claimed here.
Development branch · Session boundary PR #69 · Theme-token PR #68
03 · For Rent — multi-role product workflows, interaction states, and SwiftUI
Product statement: A Canadian rental-marketplace prototype supporting guest, renter, and landlord journeys across discovery, conversations, viewings, decisions, offers, and qualification states.
My role: Product design and SwiftUI implementation across role-aware journeys, protected actions, authentication return paths, accessibility behavior, state coverage, and deterministic demo support.
Product focus: mutual-decision workflows, information architecture, permissions, interaction states, accessibility, and implementation-aware UX.
Current boundary: Portfolio prototype. No App Store release, production marketplace, real payments, or real-user adoption is claimed.
04 · StreamNexus — product pivot, role-based web workflows, and release discipline
Product statement: A full-stack portfolio prototype exploring customer and administrator workflows around streaming-rental discovery, catalog management, authentication, authorization, and rental states.
My role: Product framing, workflow design, full-stack implementation, testing, security review, and release-boundary documentation.
Product focus: role and permission states, administrator UX, system boundaries, failure states, authentication, and implementation evidence.
Current boundary: Portfolio prototype, not a hosted production streaming service. Real users, real payments, and production adoption are not claimed.
Product framing · workflow architecture · information architecture · interaction design · prototyping · design systems · accessibility · state completeness
Human-AI interaction · human approval · trust and uncertainty · context and continuity · correction and recovery · privacy boundaries · evaluation-aware UX
Figma · React Native · SwiftUI · React · Firebase · Node.js · GitHub · testing · CI/CD · implementation verification
Implementation is supporting evidence for product decisions, not a claim of senior software-engineering positioning.
Ambiguity → Workflow → Interaction → Prototype → Build → Verification
- Find the unknown. Clarify users, outcomes, constraints, evidence gaps, ownership, and the decision that actually needs to be made.
- Map the workflow. Model actors, states, permissions, data relationships, failure conditions, and handoffs.
- Design the interaction. Establish hierarchy, behavior, content, accessibility, and edge states.
- Prototype the decision. Use realistic flows and working prototypes to expose assumptions static screens can hide.
- Build enough to test. Carry the interaction model into implementation where technical constraints matter.
- Verify before claiming. Review behavior, accessibility, privacy, security, links, tests, ownership, and limitations.
Evidence before claims. Metrics and outcomes stay out unless their source and method can be reproduced.
Ownership stays explicit. Independent work, team projects, and personal contributions are separated rather than flattened into “built.”
Prototypes stay prototypes. A working demo is not described as a production system, launch, adoption signal, or customer outcome without evidence.
AI assistance stays attributable. AI can support research, exploration, implementation, review, testing, and documentation. Product direction, acceptance, privacy, security, evidence quality, and public claims remain human decisions.
Accessibility is product quality. It belongs in content, states, interaction, motion, validation, and testing, including a static alternative for this profile’s motion banner.
Anthropic
- AI Fluency: Framework & Foundations
- Claude Code in Action
- Introduction to Claude Cowork
- Claude Code 101
SCRUMstudy
- Scrum Fundamentals Certified
Additional completed credentials are listed on LinkedIn.
I’m interested in Product Designer and AI Product Designer work where complex workflows, interaction quality, technical constraints, trust, and implementation need to stay coherent from concept through verification.
Toronto, Ontario, Canada · Open to Canada-relevant Product Design opportunities.