Experience Thinkers

What is State and Why we need it? Photo by  Daniel Leone  on  Unsplash This is a two-part series, In the first part, I am going to write about why we are speaking a lot about  State  and  why we need it in our application.  In the second part, I would write a sample to-do application using React and apply  different state containers to evaluate against different architectural concerns like  Scalability ,  Manageability ,  Performance, and Productivity . Let's start swiftly….. Photo by  Austin Distel  on  Unsplash I am sitting in my office after finishing one of the major application, my state of  mind is relaxed and COOL . Well, am I supposed to write about my state of mind, which is in a COOL state or do I need to focus on Application  State  in the web ecosystem? Well, if you take a birds-eye view, both  Mental state  and  Application state  looks to be representing some or other form of information. My mind state is  relaxed, cool and happy , where is an

Lately I started working on a Frontend Migration project where the Application was earlier running on Durandal and Knockout.  This interesting and lovely story started when one if out chief architect installed me to understand the product line from a UI perspective. I found that there are multiple products running on outdated technology stack like Durandal and knockout There is no harmonization across these products. They need a single unified platform (SSO) for all the assets Selecting a future technology stack is a very complex work which required understanding current and future requirements, trade-offs, learning curve etc. A wrong selection would impact productivity in product development. So I did a comparison analysis around some of the frontline frameworks available like React, Angular, Polymer. Couple of you thought about why I have chosen only these three items in the analysis : Well there are good number of UI frameworks available in the market whi