Across mobile and backend systems, I built and iterated core product functionality through my 1099 software solutions work with Archlife Industries.

• Built Plaid connections, trending investors, and suggested stocks.
• Built social features: direct chat, profiles, posts, likes, emojis, and threaded comments.
• Wrote data-visualization logic for comparing stock and crypto performance.
• Transitioned the React Native codebase from JavaScript to TypeScript.

Archlife also served as a public lab: a place for product ideas weird enough to be memorable and technical enough to be real. The public repos make the work inspectable instead of merely described.

• Built an OSS Expo + MetaMask mobile app for a hackathon.
• Shipped a personal life intelligence layer as open source.
• Built a financial categorizer and aggregator dashboard for preparing and filing taxes using agents.
• Published public repos that make the work inspectable instead of only described.

Some Archlife projects demanded more than a feature that worked: privacy, auditability, and controlled operations had to be present in the engineering itself. I treat HIPAA and SOC 2 as system-design requirements, not compliance theater—minimum-necessary access, traceable change paths, and operational guardrails that can hold up under review.

• Mapped product decisions to least-privilege access boundaries, controlled production permissions, and attributable operational actions.
• Built for auditability with clearer event visibility, traceable release paths, and investigation-friendly system behavior.
• Treated sensitive-data handling as an architecture concern: tighter trust boundaries, reduced unnecessary exposure paths, and stricter interface discipline.
• Hardened release workflows so compliance-sensitive changes had repeatable review and rollback expectations before production.

Finequities is the clearest production example: SOC 2 readiness became concrete work across mobile, backend, and release operations. The same principle carries into healthcare—minimum-necessary data flow, strict access boundaries, and audit trails from day one—so protected data can stay safe without destroying usability.

• Finequities: tightened access boundaries, reduced security ambiguity in fast-changing product areas, and improved incident-readiness and evidence quality.
• Finequities: drove TypeScript migration and architecture cleanup that made compliance-sensitive logic easier to reason about.
• Healthcare-oriented systems: design for ePHI boundary discipline, role-scoped access, immutable audit trails, and compliance-aware release gates.
• Across both: translate policy expectations into real software behavior instead of leaving them as documentation-only promises.