When designing applications is it better for performance to utilize multiple pages with less stuff or fewer pages with groups and popups more extensively used?
1 Like
Bubble only allows native apps to be one page, so you’ll have to show/hide groups to give the illusion of changing pages.
Check this out: Groups and there relation to performace
2 Likes
What I meant is for an app that is not just a native one. Where an app is designed more to be a web app then anything else. Does it make any difference to use multiple pages or is it more effective to use groups from an app performance point of view.
I would personally use groups as often as possible, yes. Even for the desktop version.
The transition speed is much better.
The only issue is - by using groups, your app will basically be ignoring the traditional functions of a browser default “back” button
So if a user clicks the browser back button - they might leave your app by accident
2 Likes
That’s why I read earlier to build two different applications, one for Apps and another for Web, right?
Yeah I read that as well in a much earlier post but as @natedogg explained to me in a different forum message, you can set one page of an app to be the native app. This way the app uses the same database through all the different interfaces.
1 Like
This issue of the browser back button, is there any way to work around it?
Ya you can, by using URL parameter.
Rather than showing or hiding a group - you would have a workflow that reloads your page; but specifies a parameter in the URL
So the “go to page” workflow function + a parameter.
Example:
Go to page X
Parameter = “Visible = group 2”
So that will show up in your URL - then you can have conditions on your groups to read the URL
Example:
“When 'get data from page URL “visible” is not “group 2” - this element is not visible”
Typing this from my phone - so can’t give to great of example 
But yes - with URL parameters - the browser back/forward buttons can hide and show groups
2 Likes
And this works for a native app? Since it doesn´t let me use the go-to workflow for whatever reason.
A native app wouldn’t have a browser back button…
I thought you were asking about using groups for an app run in the users browser (safari - chrome etc).
But if your building a native app - that users will download from an App Store - then you don’t have to worry about the browser back button.
Just hide and show the groups
On android there will always be a browser back button however, how should I cope with that? I love the fact IOS doesn´t have it since it really facilitates controlling where your users can go and not go, to not show outdated pages, however with android I just can´t seem to figure out how to deal with this problem. Have you designed something for android as well already?
Hello guys, I m trying to built a site that offers three membership “standard, premium and gold” using stripe subscriptions. I need to group the membership in three different user call standard member, premium member, gold member.
can anyone tell me how to get started, I try eveything its not workin
Oh…
no - sorry; I don’t know the solution for that.
i haven’t worked with android yet.
Are you 100% sure about this?
When an app is “packaged” as a native application it kind of implies that it’s an isolated operation. Where would the “browser back” button go to in that instance?
If a user clicks the app icon (on there smartphone home screen) - the first and only thing that would load is the “native” app. So where would/does the back button go to?
Are you testing your “native app” in a mobile browser? Maybe that is where the confusion is coming from.
When your native bubble app is complete - you will compile it with a third party development environment. Many people have used “Phonegap” or “React” to do this
Love this, just implemented it!
1 Like
For example in the instagram app on android, if you do a hashtag search and open a profile from there, when you press the on screen back button, it goes to the hashtag search, if you press the back button again it will probably go to your feed, and from there i would exit.
I am creating a native app that i would like to maintain online as a web, and i am not really sure how to cope with the browser back button as with the android back button.
I don’t know the answer to that - unfortunately.
I have not tested on android - so I don’t exactly know what the back button on the hardware does, in this context.
I realize the issue it might present with a web browser wrapped “native application” - if I am understanding the sceanario correctly. (Which I don’t know if I am haha).
It may prove that the best way to do a hybrid application for android, using bubble - would be to have multiple webviews (rather than building the native app all on one page).
That would require some additional code.
That way the app back button and the hardware back button on android - could go back to the same screen…