Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Testing my project for mobile and tips to reduce grief with it

Community Beginner ,
Nov 16, 2015 Nov 16, 2015

Hi guys

I've looked at previous threads on publishing on mobiles and I'm filled with dread about it ! I'm seeing a fair bit of frustration and a few unanswered questions which is making me quite worried. I'm hoping for help to ensure that I avoid similar pitfalls when publishing for mobile and tablet. I have two questions to date:

1) I'm trying to "test" publish a project to mobile by trying to send a zip file with the html link within it. This is working on my laptop but I can't get it to work on mobile. Any tips on how I can test how the project plays on my mobile? I don't yet have an LMS or a website to host at this point.

2) When I change the view as the project plays on my computer to tablet or mobile mode I do notice that quite a number of objects/images go out of alignment. If this is the case do I need to manually insert these images for each screen size (which means I have to go through it three times). Is there a smarter way of doing this? Someone mentioned vector images and I had no idea what that meant. Are there certain types of images that don't resize well/others that resize better?

3) Any general tips to help me have a smooth experience when designing/publishing to mobile?

Thanks

Hamada

849
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 16, 2015 Nov 16, 2015

Using a zip file is not the way to go unless you were building a SCORM package and you were uploading it as a zip to an LMS.

Ideally all HTML5 or responsive content should be tested from a web server.  If you don't have that, then you need to at least test using Adobe Edge Inspect and use the Adobe Edge Extension for Chrome browser on your desktop:

Adobe® Edge Inspect Installation Guide

Building responsive projects is tedious at best.  You have to start with your primary (desktop) output and then reposition, resize or replace objects accordingly for all the other viewport sizes.  It will add significant development time to a course project. Captivate 8 had three viewport sizes, Captivate 9 has 5. For my money there is really not much point creating a responsive project unless you have a truly compelling reason.  The fact that you want to play courseware on mobile devices DOES NOT of itself make a compelling reason as normal HTML5 content will also work quite well.  It doesn't have to be responsive to be 'mobile'.

If you want the 'smoothest and easiest' route for mobile learning, avoid responsive projects and just build HTML5.  That's my advice.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 20, 2015 Nov 20, 2015

Thanks Rod - that's really helpful. Can I ask then what would a compelling

reason to build a responsive project be?

Also, you mention that a standard non-responsive project will play OK in

mobile/tablet - but if I have a fair few diagrams in my project won't the

diagrams potentially be out of whack when viewed on mobile/tablet if I

don't do a responsive design?

Thanks again

Hamada

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 20, 2015 Nov 20, 2015

Hamada asked:  "...what would a compelling reason to build a responsive project be?"

I ask myself that question a lot and I struggle to come up with a really good answer. 

In the world of responsive WEBSITES there is good data to back up the allegation that a larger and larger percentage of people are attempting to view the content via cell phones, and when they do, they're almost always going to be doing it in Portrait mode.  Since there's money to be made or lost when people can or cannot view your content, web designers are more and more driven to accommodate an audience that will be viewing their content this way.  That's why you are seeing a lot of websites nowadays with 'mobile-friendly" layouts that feature rather huge heading texts and single graphics with a bunch of text to one side or the other.  These websites bootstrap or foundation JS to dynamically alter the font CSS styling to look acceptable in all types of viewport sizes.  And they have the graphic wrap to be above or underneath the text when viewed in portrait mode on a cell phone.  It's a relatively simple formula.  But they're NOT trying to move things around on the screen and they're NOT trying to synchronise audio voiceover and Closed Captioning with it.  (If they do, they use straight video instead of animation.)

It's these responsive WEBSITES that Captivate's responsive output is taking as a concept model for E-LEARNING.  But my intuition tells me that these two content genres are VERY different, and there are in fact VERY FEW people trying to access typical e-learning courses on a mobile phone even now.  A great deal of courseware is simply NOT going to look good or be readable and deliver good instruction at such a small size. (Can you imagine trying to learn Photoshop on a mobile phone?)  For most e-learning content the audience will want to be using an iPad/Android tablet at least, and that tablet will most likely be in Landscape mode, not portrait.  But my gut is telling me that the desktop browser experience is still by far the best platform for delivery of good e-learning content and there would be VERY few people that can ONLY view it on a mobile phone and do not have a tablet or computer as an alternative way to view the learning.

So I come to the conclusion that for software training (simulations etc) I would NEVER recommend building a responsive project.  The screenshots would be unreadable at most sizes.  You COULD potentially see soft-skills training working for responsive, but I would be recommending to clients that they building it only for tablet screens and up.  Since most tablets are running resolutions of at least 1024 pixels wide or more, their resolution is not that much different to desktops.  So why use responsive, when you can just build the same course for both?

And the REAL killer is COST. Since each different viewport you build for with responsive projects adds another layer of time and cost to your development budget, your client would need to see proof that going to all the time and expense of building for cell phones was going to pay back.  Quite frankly, in the current economy, where training budgets are being cut, not expanded, I don't see many clients that are SO wedded to the idea of mobile learning that they are willing to double or treble the development budget JUST to be able to brag about how the screen changes from desktop to tablet to cell phone.

But your mileage may vary...

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 23, 2015 Nov 23, 2015

Thanks Rod. I agree with you about mobile, particularly with the course I'm developing does depend on graphs/tables and diagrams. And I think you are right the cost benefit doesn't add up for such courses So I will be doing the remainder of my courses as non-responsive.

Two last questions then:

1) just picking up on your tablet point - say I was developing a non-responsive project for tablet - would the tables and graphs I develop non-responsively be slighttly skewed when played on tablet? OR even mobile in the off chance that I have some more basic lessons with not too many graphs etc?

2) For the responsive projects I've done so far, are they convertible back to non-responsive?

Thanks again

Hamada

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 23, 2015 Nov 23, 2015

If your tables and graphs are not displayed with changed aspect ratios in desktop or mobile then they should not be 'skewed'. 

Responsive projects cannot be converted to non-responsive and vice versa.  You'll need to use the same original assets to rebuild your course.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 13, 2015 Dec 13, 2015

Hi Rod

Thanks very much for your help so far and apologies for not coming back earlier - I took a little break from the day to day madness !

I just had one last follow up question to your above post where you said that as long as my aspect ratios for things like graphs and figures aren't changed then they shouldn't be skewed. This leads to a relatively ignorant question - how do I know whether my aspect ratios are skewed or not?

Thanks again

Hamada

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Dec 14, 2015 Dec 14, 2015
LATEST

If the graph or table is inserted as an image, just reset the image to it's original dimensions under Properties > Reset to Original Size.  That will also reset it to original aspect ratio.  If the image jumps appreciably in size then you are wasting bandwidth.  Export the image to a graphics editor and resize it to be ONLY the size you need to display in Captivate.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Help resources