A client is planning a suite of learning modules that will be created as separate storyline projects, and each one published for use in the Articulate Mobile Player. Learners will have the option to download all of these.
When a learner has a downloaded AMP library of several of these modules, and is is looking at the content offline (on a plane for example), is there a way that a link/hotspot (or whatever) in one file can launch another, without the leaner needing to exit to the AMP Library?
Normal "get URL" links from one project to another, when used in Offline mode, simply jump to Safari and request you to connect to the internet.
I'm not sure I understand what you're looking to do - if all the courses are in the AMP library, the user could just return to the library to access the next course. If they're directed to a URL for the course - it will operate just as regular URLs will in that you'd be prompted to connect to the internet.
As you say it may be that learners will just need to return to the library and launch different modules from there.
What's actually happened - the people I've just been asked to advise, have built a sophisticated, highly graphical 'menu system' as one storyline project, which then jumps to different storyline projects as the learner selects. This menu and its graphical appearance is itself a value-add for their client. They organized it this way as all of the separate modules are being worked on by different people, will be completed / uploaded at different times. Plus also, combining all of the modules into one project may make for a humungous SL file. Lastly, they are trying to avoid reworking everything to use the AMP library as the 'menu' for the modules.
I guess i was thinking that there might be some way to address the AMP programatically, but I did suspect the way they'd have to do things offline.
A related point: there's not much in SL help / tutorials about strategy for menus / modules, very large projects, etc. I may develop something.
I can see with that set up why they'd like to not have to revert to the menu - but even with a link inside a Storyline course - if it's published for use in the mobile player, the user when clicking on it would be directed back through the opening within the mobile player app (it'll all happen automatically - they won't need to click back into the library) so it wouldn't be an entirely seamless process.
I would love to see some examples or ideas you could share here on your experience with larger courses or complex menus!
3 Replies
Hi John,
I'm not sure I understand what you're looking to do - if all the courses are in the AMP library, the user could just return to the library to access the next course. If they're directed to a URL for the course - it will operate just as regular URLs will in that you'd be prompted to connect to the internet.
Thanks Ashley.
As you say it may be that learners will just need to return to the library and launch different modules from there.
What's actually happened - the people I've just been asked to advise, have built a sophisticated, highly graphical 'menu system' as one storyline project, which then jumps to different storyline projects as the learner selects. This menu and its graphical appearance is itself a value-add for their client. They organized it this way as all of the separate modules are being worked on by different people, will be completed / uploaded at different times. Plus also, combining all of the modules into one project may make for a humungous SL file. Lastly, they are trying to avoid reworking everything to use the AMP library as the 'menu' for the modules.
I guess i was thinking that there might be some way to address the AMP programatically, but I did suspect the way they'd have to do things offline.
A related point: there's not much in SL help / tutorials about strategy for menus / modules, very large projects, etc. I may develop something.
Hi John,
I can see with that set up why they'd like to not have to revert to the menu - but even with a link inside a Storyline course - if it's published for use in the mobile player, the user when clicking on it would be directed back through the opening within the mobile player app (it'll all happen automatically - they won't need to click back into the library) so it wouldn't be an entirely seamless process.
I would love to see some examples or ideas you could share here on your experience with larger courses or complex menus!
This discussion is closed. You can start a new discussion or contact Articulate Support.