Frontend development in Pune
A front end for a factory is read in conditions office software never meets. It hangs on a screen at the end of a line, is glanced at from three metres away, is tapped by someone wearing gloves on a tablet in a noisy bay, and must still make sense at the end of a long shift. Pune's industrial software companies often build their first dashboards like office web apps, with small text and dense charts, and then wonder why supervisors go back to the whiteboard.
We design and build React and Next.js interfaces for the floor. Large, high-contrast status views that read at a distance, touch targets sized for gloves, colour never used as the only signal, screens that recover by themselves after the plant Wi-Fi drops, and a separate, denser view for the engineers in the office. We test on the actual screens and tablets your customers install, in the lighting they work under.
Pune runs two economies inside one metropolitan area. It is one of India's most important automobile and manufacturing hubs, with plants in Chakan, Pimpri-Chinchwad and Talegaon; Chakan alone hosts vehicle plants for Mercedes-Benz, Volkswagen, Bajaj Auto, Mahindra and Jaguar Land Rover, surrounded by hundreds of component suppliers. It is also one of the country's largest IT hubs, spread across Hinjewadi, Kharadi, Baner and Viman Nagar. And it makes vaccines: the Serum Institute of India, the world's largest vaccine manufacturer, is here too.
The most interesting software problems sit where those economies meet. Carmakers expect their suppliers to exchange schedules, shipping notices, drawings and quality documents electronically, and to keep up when the format changes. Plants want to know why a line stopped, which machine keeps failing and what the real output was per shift, but the data sits in machine controllers, a manufacturing execution system, an ERP and a supervisor's register, none of which agree. Industrial software startups, often founded by engineers who know those plants from the inside, are building products to fix exactly that, and selling them in India and abroad.
Our place is the software above the machines, working alongside your automation partner. We build the integrations that read what your machines and systems already expose, the data pipelines and dashboards that turn it into one picture, the supplier portals, the mobile apps for technicians and inspectors, and the SaaS products that package all of it. Pune also has a deep bench of IT services and engineering services firms, and a firm like ours can take a specialist piece of their larger programme, delivered under their name.
We are in Bengaluru and share your time zone, so the working day is the same on both sides and a problem raised in the morning gets a response that morning. Most of the work runs through your repository and a shared chat channel, and you talk directly to the engineer who writes the code. What we learn about your process, from calls, documents and photos of the floor, is written down as we go, so everyone works from the same picture.
We are the right fit for a defined build, an integration with an end date, or a product that needs to reach its first pilot plant before your own team is hired. Start with a fixed-price two-week piece and judge us on what ships. Pune's IT services and engineering firms can also bring us in white-label, under their name.
Four ways this arrives.
We measure on real devices and real traffic first, not a lab score on a fast laptop. The fix is usually less JavaScript: a smaller bundle, images sized for the screen, and third-party scripts that stop blocking the first render.
A procurement checklist, a customer complaint, or a letter from a lawyer. We fix the causes rather than the line items: real buttons, labelled forms, focus that lands somewhere sensible, and automated checks in CI so it stays fixed.
Global state that everything reads, no types, and three versions of the same modal. We add TypeScript file by file, put tests on the flows that make money, and move shared pieces into one component library as screens are touched.
Usually for search visibility or first-load speed. We move it route by route behind the same URLs, so the old app keeps serving while the new one takes over, and nobody has to sign off a risky weekend cut-over.
A Next.js web app with five operational dashboards and Tableau reports rendered in place, without a second login.
Read the write-up →Asked by Pune teams.
How do you work with teams in Pune?+
We are in Bengaluru and share your time zone, so calls, reviews and releases fit inside your normal working day. We work in your tools, Slack, GitHub and Linear or whatever your team already uses, and you talk directly to the engineer writing the code. Photos, short videos and a walk-through call from the floor go a long way, and everything we learn is written into your repository as runbooks and architecture notes.
Can you connect to our machines and plant systems?+
Yes, through the data they already expose. We integrate with what your manufacturing execution system, historian, SCADA or machine gateways publish, whether that is a database, an API, a message broker or exported files, and build the pipelines, dashboards and apps on top. We work alongside your automation partner, who looks after the controllers, and help you specify any new data points worth adding to the line.
How does your rate compare to hiring in Pune?+
PayScale puts a mid-career software engineer in Pune at about ₹14 lakh a year. Our published rate is $35 an hour, with a $5,000 minimum. That buys a senior engineer who writes the code, works in your Slack, GitHub and Linear, and starts within days, with no recruiting round, notice period or employment overhead. Begin with a fixed-price two-week piece at $2,800 and judge us on what ships.
Can you work white-label for our IT services firm?+
Yes. Work ships under your name, in your client's repositories and through your delivery process, and we sign an NDA before specifics. We stay behind your team unless you want us in the room. It works best for a well-defined specialist piece inside a larger programme, such as a data pipeline, a mobile app or an infrastructure migration, and the code belongs to your client from the first commit.
Do we need to move to Next.js?+
Not always. If the app sits behind a login and nobody finds it through search, a well-built React single-page app on Vite is simpler to host and easier to reason about. Next.js earns its keep when first load and search visibility matter, or when you want rendering close to the data. We will tell you which case you are before anyone rewrites a route.
Can you work from our Figma files?+
Yes, and we will ask questions about them. Designs rarely show the loading state, the empty state, the error, or what happens when a name is twice as long as the mock-up assumed. We raise those early and propose something, rather than inventing it quietly in code and leaving your designer to find out in review.
Will you build us a design system?+
We will build the one your product needs, which is usually smaller than people expect: design tokens, the components you actually use, and Storybook to show them. We extract it from the screens you already have rather than designing it in isolation, because a component library nobody migrates to is just a second way of doing things.
How do you handle accessibility?+
We build to WCAG 2.2 AA by default, test with a keyboard and a screen reader, and run automated checks in CI so regressions are caught before they ship. Automated tools find only part of the problem, so we also test the key journeys by hand: sign-up, checkout, and anything a user does every day.
Do you only do the front end, or the API as well?+
Either. A lot of front-end pain is really an API shaped for a different screen, and when that is the case we can fix both sides. If your backend team owns the API, we write down what the front end needs from it and agree the contract with them, rather than working around it in the browser.