Skip to content
YMP
← All work

Operational software · desktop, mobile and API

Prototype

Senzovia

Inventory software built from a real operational problem: a Romanian PVC factory counting roughly 500 product varieties by hand and typing the results into Excel. The prototype models stock as a ledger of movements and supports counting sessions, customers and shipments, Excel import and export, and a graph of how categories, products and customers connect, in three interface languages. A desktop client, a mobile client and a Cloudflare Workers API share one core package. Computer-vision counting is the planned next input; so far it exists only as an isolated experiment.

  • React
  • TypeScript
  • Tauri
  • React Native
  • Cloudflare Workers
  • Cloudflare D1
  • Hono
  • Zod
Senzovia stock screen: summary figures for SKUs, units on hand and out-of-stock items above a searchable table of PVC profile products with category and quantity.
Stock — sample data
Senzovia graph screen: categories, products and customers drawn as connected nodes, linked by shipments and assignments.
Graph of categories, products and customers — sample data

My part

Sole developer — from the product and domain documents to the desktop and mobile clients, the API and its data model, and a shared core package; authentication with MFA and tenant isolation.

Scope

  • Focused on dashboard design, data visualisation and application architecture.
  • The screenshots show the desktop client’s interface running in a browser on invented sample data, with no backend; the on-screen banner says so. They are not captures of the native app window.
  • The mobile client and the API are part of the prototype but not of the screenshots.
Source on request

09 — Work with me

Have somethingyou needbuilt?

A new product, an internal tool, or the system behind an interface that already exists. If the problem isn’t pinned down yet, I can help shape the product and the architecture before anything is written. Tell me what it is, who it is for and when you need it. I answer with what I would build, in what order, and what I would decide first — and I say so when what I learn along the way contradicts the plan, including mine.