I have to say this project is one of the biggest challenge for me. Today, in Veo One, there is separate account page and client page, user can add client to client page and use that page as household page.
Stage one: We need to build Household page
Story starts from talking about building household page. But that means we have account page, client page and house page which will be very confused. As my understanding, client page is a group of accounts and same as household page. Finally we decide to combine then together.
Stage Two: Let's try Mobile First
Veo One is mobile last platform. We build everything for large screen, and later either go back fix all the bugs for mobile or build something very basic. Because I am working on combining account, client and household, I ask myself that why not trying "Mobile First"?
Image 1 shows how is client record page like in current product. You can see there are some added account under the primary client name, so this page can be used as a household page.
There are many tabs on the top of the page, most of them are for vendors. User can manage their data from Veo One platform without launching their vendors.
Before I start my work, my first question is what do we really need for mobile view?
Section for Positions, Balances and History are the most frequently visiting area. In legacy Veo One, those sections are in a separate page for avoiding loading problem. But if we only show limit data in over view page, there won't be loading problem.
By clicking each account list in account lists, user can go to check individual account page. Account page is existed page in Veo One which includes "Account Information", "Client Info", "Balances", "Positions" and "Transaction History".
I also add some new feature for manage account easily, they are "Show/Hide this account", "Contact this client", "Remove this account from this group", "Move to ..." and "Add notes".
"Filter accounts" is a very handy tool for household and client page. By filtering different accounts, user can check different data. User can filter accounts in the over view page, also they can hide (filter away) account in individual account page.
For example, advisor X needs to check John Smith's portfolio page, but he doesn't want to show John Smith's 401k account in performance and assets allocation. So he can easily hide that account, then most of the data will get update.