Inspiring

Question

Escape from Responsive Design Hell

Forum|Forum|9 years ago
May 18, 2016
3 replies
586 views

So, I recently started using Captivate 9, graduating from version 6. Working on a new project which I knew had to be HTML5 and work on tablets as well as computers.

Naturally, I assumed this meant I needed to create a "Responsive Project." I spent considerable time learning about this option, including watching tutorials and reading the Forums. After much trial and error, I got all the elements of the prototype Captivate module to line up correctly at 4 different breakpoints. In between those breakpoints though, things were still misaligned. (I mean, they were fine at 800 w and 600 w, two different breakpoints, but if I sized the browser screen to 700 w, no good.)

Anyway, I saw several wise persons on the Forums make the point "Are you sure you really need a Responsive Project?" I thought, since it had to work on different screen sizes, the answer was Yes. What I didn't know, but just discovered, is you can create a NonResponsive Project and output to HTML5 with "scalable" content. Wow. That fixed everything. And I only need to build it once, not four times for four different breakpoints.

So my questions are:

Why didn't Adobe tells me (more clearly) that you can have a "scalable" project that is not what they call "responsive"?

Why would anyone want to build what Captivate calls a Responsive Project? What are the advantages to make it worth all the work and pain?

I am interested in hearing others' views. Thanks.

Jack

responsve

This topic has been closed for replies.

C

Corbin-st2HItAuthor

Inspiring

Thanks, everyone.

I am testing on a phone even though the requirement is just desktop and tablet. The scalable version looks good on the phone too. And it does make sense to me to use responsive design if you need a different layout on smaller screens - I've done that in Dreamweaver for my website.

As for the matter of "management wanting responsive because it's trendy", I wonder how many stakeholder actually know the difference between responsive (adjust layout) and scalable (adjust size of the content, same layout). As long as it looks good on all required devices. In other words, "Sure, boss, this is responsive. See how it changes size." :-)

- Jack

RodWard

Community Expert

You are correct that there is a lot of misunderstanding in this industry about what 'responsive' truly means.

I even once had a vendor of a rival elearning authoring tool tell me on this forum that their tool created responsive output when in fact it was just scalable. So if even the people making the tools don't always know what it means, what hope does management have?

Captiv8r

Legend

Hi there

What the heck. I'll wade in knowing full well that I'm likely wrong and will be pointed out, I'll offer my own observations.

Responsive is the "new kid on the block". You know. He's the one that came from that exotic land. Everyone wants to be like him and if you aren't? Well, you are somehow "missing out".

Sure, it's great that things respond and all, but as you have seen, it requires a completely different mind set. Instead of designing for one audience, you now have to think about designing for up to five audiences (since you have five breakpoints that are possible).

Especially when working with a LMS so tracking can occur, I personally find myself questioning the value of deploying any sort of training that will occur via a smart phone. But that's just me. Maybe there are hordes of people out there that truly enjoy staring at a four inch screen and trying to comprehend information presented that way. My gut says that it's just another check mark that management can tick off and wildly exclaim, WE ARE RESPONSIVE!!!!

On the other hand, tablets would seem to make more sense. So there's likely a real use for them.

Cheers... Rick

RodWard

Community Expert

I agree with you Rick. I think many types of e-learning content are simply NOT suitable for delivery on a smart phone screen.

However, I think you are correct that management won't appreciate that fact in many cases and (as they like to do) will just mandate "Go Responsive" because it sounds like the "techie switched-on" thing to do.

I

iDoNotBelieveIt

Known Participant

I have just spent some time redesigning the format I use to work across devices. I share the concerns about phones but people do use them; I even have them joining in live webinars on them. Plus when I test on a phone it is surprisingly good. As Lieve pointed out the main design issue will be for phones on account of the screen size. However resolution is improving all the time and breakpoints are determined by pixels not dpi, so the higher dpi phones will display at the tablet breakpoint. Devices also have different aspect ratios.

If scalable output works for you great, because designing for responsive is very time consuming and the previews are guides only. They are not WYSIWYG.

Lilybiri

Legend

I try to avoid responsive projects as well, but will try to clarify.

You need a responsive project if you want a different layout for one or more breakpoint views. Especially on the small resolutions of phones, maybe you do not want to have the same objects, or not a video but a static image instead. Same with views in Portrait mode which can benefit of another layout as well. But it is a lot of increase of work if you have to create a real responsive project. Moreover as a former professor, I'm not convinced that you can deliver the same type of content on all devices.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded