Hey @Kade333!
It looks as though the first issue might be solved by first disabling mobile view for the components in your container and then enabling mobile view for the container followed by the components inside. When taking a look at your app I noticed the container wasn't enabled on mobile and attempting to enable it threw an error that it overlapped existing components. Disabling and enabling them like this should fix that.
The second issue you're raising looks to be a bug on our end. At the moment though, our mobile dev team's efforts are going toward the native mobile app builder mentioned here. I can't guarantee when or even if there be a fix for that particular bug since we're primarily looking to address people's needs with the new platform. Is it something you've already taken a look at?