The issue is closed so discussion can go on here. Three of the more interesting comments which should maybe be discussed here are:
IMO the main issue about multi-account is the UI design and implementation of it. If someone can provide UI mocks on how it should work (setup, account selection etc.) please post .
What are the alternative modes that people do have in mind, in which new accounts may be used? (an account preference)
- separated account?
* tabs to switch chat lists and used account
- alias inclusion account?
* all chats included in the default chat list (“unified/shared inbox?”)
* when creating a new chat the (default) account is preselected in the list of accounts to choose
Same, tabbed or not, for “unnapproved emails” (contact request)?
I’ll provide my personal ideas based on my needs, maybe that can provide some orientation. In general, the XMPP client Conversations is a good example of a multi-account UI.
I imagine the account management view as in Conversations: You can add accounts to the list and activate or deactivate them separately via switch on each entry.
The chat list would then display the chats for the selected accounts in a single list because for receiving I don’t care much about to which account a message has been sent. So the same goes for contact requests.
For replies, the proper account would be automatically selected and for new chats I would select it myself.
Contacts would be independent of the account, I could always see all of them.