FluidOS Calendar

A native calendar application to track meetings & events

Overview

The Fluid OS Calendar is one of 12 conceptual applications my team and I designed for a foldable phone using the Fluid OS design system. The calendar application is a native application that allows users to manage their day-to-day schedules. After my team member and I designed the phone view, I optimized the watch experience.

Duration

Nov - Dec 2021
(3 weeks)

My Role

UX Designer
Mobile Designer

Team

Ifrah
Abbie

Tools

Figma
Notion

Objective

How can we design watch and phone views to ensure events are accessible?

The Fluid device is a foldable phone that can switch from watch to phone view. When in watch view there is a third of the screen space making it crucial to have just the necessary items.

Solution

FluidOS Calendar : Highlights

Abbie and I focused on designing a calendar application using the component and styling of FluidOS. The application is accessible in both the fluid phone and watch views.

Highlights

List View

The list view is the default view of the calendar application. The phone displays a monthly overview along with a scrollable list of upcoming events. The watch version only displays a list of upcoming dates.

Highlights

Detailed View

​​​​​​​Once the user taps on the event, they are taken to the detail screen which shows the details of the event such as the end times, location, and notes.

Project Timeline

3 week sprint

The calendar app was designed during our final sprint for Fluid OS

LowFi wireframes + Iterations

Major improvements to prototype

improvement #1

Designing for legibility

We received feedback from our professor that the events were too tightly packed. We decided to increase font size and padding between events.

improvement #2

Designing for accessibility

I chose to add the gray background bubbles to create larger and easy-to-follow touch points.

Final Screens

The final product

Reflection

Key Takeaways

Differenciate the UX

There needs to be a difference between the experience of using the phone view v.s. the watch. I constantly found myself coming across this question "Why would the user want to use the watch view?". The user should feel the differences and respective benefits between the two views.

Smaller screens = sacred space

The watch screens can't be designed exactly like the phone version because it is only a third of the space. There need to be certain affordances to convey the necessary information, attention to touch points, sizing, and ensuring the screen isn't overcrowded.

Thanks for reading!