State ManagementState Management can be fairly difficult to understand at times. New software patterns are for ever adding complexity to the situation and adding too this confusion.So mitigating this should be considered a priority. That's why we think tools like Zustand and tRPC are game changers.In most cases, the above tools are great and could be used, arguably, in all cases. But sometimes it's just easier to use tried and tested tools like Redux for the big state management data.Developer ExperienceDeveloper Experience, sometimes called DevEx or DX, can be important for a company that employs developers. It can be a good way to retain high quality staff who would otherwise jump ship to work with other companies providing better DX.Another benefit is that development may be more efficient, both in output and code fidelity. Because tRPC is based around TypeScript and as a result inferences are made on the client against types on the server, this can boost the accuracy of tha system and remove many issues relating to client/server communications regarding type safety and data structures. So this would be a benefit to the organisation that uses this technology. The boiler plate for tRPC is much smaller than the alternatives and because of benefits like Auto completion, Automatic Type Safety and Request Batching, we believe it offers a great Developer Experience.There are still user cases for using GraphQl and Redux like when you have sepearete frontend and backend teams or the backend is not written in TypeScript, but if the development team are using TypeScript both on the frontend and backend and the frontend has access to the backend code, for the time being we think tRPC seems like the obvious choice. This article gives a good explanation about whether you should use tRPC or GraphQL for a project.
State Management
So mitigating this should be considered a priority. That's why we think tools like and are game changers.
Zustand
tRPC
In most cases, the above tools are great and could be used, arguably, in all cases. But sometimes it's just easier to use tried and tested tools like for the big state management data.
Redux
Developer Experience
Developer Experience
Another benefit is that development may be more efficient, both in output and code fidelity. Because tRPC is based around TypeScript and as a result inferences are made on the client against types on the server, this can boost the accuracy of tha system and remove many issues relating to client/server communications regarding type safety and data structures. So this would be a benefit to the organisation that uses this technology. The boiler plate for tRPC is much smaller than the alternatives and because of benefits like Auto completion, Automatic Type Safety and Request Batching, we believe it offers a great Developer Experience.
There are still user cases for using and like when you have sepearete frontend and backend teams or the backend is not written in TypeScript, but if the development team are using TypeScript both on the frontend and backend and the frontend has access to the backend code, for the time being we think tRPC seems like the obvious choice. This gives a good explanation about whether you should use tRPC or GraphQL for a project.
GraphQl
Redux
article