Forum Discussion
Keeping SCORM package small, best practices?
Are they any documents or guides that already exist for best practices while designing in Rise to ensure you don't end up with a massive SCORM file at the end?
If not, can anyone add to this list of recommendations to avoid this issue in the future (for now, without use of an external tool):
-Compress any possible video/ image assets and pay attention to file size as you upload
-When designing in an external tool (Canva, Adobe CC, Adobe Express, etc.) make sure to watch your file size upon download
-Be mindful of use of AI audio generated within Rise, larger file sizes
-Be mindful of GIFS, background image file size, etc.
Anyone else have anything to add or know of any existing resources for this kind of guidance? Additionally, any documentation from Articulate of how much size interactive blocks, custom blocks, or anything else that might take up additional data and need to be considered for usage would be very helpful.
As the eLearning community drives toward more innovation, creativity, and interaction focused around a better end user experience, I am finding it difficult to navigate the balance of this with functionality without fully knowing the sandbox we have to play in (Rise current barrier, easier to see in Storyline).
2 Replies
This might not be feasible if you have an interconnected asset like branched learning, but we tend to break up our courses into multiple SCORMs. This is because our LMS has a hissy fit when anything gets too big (what that size is is anyone's guess) and won't save progress after a certain point.
You can think of the course as a book, with each SCORM serving as a chapter, and each Rise lesson or Storyline module acting as a section. This also helps keep your files manageable when it comes to updating.
You can also compress your SCORM using SCORM compressors like Doctor Elearning. Try it and let me know if it also worked for you.
