Omkar Sahu

I'm a front-end engineer based in Hyderabad, India, with more than 17 years of professional experience. I spent 12 years as a senior front-end developer, designing and building websites, and I have worked as a full-stack developer since 2022. I created oks-ui, a React component library with no runtime dependencies, and I write and maintain this site.

How my posts are written and checked

Why I built oks-ui

At the company I work for, I built the UI components for our product from scratch, with no third-party libraries.

A few days later I found that another developer had changed one of them to solve a problem of their own that day. It worked. But I could see where that leads: if everyone fixes things by editing the shared component, the product slowly turns into a mess where no two screens behave the same way.

That stayed with me, and I realised any team with shared components can drift like this. I wanted components that stay consistent across a whole product by design: when something needs to look or behave differently, there is a clear, supported way to do it, a prop or a theme variable, so nobody has to change the component itself.

oks-ui is my attempt at building that for anyone to use. It is free and MIT licensed, so a team can start from a consistent set of components instead of building and maintaining its own.

What it gives a new project

The point of all this is that a new project does not start from a blank page.

• Consistency from the first screen. Every screen uses the same components and the same design tokens, so buttons, forms and tables look and behave the same everywhere.
• Less to build and maintain. Dozens of components, plus complete templates and full-screen patterns, are ready to use, so a team can spend its time on its own product.
• One place to change the look. Colours, spacing, corner radius and dark mode come from CSS variables, so a rebrand is a change to a few values, not a search through components.
• Accessible by default. Components work with a keyboard, show visible focus and use sensible ARIA roles.
• Light on dependencies. No runtime dependencies beyond React and no theme provider, and you import only the components you use.

Find me elsewhere

• LinkedIn
• dev.to
• Medium
• Email