Rambox: group your apps and keep their sign-ins clear
Rambox brings email, chat and other web apps into one desktop window. It helps people who switch between clients or work accounts organize apps in workspaces and separate accounts through sign-in profiles.
Form your own approach first, then explore the reasoning to check trade-offs and validation you may have missed. There is no single right answer.
01
DESIGN QUESTION
How should an app preview explain a different group and account?
Design an app-adding flow for a tool used with several clients. A user has a Client A workspace but is about to select a Personal sign-in profile for a new inbox. Workspaces group apps; profiles determine shared sign-ins. They are allowed to differ.
- Do not prohibit legitimate use of a different profile or sign in on the user's behalf. Design a relationship preview and a way to change it before adding the app.
- Walk through inheriting Client A, explicitly choosing Personal, and retaining the original profile after moving the app to Client B. The third case is this exercise's specified move rule, not a claim about Rambox behavior.
- Deliver a flow sketch, key messages and an observation task testing whether users can explain which sign-in information the new app will use.
Explore the reasoning
- Show the workspace and sign-in profile names together, with text distinguishing inheritance from an explicit choice. Do not rely on matching colors alone.
- Explain the consequence of a different profile before confirmation. Difference itself is not an error; the user may intend it.
- Under the exercise's rule, moving an app does not change its profile. Check whether the moved app misleadingly appears to inherit Client B; offer a separate change if needed.
- Ask observers to predict the account in all three cases, then inspect the prototype's feedback. Separate conceptual misunderstandings from misplaced controls. One correct answer does not establish that the design is validated.