01CID ERP
Giving a long-running Swiss ERP a modern interface, without rewriting its engine.
- Lead dev
- Product development
- Design system
- Client
- Fair IT
- Role
- Lead front-end developer
- Year
- 2024 - Today
- Stack
- React · TypeScript · TanStack Query · Storybook · XML / XSD · Python (OpenERP)
The challenge
A legacy backend we could not rewrite: more than 200 OpenERP modules and nearly 4,000 view definitions, all described in XML on the server.
Every customer customises their screens, so we could not hand-code a fixed set of pages.
Very different users, from accountants entering data all day to managers and HR, working in dense forms and long tables.
My answer
A new React and TypeScript front-end on top of the existing backend: the business logic stays where it is, and the interface is rebuilt from scratch.
An XML rendering engine. The front-end reads the XML of each screen, validates it against a schema, simplifies it, then turns it into React components. Every existing view and every customer customisation works without writing a screen by hand.
The ERP’s dynamic rules rebuilt on the front-end: fields that update each other, or appear and become read-only depending on other values, so forms behave the way users expect.
A design system of 60+ components in Storybook, built with our designers, and keyboard-friendly tables built for heavy data entry.
