You’ve spent months, maybe even years, building an application for your organization. It looks great, has gone through a rigorous QA process, and has gotten good reactions from your beta testers.
Launch day comes; are you certain your application can stand up to unexpected demands, high messaging rates, or slow data connections?
In software development it’s easy to push addressing performance concerns towards the end of the process (maybe even when it’s too late). However, there are tools readily available to help you identify, and mitigate performance issues early on.
As our application began to grow we started noticing our animations drop lower than 60fps and visually poor mounting/rendering performance. Our application also contains a large chat feed with multiple channels to chat in. As the messages in each channel began to grow (hundreds, or even thousands) we would notice poor scrolling performance and poor rendering performance as the user switched between channels.
By using the tools and methods below, our team was able to identify and eliminate 13,000+ wasted renders in initial application load, and thousands of additional wasted renders post-load in the Church Online Platform.