screenview

Petal Cloud Storage

Roles

  • User Research
  • UX/UI Design
  • Branding
  • Visual Design
  • User Testing

Problem

Fellow stakeholders and investors are interested in creating a cloud storage platform that differs from other competitors in the market.

Things to consider:

  • How can we differentiate this new brand from already well-known competitors?
  • What are the main goals of this platform?

Solution

My solution to this brief is Petal, a cloud organizational web and mobile platform focused on user-friendliness, organization, and accessibility. This platform aims to aid its users by providing access to their data through multiple devices. Petal also stores user files and allows them to stay organized, and share and save links with other users.

Research

To fully understand the current cloud storage market and how people utilize these platforms, I created a user survey catered to the client briefing. I sent this survey to the general public to gain some insight into a new cloud service that could potentially fill in the missing pieces. From the survey results, I noticed a few key takeaways:

Competitive Analysis

I performed a competitive analysis of a diverse range of cloud storage platforms that each brought something different to the cloud storage market. I analyzed Dropbox and Google Drive because they are the market leaders in this industry and the most recognizable in my survey. I also analyzed Pinterest for its different approach of social media sharing to cloud storage.

dropbox image google image pinterest image

With these competitors in mind, a new potential platform can provide a service with better security for the user so their files aren't compromised. For example: if a user uploads a file into the cloud, the platform can provide an internal virus scanner that scans any uploaded file. Additionally, this new platform would provide better updates that would eliminate system crashes and provide weekly backup options to users so they can stay on top of backing up their files.

Full SWOT

User Personas

I interviewed two people in person from my survey to talk in-depth about their experiences with cloud storage platforms. From these interviews, I realized that even though their backgrounds were different, they both shared the same frustrations of expensive monthly plans and lack of security.

image of Gene image of Sara
Full User Personas

User Stories

Equipped with an understanding of the client's needs and information provided to me by the user survey and user personas, I created a list of features that the participants deemed the most important to help establish user stories. I broke these stories down by priority: high (ex: creating content), medium (ex: scan my downloaded files for viruses), and low (ex: delete files).

Role Task Importance
New user Create a new account High
New user Sign up for a personal account vs Business High
Existing user Copy and share links to documents High
Existing user Creating content like notes, documents High
Existing user Backup files from my old device to my cloud account High
New user See how much free space I have left Medium
Existing user Provide 2-step verification when I log in to my account for security Medium
Existing user Share my files with someone Medium
Existing user Scan my uploaded files for viruses Medium
Existing user Saving content I find on the web Medium
Existing user Submit a crash report if my app crashes Medium
Existing user Upgrade my storage space Medium
Existing user Organizing content using categories, tags, groups, etc. Medium
Existing user Connecting with other users for real-time collaboration in notes or documents Medium
Existing user Provide access/permission to see other people's files Low
Existing user Search for files Low
Existing user Customize my account Low
Existing user Add co-workers / Family to collaborate with Low
Existing user Delete/Archive Files Low

User Flow

Next, I started sketching out possible user flows to accomplish the goals of my target audience, based on user stories and user personas. I observed the ways Dropbox, Google Drive, and Pinterest mapped common flows, such as signing in, onboarding, and upgrading. I created my user flows based on what seemed most straightforward and user-friendly.

image of user flow

Implementing & Early Testing

With my user research, stories, and personas, I began to brainstorm and sketch out ideas for the platform with wireframes. I started testing these out right away on people in real-life scenarios.

image of first sketch image of second sketch

This first round of usability tests highlighted some design inconsistencies in my primary layouts, as well as issues with upgrading the user's storage plan. For my web landing page, a user stated that my grey input boxes looked similar to the primary call-to-action buttons. Additionally, displaying two separate trash can icons proved to be confusing for another user. With my web dashboard page, a user stated that the folder icons looked like they were all open and were hard to interpret.

image of wireframe 1 image of wireframe 2

For my mobile application, I had similar feedback regarding my folder icons being hard to interpret. Another user also stated that my upgrade/pricing table did not have a way to determine which plan was selected, and suggested that I add some sort of radio button or call-to-action button to make this clear.

See Full Wireframes Image of mobile wireframe

Overall, the feedback revealed that the functionality was there, but needed just a bit more work on the design element.

Brand Development

For the Petal Brand, I developed a logo design, style guide, and some illustrations for the overall platform. All of these elements can be put together to represent Petal’s growth as a brand and product.

image of logo in black and white image of my different typefaces

When sketching out the logo, I had initially wanted to give it a cloud name (like Cirrus or Cumulus) but realized that this idea was already done and very predictable. My second idea was to go with a name like “Vault” because of the association with keeping belongings safe and secure, but I ultimately felt that this idea was not what I wanted to convey to my user. Lastly, I thought of "Petal". I gravitated towards this idea because of the symbolism that it provides: when someone picks a petal from a flower, they can carry that with them wherever they go, or preserve it in a book or diary. I liked that this idea can apply to a cloud service as well - when someone wants to access a file on the go, they can do so on their phone or tablet. Additionally, I loved that a flower/petal represents growth, whether it be in a company or a person. I want this tool to help the user achieve that growth, no matter what shape or form.

style color

For my overall style guide, I initially went with earth tones to match the plant theme of my brand. I mainly wanted to stand out by staying away from what was commonly used with the current competitor brands. Regarding the primary font set used in my style guide, I wanted to use clean fonts to contrast with my earthy color scheme. I tested out a few different color schemes with Petal's logo:

image of different color variations of logo

Execution & Testing

Once I adjusted my wireframes based on my first round of usability testing, implemented my style guide, and made my platform more realistic to the user, it was time to perform my second round of usability testing. For my landing page prototype, I was able to improve the center section, made the boxes more square, and added text to the left to prompt the user to input their information. Additionally, I added a navigation bar to the bottom of the page with links to About, Why Join, Contact Us and Connect.

hifidelity1 hifidelity2

In my dashboard prototype, I replaced the folder icons with open and closed folder icons that were more distinguishable for the user, and removed the second trash icon.

View Web Prototype

For my mobile prototype, I applied the same changes as I did with my web application, but also played around with the coloring to see which way turned out most effective to the user.

View Mobile Prototype image of different color variations of my mobile hifi

Unfortunately, each color scheme variation still made it very hard for the user to see the font and icons. As previously stated, my feedback highlighted my font set looked familiar to one another and my color scheme would make it hard for the user to see icons and buttons.

upgraded version of my hifi upgrade2

After further iterations and doing further research, I implemented a new, trendier color scheme that was not only more fun but also more appealing and inviting to the user. I thought this color scheme would be a little more calming and engaging as well. I also provided a new font set that consists of Baloo and Montserrat; these fit perfectly with the overall color scheme and layout of the web and mobile application. On the landing page, I added an image to the left, moved the center login to the right side of the page, added social media icons to the bottom of the navigation page, and improved the logo color scheme.

upgraded version of my homepage upgraded version of my dashboard

The same will apply to my mobile application as well. I improved the landing page by adding an image and improving the color scheme and font.

upgraded version of my mobile homepage

Conclusion

Watching Petal blossom from idea to prototype was a comprehensive process that provided many lessons for future iterations and projects. A few of these lessons were:



With that being said, I would like to thank you for taking the time to view my case study, and hope you have a wonderful day.