There was a lack of connection between Placester's clients and Placester as a company. We wanted to strengthen our relationship with our clients and provide them the very first Placester app to help them manage website content.
By creating an app for Placester's resources, it aimed to solve the problem of lack of connection by giving our customers a more transportable way to stay connected to Placester content.
Real estate agents could view content on a dashboard, edit that content, and either save as draft or publish it directly to their website from this application. The enablement of customization gives customers a chance to spin the content more to themselves, creating loyalty and satisfaction.
1. Convenient access
Right when the app loads, the customer can see all the recent and past content Placester has published out on a dashboard feed. As the customer scrolls through this feed, they can see the type of content by the icon and a badge to indicate if the content has been viewed, used, or is new– right at their fingertips.
2. Easy customization for personalized content
Two main types of customization:
3. Control over content
Placester customers will be able to easily control the content they choose to use on their website. The "more" options allow them to hide the content or save the content as a draft to publish later. Besides that, tapping the green CTA "publish" will give them a confirmation module to accept, and done! Published!
I started off listing all the things a realtor/agent may need to do the tasks in the app. I brainstormed features, functions, sketched out some rough flows of publishing content and filtering out content in "settings."
This included other experience paths and actions.
I originally thought of "viewing" and "editing" a piece of content as two steps: if you wanted to edit content, then it would reveal the mad-libs- this wasn't efficient because the user had to go through one more step to view mab-libs.
There were also just too many actions (hide, edit, revert, save the draft, and publish) that I tried to divide out into these two screens.
After getting feedback from my team, I learned that the primary action of "publish" should be the only control in the bottom navigation because it's the most important function- the CTA. Other actions like "hide content, save as draft, and revert," can be secondary options in a top-right menu. Viewing and editing content did not have to be in two steps. Once a user clicks on a piece of content from the index, it should already be in edit mode with mad-libs visible. It takes away one more unnecessary step.
My UX team and I designed different icons to distinguish different types of content from each other in the content index. The user would be able to filter the index by newest, oldest, or content type! This keeps their dashboard clean and only returns the content the user actually wants to see if the way they want to see it!
I applied the same concept of text "mab-libs" to photos: I created a photo adding functionality so the user could add his/her own photos in the content as well. This also gives them some more customization to their blog posts.
All in all, Placester's content app was a new way for agents to carry our content with them, customize that content, and have easy control of how to put it on their websites. This was the final main flow of picking a piece of content, editing the mad-lib, and finally publishing.
I also designed this app for Android for version 1 of the content app. The engineers were learning React Native, we decided to simplify the content app into a feasible, simpler version that can be used on both iOS and Android platforms.
This simplified version just allowed a user to save a piece of content as a draft, go to drafts, and then publish it.
I created this flow diagram at the end of the project to help the engineers visualize the process better.
A look-see into the redesigned version: This was the dashboard, the content detail, the drafts folder, and the publish/remove option.