Curious how others have designed the UX of homepage(s) for logged-in vs. logged-out users.
We currently have 2 URLs for two versions of our Homepage
- Our Homepage where users can signup/loggin
- Another Homepage that we redirect users to when the user is logged in.
In doing usability testing with our end users, logged in users have reported that they are confused when they type in our homepage (it partially loads) before a workflow redirects them to the logged in other page. The UI is choppy because the homepage URL partially redenders before the workflow redirects the user.
How might we think about redesigned our homepage for logged in/logged out users? We’ve noticed that other major sites use the same URL for both the logged in and logged out user. Are Bubblers using only one URL and conditional logic to support homepage variants? Are there other ways to reduce the choppiness of the redirect and thereby have 2 separate URLs?
An example: Twitter. If you’re logged out, you’ll be on a version of the homepage the asks you to sign up. If you’re logged in, you’ll automatically be taken to a version of the homepage that = your twitter feed. (notably the same URL is used for both)
An example: Meetup. If you’re logged out, you see one homepage. If you’re logged in, you see a list of event for your meetup groups (notably the same URL is used for both)
I put everything for the logged out user in one group, then everything for the logged in user in another. I don’t show anything until I run a workflow to determine whether or not the current user is logged in, then I show the appropriate group. Works alright, but takes a hair longer to show anything when the page is loading. There’s no flashing, though.
1 Like
@emmanuel, do you know how bubble’s homepage redirects to bubble.is/home for logged in users without flashing the logged out homepage first?
Also, does your roadmap include allowing us to only load the code that’s visible on the page? …so hidden groups/content don’t need to get loading, making initial page loads a bit faster?
I ask because we’re trying to decide how to structure our logged-in and logged-out homepage, and both of these factors may change our approach.
Thanks.
You can explore the app in the editor at bubble.is/apps. It’s just a page load redirection.
1 Like
I didn’t realize that code was public. Thanks for sharing.
As for the second part of my question:
does your roadmap include allowing us to only load the code that’s visible on the page? …so hidden groups/content don’t need to get loading, making initial page loads a bit faster?
We already do things like that for repeating groups, and yes, optimizing this more is on the roadmap.
1 Like
Awesome. Thanks for the info.
