With the exponential pace of technological advancement, businesses strive to get the best out of it and to ensure their web app runs smoothly on all browsers and platforms. As an end user’s attention span continues to shorten, so will he or she not hesitate to press the back button on their browser if a site seems faulty. So, what’s the solution? Make web apps and sites work flawlessly on every browser, device, and platform. It sounds like a simple and straightforward goal, right? If a business doesn’t wish to lose customers due to less than optimal UX, cross-browser compatibility and cross-browser testing must be considered.
So, what is cross-browser testing and what should we know about it to assure the quality of our websites?
Cross-browser testing is the practice of making sure that the websites and web apps created work across an acceptable number of web browsers.
Recently, we had the opportunity at SDH to develop a project using React with support from Redux/Toolkit. Thing is, though data was kept and fetched in the store, there was no caching mechanism implemented in the app. And holding dozens of responses in the state is not my idea of a cool idea. Whatever the case, it soon got a little too easy to get lost in all those state slices, despite the use of Toolkit.
What’s more, it had zero influence on the backend at that point. With those iceberg-sized chunks of data drifting about, some requests took an eternity to resolve. And since the UI’s application consisted of long item lists with few CRUD operations, it soon became clear that some form of cache would come in pretty handy just about then. So the choice fell to SWR - a library made by the developers of Vercel (also of Next.js fame).