To provide a better experience for those of you with large screens, we've now optimized the layout of the Load Impact app to provide a better experience for large screens. Check out the new responsive layout: why now? We'll share that, too.
A little history: back in 2015, we refactored our app with a focus on improving the whole user experience. Among many improvements, this release delivered better app performance, visual design, and user experience.
Large upgrades like the one in 2015 (1) always have more risks and unknowns. With such a huge project scope, the deadline became unreachable, and we had to begin removing features and improvements for the launch day. At the time, as important as it was, we had to delay creating a responsive layout.
Thus, the grid we shipped looked like this:
The danger with such a delay, of course, is that we might never have gotten back to creating the responsive layout. When a SAAS company in a competitive market postpones any action, it risks not finding the time to work on it in the future. As expert Hiten Shah pointed out in his SAAS newsletter:
The #1 challenge that people have with product development can be summed up in one word: Prioritization.After the launch, the design was broadly praised. We had only a pair of user comments (2) regarding the limitation of the old layout. But a recent analytics review showed us than more than 40% of our users access the app from a large screen.
The statistics didn't surprise us. We provide a developer tool, and most developers use a desktop monitor. But the discovery forced us to more urgently prioritize the experience on large screens.
Luckily, the implementation was also more straightforward than we expected, thanks to our having built a good, maintainable CSS architecture and the ability the CSS3 flexbox standard brings to create layouts easily.
We will be iterating more improvements for large screens soon. In case you are interested in the topic, we found these articles about responsive large screen layout worth sharing:
Happy load testing!
(1) In general, we deploy many small upgrades than a large one. Minor iterations have a smaller scope, are easier to plan, and receive faster customer feedback.
(2) Don't expect to get critical feedback from your users without seeking that feedback directly. People tend to accept what you provide them without commenting to you.