Thank you!! Well, to be honest, I initially advocated for a totally different state design — our state was everywhere. This backfired at us because although one should keep state as locally as possible, this made further growth impossible. Another thing we could have done is use better state management solution but Redux in the beginning felt like an overkill.
Another thing is that initially, our data structure was much different (very simple and straightforward) but as the number of features grew, it was no longer possible to pretend like we will keep it simple :D we had to make some multiply-nested objects.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Congratulations, for making an app that 1k+ people find useful.
🥳🥳🥳🥳
Please tell me about what kind of refactoring you did to scale the app.
Thank you!! Well, to be honest, I initially advocated for a totally different state design — our state was everywhere. This backfired at us because although one should keep state as locally as possible, this made further growth impossible. Another thing we could have done is use better state management solution but Redux in the beginning felt like an overkill.
Another thing is that initially, our data structure was much different (very simple and straightforward) but as the number of features grew, it was no longer possible to pretend like we will keep it simple :D we had to make some multiply-nested objects.