Back

Ditto

Squirrels

Research & Product Design

Native & Web Applications

Ditto is a SaaS web application for conference rooms and classrooms. Ditto enables anyone connected to an organization's wifi network to share their screen wirelessly to an AppleTV or Chromecast device via a macOS or Windows application.

🏔️ The Objective

The user enters room code to get a download link for a Mac or Windows app.

User downloads a one-time app. They can push their entire screen or a specific app to a designated receiver.

Each service reminder had to be applied one by one, on each vehicle, making it difficult standardize schedules across fleets with similar vehicles.

🕹️ Challenges & Constraints

Ditto would have multiple users with different roles and permissions.

The user interface would need to address the numerous technical layers that come with wireless mirroring of various devices.

The native applications needed to be easy to use for anyone wanting to share during a meeting, regardless of technical level or knowledge of screen sharing protocols.

👥 The Personas

Account Administrator - Responsible for managing rooms, devices, and billing details.

End-User - The person who is trying to share their screen to the front of the room.

Planning

By involving product managers and engineering from the start, I began to formulate a basic understanding of technical limitations and business goals. Using these flows in the discovery process allowed me to understand some of the decision making for each user.

💻 The Native App

A typical end-user, someone who might be an outsider or anyone needing to share their screen during a meeting, would not need a dedicated account with Ditto. The room code, set by the admin, would be displayed on the receiver as part of Ditto's digital signage, which would let any user download the native sharing app when entered on the connect page.

🌀 The Admin Portal

The account portal is the administrative engine that manages everything in the organization. I wanted to make sure that the rooms' concept remained simple but dealt with the complexity of managing several new devices as it added new challenges with the interface.

Ditto also introduced new receiver types with Mac, Windows & tvOS. The receivers would handle custom branding, multiple device sharing, and mass deployment.

Managing rooms and devices are a different experience but are closely related to the overall design. In the beginning, we sketched out some concepts where Ditto rooms and devices existed on the same plane. We ended up giving the two space to breathe as our customers were concerned with the potential of devices moving around to different conference rooms from time to time.

This design allowed our customers to freely manage an organization's devices (eventually moving towards MDM) and quickly add or remove a device from a Ditto room. Customers' paid for the room and not by the device, which gave them the freedom to move devices, if needed, without affecting their billing profile.

As the lead product designer, I was in charge of designing an experience that addressed both a typical user whose environment was primarily a meeting space and an administrative user in charge of managing those meeting spaces.

🤝

Matthew Elsey

Project Manager

Jason Price

Engineer

Back

© 2023 - Keep it stupid simple

Back

Ditto

Squirrels

Research & Product Design

Native & Web Applications

Ditto is a SaaS web application for conference rooms and classrooms. Ditto enables anyone connected to an organization's wifi network to share their screen wirelessly to an AppleTV or Chromecast device via a macOS or Windows application.

🏔️ The Objective

The user enters room code to get a download link for a Mac or Windows app.

User downloads a one-time app. They can push their entire screen or a specific app to a designated receiver.

Each service reminder had to be applied one by one, on each vehicle, making it difficult standardize schedules across fleets with similar vehicles.

🕹️ Challenges & Constraints

Ditto would have multiple users with different roles and permissions.

The user interface would need to address the numerous technical layers that come with wireless mirroring of various devices.

The native applications needed to be easy to use for anyone wanting to share during a meeting, regardless of technical level or knowledge of screen sharing protocols.

👥 The Personas

Account Administrator - Responsible for managing rooms, devices, and billing details.

End-User - The person who is trying to share their screen to the front of the room.

Planning

By involving product managers and engineering from the start, I began to formulate a basic understanding of technical limitations and business goals. Using these flows in the discovery process allowed me to understand some of the decision making for each user.

💻 The Native App

A typical end-user, someone who might be an outsider or anyone needing to share their screen during a meeting, would not need a dedicated account with Ditto. The room code, set by the admin, would be displayed on the receiver as part of Ditto's digital signage, which would let any user download the native sharing app when entered on the connect page.

🌀 The Admin Portal

The account portal is the administrative engine that manages everything in the organization. I wanted to make sure that the rooms' concept remained simple but dealt with the complexity of managing several new devices as it added new challenges with the interface.

Ditto also introduced new receiver types with Mac, Windows & tvOS. The receivers would handle custom branding, multiple device sharing, and mass deployment.

Managing rooms and devices are a different experience but are closely related to the overall design. In the beginning, we sketched out some concepts where Ditto rooms and devices existed on the same plane. We ended up giving the two space to breathe as our customers were concerned with the potential of devices moving around to different conference rooms from time to time.

This design allowed our customers to freely manage an organization's devices (eventually moving towards MDM) and quickly add or remove a device from a Ditto room. Customers' paid for the room and not by the device, which gave them the freedom to move devices, if needed, without affecting their billing profile.

As the lead product designer, I was in charge of designing an experience that addressed both a typical user whose environment was primarily a meeting space and an administrative user in charge of managing those meeting spaces.

🤝

Matthew Elsey

Project Manager

Jason Price

Engineer

Back

© 2023 - Keep it stupid simple

Back

Ditto

Squirrels

Research & Product Design

Native & Web Applications

Ditto is a SaaS web application for conference rooms and classrooms. Ditto enables anyone connected to an organization's wifi network to share their screen wirelessly to an AppleTV or Chromecast device via a macOS or Windows application.

🏔️ The Objective

The user enters room code to get a download link for a Mac or Windows app.

User downloads a one-time app. They can push their entire screen or a specific app to a designated receiver.

Each service reminder had to be applied one by one, on each vehicle, making it difficult standardize schedules across fleets with similar vehicles.

🕹️ Challenges & Constraints

Ditto would have multiple users with different roles and permissions.

The user interface would need to address the numerous technical layers that come with wireless mirroring of various devices.

The native applications needed to be easy to use for anyone wanting to share during a meeting, regardless of technical level or knowledge of screen sharing protocols.

👥 The Personas

Account Administrator - Responsible for managing rooms, devices, and billing details.

End-User - The person who is trying to share their screen to the front of the room.

Planning

By involving product managers and engineering from the start, I began to formulate a basic understanding of technical limitations and business goals. Using these flows in the discovery process allowed me to understand some of the decision making for each user.

💻 The Native App

A typical end-user, someone who might be an outsider or anyone needing to share their screen during a meeting, would not need a dedicated account with Ditto. The room code, set by the admin, would be displayed on the receiver as part of Ditto's digital signage, which would let any user download the native sharing app when entered on the connect page.

🌀 The Admin Portal

The account portal is the administrative engine that manages everything in the organization. I wanted to make sure that the rooms' concept remained simple but dealt with the complexity of managing several new devices as it added new challenges with the interface.

Ditto also introduced new receiver types with Mac, Windows & tvOS. The receivers would handle custom branding, multiple device sharing, and mass deployment.

Managing rooms and devices are a different experience but are closely related to the overall design. In the beginning, we sketched out some concepts where Ditto rooms and devices existed on the same plane. We ended up giving the two space to breathe as our customers were concerned with the potential of devices moving around to different conference rooms from time to time.

This design allowed our customers to freely manage an organization's devices (eventually moving towards MDM) and quickly add or remove a device from a Ditto room. Customers' paid for the room and not by the device, which gave them the freedom to move devices, if needed, without affecting their billing profile.

As the lead product designer, I was in charge of designing an experience that addressed both a typical user whose environment was primarily a meeting space and an administrative user in charge of managing those meeting spaces.

🤝

Matthew Elsey

Project Manager

Jason Price

Engineer

Back

© 2023 - Keep it stupid simple