In this webinar recording we look at one of our preferred approaches when creating content that needs to be viewed across multiple devices, without using fluid boxes.
This saves design and development time.
The trick is to publish as Scalable HTML.
Example built in the video
https://learningthatworks.com.au/review/scalable_portrait/
We created our end of year Christmas Party game using Scalable HTML5
https://learningplan.com.au/christmas-game/
Thanks for this!
These are great. Thanks for posting!
Thanks Todd, glad you found it useful.
Thanks Lieve, really appreciate your input as always, and do agree. This was to highlight an alternative for users who are still struggling to understand and master fluid boxes.
Also, designing (storyboarding etc) both the desktop and mobile version for a responsive solution can take extra effort (and budget), so once again, this is just an alternative when responsive may be considered, but not absolutely necessary.
If designed with smaller devices in mind, Scalable can be a viable option for some. It is by no means a definite solution all the time.
Thank you again for taking the time to contribute to the discussion!
Did you see my comparison, where I mention Rescalable as wel and talk about developing time:
You are aware, I hope, that this solution is not ideal in many circumstances? Since several versions Captivate offers the possibility to create real responsive projects, either with Breakpoint views or with Fluid boxes. It is only in rare situations that the one file fits everything hype is really practical and true. You put ‘reponsive’ in the tags, but a rescalable HTML file is NOT responsive, it only adapts the scale to the browser resolution, but will not rearrange the layout when going fro landscape to portrait, nor will it replace memory hungry items by smaller ones for mobile devices which have by definition less power and resources than a laptop/desktop.
Thanks Lieve, really appreciate your input as always, and do agree. This was to highlight an alternative for users who are still struggling to understand and master fluid boxes.
Also, designing (storyboarding etc) both the desktop and mobile version for a responsive solution can take extra effort (and budget), so once again, this is just an alternative when responsive may be considered, but not absolutely necessary.
If designed with smaller devices in mind, Scalable can be a viable option for some. It is by no means a definite solution all the time.
Thank you again for taking the time to contribute to the discussion!
You must be logged in to post a comment.
