How React shaped Haptik’s frontend story
Submitted by Nabendu Karmakar (@nabendu) on Thursday, 7 December 2017
Full talk on success and failure stories with React; code overheads and code rewrite stories with React
At Haptik, we use React extensively. In fact, 5 out of our 5 heavy lifting customer facing Apps are written in React.
But this was not the case always, we had to try a whole lot different technologies to fail and then move to React 2.5 years back only to succeed. React has, in fact, made our frontend journey very simple.
This talk will revolve around how React has helped a startup to build and ship great bug-free and good looking products. How React eased our process to get started, our learnings to build extensible products and things we did wrong (and learned from).
We wish to give back to the same React community who has helped us grow extensively in our journey.
This talk revolves around how Haptik has achieved great success using React –
- Will talk about frontend use-cases we have at Haptik.
- Issues we faced - the need for a solid, production-ready framework.
- React coming into the picture.
- How (as backend engineers) we started using React 2.5 years back when it was pretty new.
- How we use React now.
- Our key learnings.
- Must-have and must dos when we choose a frontend stack and how React passes every time.
- Our approach when composing and architecting a React project.
- Our go-to libraries and their use cases.
- Things that we ignore while coding in React.
- React for startups.
- Future of React in general and future of React in Haptik.
Nabendu is a Senior Fullstack Engineer with a experience of more than 5 years in building scalable and extensivle products. He’s currently heading the React team at Haptik Inc. and is associated with React for more than 2 years.
A tech evangelist, Nabendu loves to create stuff, solve complex problems and build scalable solutions. Currently he is very busy pushing great conversational UIs.