TALK

An app that allows you to schedule your calls

Click to see prototype

The Problem - what's wrong with phone calls?

Caller and Receiver have different availabilities:

To make a phone call requires both the caller and the receiver available at the same time. However, people have different availabilities.

Time of call is entirely decided by the caller:

Caller only calls when he/she is available with receiver's availability unknown. Receiver will often receive calls at inconvenient times but the same will not happen to the caller.

SOLUTIONS

SCHEDULING

Set up a time with the person you want to talk to. You can send or receive schedules and all of the talks will appear in the Talks tab.

CAPP CALLS BOTH YOU & CONTACT

The app is not just a reminder. At scheduled time, The app will connect you and your contact at scheduled time. Both you and your contact’s phones will ring.

ASAP

ASAP is a special kind of schedule with an end open end. ASAP doesn’t have a preset time. You send ASAP to a contact. Whenever the contact confirms the ASAP, the talk will be connected.

Click to see prototype

Design Process

Ideation

Identify the Problem

Different Availabilities: To make a phone call requires both the caller and the receiver available at the same time. However, people have different availabilities.

Power Imbalance: Caller only calls when he/she is available with receiver's availability unknown. Receiver will often receive calls at inconvenient times but the same will not happen to the caller.

When a call is made...
Caller Always Available
Receiver Availability Unknown

Propose a solution

Use schedules to manage availability

The most common way to resolve availability conflicts is to make schedules. Calls should be scheduled at a time convenient for both the receiver and the caller.

Caller and receiver co-decide the schedule

Schedules should be mutually agreed on by both the caller and the receiver

Design the Experience

1. Scheduling

To set up a schedule between two users, there are three scenarios:

Life Cycle of a Schedule

Design of A Schedule

Comparison between Calls and Scheduled Calls

Temporal Structures of Old and New Model

2. Automatic Connection: Redefining Calls

What happens at the scheduled time?

Key Difference: One person calls another --> App calls both people

Users need to notified at scheduled time that they have a call. Instead of reminding the user and let the Both users need to be alerted at the scheduled time. We can take one step further and let the app "call" both users at the scheduled time. Therefore no one will actually initiate the "call". The app will notify both users and wait for actions from them. If both users agree to talk, the talk will start.

Two Steps: Remind user + let user make the call --> One Step: App rings and connect users

CAll -> Talk

The idea of "calling" is fundamentally changed by this app. Calling someone suggests one person initiates the call and another person receives. However with this app, no one will initate the call and it is all done by the app.

Therefore, "call" doesn't not capture the nature of this new form of interaction between users. "Calls" will be renamed to "Talks".

Comparison of Call and Talk

Call Talk
Caller can make calls at his/her own convenience without regard to receiver's availability. Receiver can't decide when to receive calls. Both caller and receiver's avaiabilities are taken into account; receiver can either accept or reject a schedule.
Caller and receiver are different. Caller initiates a call; receiver passively accepts a call. Caller and receiver are equal. Since the app will make the "call", no one will "make the call". The distinction between caller and receiver ceases to exist.

3. Introducing ASAP

So far the app does not allow calls/talks without scheduling. There are times when we don't have a preset schedule. And we want to reach another person immediately

ASAP is a feature desinged to solve this problem.

ASAP is a special Talk that has an open-end schedule. It doesn't have a scheduled time. When user A sends ASAP to User B, user B can confirm the ASAP schedule at his/her earliest convenience. The time when User B confirms will become the scheduled time. Thus, whenever the receiver of an ASAP schedule confirms the ASAP, the Talk will be connected

ASAP allows

Flow of Experience

Design the Interface

1. Information Structure

Definition of Terms

2. Send a schedule

Two ways to send a schedule

Two ways to input time

3. Confirms a Schedule

4. Start a Talk

5. High Fidelity Interface

See prototype

Click to see prototype