⸺
Overview
At the beginning of the year, Amity introduced Amity Social Cloud, an SDK product that supports social and communication modules. Fast forward to today, a number of new features have been implemented, upgraded and our users are finding it hard to manage available features with the current admin console.
Redesigning the console aimed to shape a better experience and structure a new design framework to serve future direction.
Timeline:March 2020
Role:Research
User Experience
Prototyping
Visual Design
⸺Problem
Problem
Opportunity
How could we improve experience that support new persona’s use cases, but still maintain the existing user’s expectation?
⸺
Goal
Create a seamless and consistent experience between the client side and the admin console.
Be transparent and informative
Provide all necessary information and a description of how the product works. Communicate clearly with users along the way until they accomplish the task.
Make sure new design updates are aligned with company’ new visual identity, but still doable to the development timeline.
Reusable
Every new design component generated has to be reusable across
the entire platform and use minimum development effort.
Designing new architecture with CSM structure
According to the research, I found out that Social Cloud products and CMS (Content Management System) share a common data type, such as content pages, posts, messages, media, comments, and etc.
Rather than drilling information like a pipeline, CMS has a very effective way to handle this use case by giving all data types a dedicated me. It allows admin users to manage a large amount of information at the same time.
Rather than drilling information like a pipeline, CMS has a very effective way to handle this use case by giving all data types a dedicated me. It allows admin users to manage a large amount of information at the same time.
Final design
Navigation
Console navigation can be customisable depending on the functionality of each product.
The best practice for Platform Solution is a double panel which provides a number of spaces to categorise each feature in detail without confusing users.
The best practice for Platform Solution is a double panel which provides a number of spaces to categorise each feature in detail without confusing users.
Dashboard template
To fasten the design and development process, I categorised content area, based on available components, into three types — Listing, Group dashboard, and Settings.
Old designs
Revamp designs
Key takeaways
- Always design for a scalable product. Technology drives fast designers should think ahead. The design should be able to handle multiple possibilities from the upcoming plan.
- Wording and writing are very critical to create a clear and understandable experience.
- Understanding engineering limitations and context drive the process faster with the team. Take time to understand all constraints with the team and find a solution together.