Hi Wendy -
Thanks so much for responding. See below for more details.
In SL2, if you selected Web Publication and checked HTML5 only, the published output had a mobile folder. Within that folder, there was a player_complied.js file. Within the body of that file, it was possible to locate and change the setting of populateIOSLaunch to remove the need for the user to have to click a Play button to initiate the start of an interaction on an iOS device ( avoiding multiple clicks to just get the mobile user started). This solution only works if the first slide is NOT a video, so we adjusted our SL2 content accordingly.
However, in SL 360, that player_compiled.js file no longer exists. Instead, according to Articulate Support, the automatic display of the white screen and play button for iOS is controlled by the app.min.js file, which is referenced as a link source in the last lines of the story_html5.html . I've been able to open the app.min.js file, but the setting of populateIOSLaunch is no longer used. Because the file in minified, our developers are having difficulty determining what part of the code is actually controlling the Play button for iOS.
I thought about using the new responsive player, but my understanding is that it doesn't support JS - which we use extensively to both pass variables between SL interactions and the underlying database, and to notify the event listener on triggers associated with the user completing / cancelling out of the interaction.
Unfortunately, for now, the user experience for an iOS mobile user using Articulate 360 file isn't on par yet with our SL content. If you or anyone else has a workaround or solution now that we've moved to SL 360, I'd welcome it.
Mary