maggie manville

2024-25

Optavise App

Role: ID Card Experience; Lead Designer Design System

screens created
screens created
screens created

Give users quick access to benefits

Optavise was a SaaS business, offering companies a variety of advocacy and benefit informational services that they could then offer to their employees.

The mobile app was meant to allow users to get a quick overview of their benefits information.

notes on design

Developer handoff material

Legacy Infrastructure Problem

The app itself went through many iterations including whether it would be a native mobile app or a mobile browser app. The tricky problem was that the infrastructure of the benefit information and advocacy were at odds. Which resulted in some backend hurdles that ultimately, put the project on hold.

notes on design

Mobile screens for different edge cases

Informed future delivered product

While the native app was put on hold, the research heavily informed the development of a new product called, ‘Clear.’

images showing mockups of insurance product created
screens created
screens created

Native app became responsive site

While at the time it felt frustrating, the work that we did on the app laid the foundation for what would become the responsive site. The decision was appropriate for what the product’s function would be offering as it overlapped with another product that we already offered. It had become a “let’s have an app” just to “have an app.”

maggie manville

2024-25

Optavise App

Role: ID Card Experience; Lead Designer Design System

screens created
home screen
screens created

Give users quick access to benefits

Optavise was a SaaS business, offering companies a variety of advocacy and benefit informational services that they could then offer to their employees.

The mobile app was meant to allow users to get a quick overview of their benefits information.

notes on design

Developer handoff material

Legacy Infrastructure Problem

The app itself went through many iterations including whether it would be a native mobile app or a mobile browser app. The tricky problem was that the infrastructure of the benefit information and advocacy were at odds. Which resulted in some backend hurdles that ultimately, put the project on hold.

notes on design

Mobile screens for different edge cases

Informed future delivered product

While the native app was put on hold, the research heavily informed the development of a new product called, ‘Clear.’

images showing mockups of insurance product created
screens created
screens created
screens created

Native app became responsive site

While at the time it felt frustrating, the work that we did on the app laid the foundation for what would become the responsive site. The decision was appropriate for what the product’s function would be offering as it overlapped with another product that we already offered. It had become a “let’s have an app” just to “have an app.”

maggie manville

2024-25

Optavise App

Role: ID Card Experience; Lead Designer Design System

screens created
screens created
screens created

Give users quick access to benefits

Optavise was a SaaS business, offering companies a variety of advocacy and benefit informational services that they could then offer to their employees.

The mobile app was meant to allow users to get a quick overview of their benefits information.

notes on design

Developer handoff material

Legacy Infrastructure Problem

The app itself went through many iterations including whether it would be a native mobile app or a mobile browser app. The tricky problem was that the infrastructure of the benefit information and advocacy were at odds. Which resulted in some backend hurdles that ultimately, put the project on hold.

notes on design

Mobile screens for different edge cases

Informed future delivered product

While the native app was put on hold, the research heavily informed the development of a new product called, ‘Clear.’

images showing mockups of insurance product created
create-case screen
detail screens
detail screens

Native app became responsive site

While at the time it felt frustrating, the work that we did on the app laid the foundation for what would become the responsive site. The decision was appropriate for what the product’s function would be offering as it overlapped with another product that we already offered. It had become a “let’s have an app” just to “have an app.”