Default Responsive Screen Resolutions

[gregl27203360]

Why are the default screen resolutions for responsive design in Captivate 9 not setup to match the relative screen dimensions by default? I realize they can be manually adjusted, but am trying to understand why these defaults don't seem to correlate with the actual devices.

For example, the default tablet portrait dimensions are 768x627, yet when adding the additional landscape breakpoint, the dimensions become 1024x627. These two dimensions are not even related. If the landscape dimensions are 1024x627, then obviously the portrait dimensions should be 627x1024.  Why the differences and why are the default dimensions not setup to actually match an actual tablet in the first place? An iPad with retina display (for example) has a resolution of 2048x1536 which of course scales down to 1024x768. So why are the default tablet dimensions not setup for 1024x768 (and 768x1024 respectively) to begin with? Just trying to understand why the odd dimensions were setup as defaults in the first place.

The same is true of the default mobile dimensions which default to 414x466 (portrait) and 667x410 (landscape). Again, if the landscape dimensions are 667x410, then the portrait dimensions should match in reverse as 410x667 (not 414x466). Again, even here the default dimensions seem to be extremely low resolution for most of today's mobile devices.

I'm also trying to understand is why the screen resolution limitations are so conservative. The highest screen resolution is only 1280 pixels wide? Why does Captive 9 not allow for resolutions that account for target audiences with monitor resolutions of 1366x768 and higher? Even the tablet resolutions don't seem to make sense, as the iPad retina has a screen resolution of 2048x1536. Is there a reason that these higher screen resolutions are not supported in Captivate and are there any plans to introduce then in future releases?

Thanks!

[Paul Wilson CTDP · Accepted solution]

Your assumption is that a tablet with a screen resolution of 1024 x 768 will produce that resolution eLearning along with the reciprocal aspect ratio and dimensions in portrait. What you are not accounting for is the number of pixels that various browsers will consume. 

For example, take a look at these screen shots from my tablet using Safari as the browser.

You would think the numbers would be the same right? Ah but because the browser controls and address bar gets moved from one edge to another, this changes the resolution and aspect ration.

The fact is that there is no magic aspect ratio or resolution that will account for the vast majority of mobile devices and computers. I recommend that you conduct a technical needs analysis for the audience you are designing training for. For example, if you worked for Oceanic Airlines and all their pilots used iPhones and iPads, get your hands on a sample of these devices and check their browser resolution using a site like http://howbigismybrowser.com/

[gregl27203360]

Thank you Paul!

You've answered my question. Much appreciated! I clearly was not taking the browser into account. 🙂

This is very helpful. I will conduct tests on specific target devices such as iPads and iPhones in order to determine the exact numbers that I will need to customize my responsive layouts.

Still, it does seems rather odd that the desktop default resolution is 1024x768 which, of course, does not take any browsers into account for anyone who might be operating in that old and outdated screen resolution/aspect ratio. I'll most likely be creating content at the maximum 1280px width for desktop, but still don't understand why Adobe Captivate doesn't allow anything larger than 1280px.

[Paul Wilson CTDP]

Were you in attendance at the Adobe Learning Summit in Las Vegas? We learned about the possibility that break points may someday get replaced with something more fluid and dynamic. Obviously it's too early to say for sure what the future holds for responsive design in Captivate, however I can tell you that it has steadily improved since being introduced several years ago.

[gregl27203360]

Sadly, I was not in attendance at the Adobe Learning Summit in Las Vegas this year, but hopefully next year! 🙂

These initial questions came up since I'm just beginning my exploration of Adobe Captivate. It's always good to know that they're working hard on making improvements and innovations to existing limitations. I'm sure that the break points will certainly evolve into something more fluid and dynamic. Thanks again for your help! Cheers! 🙂