HiramBarsky

I design and develop software: SaaS products, web apps, mobile apps, and the internal tools most teams put off. Design and front-end build are the same job here, done by the same person.

That means product design, React and TypeScript on the front end, and the database and auth underneath it. What you get at the end is a working product, not a spec someone else has to interpret.

Yes, and there are five live right now you can open and use — Ring-Rival, Stips, HerbaLink, CatchBuddy and Fire Lion. Each one is mine end to end: design, front end, database, auth, deploy.

The honest limit is scale. I'm a good fit for a first version, a rebuild, or a team that needs design and front end moving together. I'm not a substitute for an engineering department.

AI makes the raw material cheap — screens, variations, working code. That moves the bottleneck from making things to judging them, and the judgement is the job.

A concrete example: on Ring-Rival it meant cutting time-to-first-punch from 22 seconds to 6, by deleting the splash screen, mode select, fighter select and tutorial. No model tells you which four things to delete.

Both, but the work looks different. With startups it's usually a first version: decide what the product is, design it, build it, get it in front of people.

With established companies it's more often an internal tool, a rebuild of something that outgrew its original design, or a design system that needs to hold up across teams. Most of my 15+ years has been the second kind, in regulated software.

Timeline depends entirely on scope, so I'd rather scope it with you than quote a number here. What's consistent is the shape: understand the problem, design it, build it in the open, and put something usable in front of you early rather than at the end.

Because I build what I design, there's no handoff round-trip. Decisions get tested in a real browser on a real phone instead of surviving a translation layer.

I build to WCAG 2.1 AA and treat it as a constraint from the start, not a pass at the end. That means keyboard paths, focus states, contrast and screen-reader semantics designed in rather than retrofitted.

Most of my career has been in banking, healthcare and pharma, where accessibility conformance and audit review are requirements, not aspirations. That's where the habit comes from.

Front end: React, TypeScript, Vite and Next.js, with Tailwind for styling.

Backend and infrastructure: Supabase and Postgres, Cloudflare Workers and D1, with deploys on Netlify or Vercel. Mobile work is React Native via Expo.

Design happens in Figma, and I use Claude and other models throughout for generation and review. The point of the stack is that one person can carry a product from design to production with it.

It depends on scope, so I quote per project rather than publishing a rate card. I'll take a call, understand what you're building, and send a proposal with the scope and price written down.

The call is free and there's no pitch deck. If I'm not the right fit for what you need, I'll say so on that call rather than after you've paid for it.