I have seen another post on this issue, but I wanted to make some clarifications as I am still having issues.
I am building a native app, but for now it’ll only be used a web app, but I wanted it to have the native feel and will eventually submit it to the app store.
My issue is that some of my groups are much longer than the native page. As a result some pages that should be fixed, now have large empty spaces beneath them, which is not optimal for the user experience.
I was told that I could simply make my groups whatever size i needed, then go back and resize the index to create the “scrolling effect”, however this has not worked for me. My larger groups simply get cut off. Perhaps this only works on native apps that are actually on the device?
@mylodge
That sounds doable, I have many groups I was hoping not to redo all of them. If its ends up being the only way then I’ll give it a Shot. Is this something that you have implemented?
in part yes, could you maybe just create that reaping group for each and drop the already created group inside the repeating group? might save you some time.
Just a theory, as I’m not in front of a computer to try it, but you should be able to use a collapsible group to change the sizes of your app screens. I’ll attempt to confirm it some time tomorrow if no one else does first.
Not quite. The groups only collapse when they are hidden/empty, so your app screens wouldn’t collapse because of that.
Let’s say your app page has a height of 2000, but the current screen you’re building should only be 1000 pixels tall. You’d create the 1000 height group, then fill the other 1000 pixels with an additional collapsed group that gets rid of the extra space.
@natedogg, I get less scroll, but still too much. enough to lose view of the group completely. Perhaps you can try, i might be doing it differently than you intended.
Here is what I did
I brought up one of my groups
I created a second group beneath it and stretched it out to bottom of the index
I set that second group to be hidden on page load and checked the collapse on hidden option.
This time, I made the main group the height of the entire page and put the collapsible group inside the main group at the bottom. If you follow this method and insert a collapsible group at the bottom of each of your main groups, the page should be the correct height no matter what.
@NigelG I finally figured it out! It turns out that I required both methods 1 and 2. I needed a collapsing group to moderate every individual group AND another group outside of those groups to moderate the length of the index itself. This forum and community is really fantastic, thanks for your time and help Nigel!
Sorry if the info I gave didn’t work out. I’m using the native app previewer.
@natedogg, what happens when text is set to “stretch to fit” causing a group to expand beyond the app’s dimensions? This seems to increase the height of the entire app, rendering other groups scrollable with blue space beneath them.
Is it best to avoid anything that increases the height of a group? Or is this only an issue within the previewer?
I tend to avoid elements that expand my main groups in native apps unless I have so much content that I have to expand.
And if you have to display enough text that would expand the element, the best practice would probably be to expand the parent group and make the text element large enough that it wouldn’t have to expand.
But in general, too many expanding/collapsing elements can be buggy/hard to clean up mistakes.
@alexsstockton can you post what you did? I would like to take a look at it since I’m making a native app as well and looking at how to expand/collapse groups. Thank you.
I did click on “collapse when hidden” but still it keeps scrolling. It doesn’t seem to work. At least the whole app-page is suuuper long, since it’s a one-page-app and the super long “edit profile” group is always part of it.
Also, I did set the app-page itself to native app/mobile and restricted the height to 600. But now it doesn’t scroll further than those 600px, despite my content being longer
When I expand to the full length everything else gets messy. (Like the floating save button for example - it just disappears.)
