I just published a StoryMap collection that contains 6 StoryMaps and 3 Experience Builders. When using the 'Preview' function of the collection, all pages display well on all devices. However, when I pulled it up on an iPhone, I had trouble with 2 of the experience builder apps (these 2 are fullscreen while the 3rd is scrolling).
The issue is that the experience builder apps are not displaying as a fullscreen app, instead the user has to scroll a little to view the bottom of the app. I believe that since the collection has a header bar (where the navigation buttons are), it is pushing the experience builder app down and forcing the page to be scrolling. For a user, it is difficult to scroll the page because you can only 'grab' a small portion of the screen to scroll and see the bottom.
The work-around that I decided to use is using a 'footer'/gap at the bottom so that everything is visible in a single screen. The drawback is that depending on the user's phone screen size, some users will see the white space at the bottom of the screen.
Link to Item 2 of the Collection
Link to Item 3 of the Collection
Fairly confident the behavior is caused by integrating an experience builder into a StoryMap collection, however I can't tell if the issue is more on ExB's side or Story Maps side.
Anyone else seen this behavior in their own collection? Any other work-arounds that may better address the behavior?
Notes: behavior was observed on 2 different iPhones, have not tested on an android. Same behavior while using Safari and Google Chrome apps.