Research and analyze your user's most common screen resolutions on your website or app.
Web design is hard. There is a never ending list of unknown variables to take into account as you are designing a new feature or tweaking the layout of a checkout page. These “unknown unknowns” can be frustrating and hard to plan for. Often it’s the simple questions that drive you the most crazy.
A question as simple as “What screen size do my users have” can be pretty difficult for designers and product managers to answer—yet critical to solve.
You need to understand how your app or site is seen by your users to make the correct design tradeoffs.
That’s why today we are excited to announce our Screen Resolution Breakdown report, available for each search and segment in FullStory.
Like all of our data visualizations in FullStory, the Screen Resolution Breakdown is interactive and tied to the specific search you are performing in FullStory. To find it, scroll down below your list of session recordings for any search or segment in FullStory.
We hope this small release will help you solve a simple but important problem—one that has dogged users for some time.
Analyze Performance by Screen Resolution With FullStory
As simple as it is, using Screen Resolution in FullStory becomes powerful when you combine it with search/segmentation and session replay.
For example, when you're in FullStory, try the following:
- Search and build a segment of users who click "Checkout" on your cart page.
- Then, compare this set against a separate segment of users who make it to your cart page but don't click the "Checkout" button.
For each segment in FullStory, scroll below your list of sessions to find the Screen Resolution Breakdown.
By comparing the Screen Resolution Breakdown for these two segments, you can quickly determine if certain screen sizes are performing poorly in your purchase funnel.
For your non-converters, you can then refine your segment further by searching for sessions with underperforming screen resolutions. Watch a few of these sessions for clues as to what might be the problem.
The power of the Screen Resolution Breakdown in FullStory depends on how you use it. So go ahead and log in to FullStory, pull up one of your favorite segments, and prepare to be surprised at just how many different ways your users are engaging with your site or app!
Psst ... 👋 Still here? Curious what drove us to develop this feature? Read on for the story behind the story for the Screen Resolution Breakdown. 👇
Why We Decided to Build a Screen Resolution Card
We get excited for all feature launches at FullStory, no matter how small the release. Product development is hard work requiring coordination across marketing, design, and engineering to create something you’re proud to release into the world. Screen Resolution Breakdown is particularly exciting for us because it has been our most frequent customer request since … well … forever.
Advanced FullStory users may have noticed a suggestion box that sits in our app. Never seen it? Find it and leave us a suggestion! When you take the time to provide us with feedback, it pings our Slack channel—we really do read all of these.
Over the past year at FullStory, it’s been painful to see this suggestion pop up over and over again. Here’s a glimpse from the past couple months alone:
What makes this request so painful is we have always had the building blocks and ability to provide this feature—just not a process to prioritize creating and launching it relative to other things we’re excited about.
How do you prioritize small releases like this one with larger, more strategic undertakings like DevTools?
The Top Ten
As it turns out, the ceaseless clamoring for this feature drove the creation of a new process at FullStory that’s brilliant in its simplicity. Here's how it works. We list out a collection of small-ish feature requests harvested from customer visits, support tickets, and internal musings. From there, based on voting from each Job Family at FullStory we rank these requests into the “Top Ten List.”
For a young company that chose huggers over product managers, creating this easy ranking process was a big step forward for us.
Now we have a process to ensure we fulfill small, requested product enhancements—the kind that delight our customers—even while we work on larger, game changing feature arcs.
From List to Launch 🚀
Once our engineering and product designers plucked this prioritized feature request from our our newly formed Top Ten List, a prototype was quickly completed.
So far, so good!
Except the prototype sat unlaunched for an extended period of time. Alas, there was a gap in our new Top Ten Process. There was no real owner for these undertakings and no real checklist for what needed to happen before they were launched. No owner? No launch.
As we've grown, we’ve come to need pure product managers on our Hugging Team. And we’ve already seen some of the benefits they can provide to product decisions. Pushing the Screen Resolution Breakdown report from “behind a flag” to “available to all customers” was the perfect task for our newly created product management practice.
With owners in place, it wasn’t long before we’d beta tested the Breakdown. We gathered customer feedback and sorted out “launch blockers” from “fast follows.” Finally, we were ready to confidently launch this feature to all of our users.
And now you have it!
While it may have taken us longer than we would like to release such a popular user request, the Screen Resolution Breakdown is here.
Check it out and let us know what you think! (You know where to go.)