I’m building a SaaS app who’s users will have their own customer-users. I’m starting on my “customer’s - customer user” experience and I’m thinking it may be a good idea to keep them separated by page? What’s the best way to set this kind of thing up?
Example: A Customer-user, via index page, would click the “customer portal or Login” buttons and be directed to separate bubble-app pages? Or would it be better for me to have them access the same main-page but with permissioned and conditional access & views?
What should I be most concerned about?
Just my thoughts…
- If it is going to be a mobile app… 1 page
- One page is simpler to manage the code / Or IF multiple pages you should leverage extensive use of reusable element to simplify the “no-code” and fix bugs once.
- If you do use multiple reusable elements that interact then you must have a messaging method to pass information between them since they typically can not access each others custom states that may be used to store intermediate results.
- If you have all elements native to one page then custom states are more accessible.
BUT I have done both at time even it the same application… A single page with many logical parts controlled by custom states for the mobile app portion and secondary pages with multiple reusable elements for Desktop components. I don’t think it has to be one or the other… rather based on the exact user experience and functionality the user needs at the time.
Again… just my thoughts.
Thanks @jgellis, It does seem like an either or situation… My app, is primarily designed for the desktop user. I’m just not sure if there is a clear rational for keep users separated by page?
Example: Lets say I have 500 Primary App users on the platform at any given time. They may have 30 - 50 of their customer users on the platform at any given time. What would be the inherent differences in having the 30 - 50 customer users on a separate page?
To clarify, these 30 - 50 customer users would, for the most part, NOT produce much data. They would be there to observe progress, approve things etc etc etc.