← All work Oathocracy · iOS app

Handshake agreements with a reputation behind them

Oathocracy is an iOS app for making informal handshake agreements, called oaths, and tracking your reputation for keeping them. The goal was to get business agreements started faster and add a layer of accountability.

Role
UX Designer
Date
February 2015
Client
Oathocracy, through HappyFunCorp
Team
1 visual designer, 1 engineer
Three Oathocracy screens: sign in, a feed of oaths, and an oath with people who joined

Scoping the MVP

Deciding what the first release needed

An oath is a promise with a deadline, optional proof and optional witnesses. People can make them public, revise them over time, and build a reputation from the ones they keep.

I met with the client to prioritize what an MVP needed. I put together a prioritization matrix with use cases and user stories, rated by value and effort, so we could agree on what to build first.

Product priority matrix listing themes, use cases and user stories with priority and effort ratings
A page from the product priority matrix.

Site map

Turning priorities into screens

I used the matrix to build a site map, so the client could see every screen the app would need. The dashboard sits at the center, with profiles, people you follow, invitations, notifications, settings and creating an oath around it.

Oathocracy app site map
App site map

Oath flow

Working out how an oath gets made

I sat down with the client and his backend engineer to map out how sending an oath would work. We sketched it together, and I cleaned it up for the documentation. The flow covers the type of oath, its description, the deadline, whether it's public, and adding promisees, proof and witnesses before it's sent for confirmation.

Oath sending process and logic flow
Oath sending process and logic flow.

Wireframes

Documenting each screen

Once I had a strong understanding of what the app needed, I moved into wireframes. Each one had annotations so the visual designer and engineer knew exactly how it should behave.

Onboarding flow wireframes from load screen to oath invitation
Onboarding, from the load screen to an oath invitation.
Login wireframes with sign in options and terms
Logging in
Creating an oath wireframes with deadline, milestones, people and proof
Creating an oath
Accepting an oath wireframes with witnesses and revision history
Accepting an oath

Visual design

The finished screens

The visual designer built the comps from my wireframes, with a wax seal as the app's mark.

Sign in screen with Facebook, Google and email options
Sign in
Feed of oaths people have made
Oath feed
An oath with people who joined and a completion date
An oath people joined
Concept · not the shipped app

Redesigned for today

How I'd update it with today's mobile patterns

Making an oath in 2015 meant filling out a long form. This concept keeps the same idea, a promise with a deadline, witnesses and proof, and makes it feel as quick as sending a message.

  • Just say the promise. Type it in plain words and AI picks up who it's for and when it's due, which you can confirm or change.
  • Progressive options. Witnesses, proof and visibility sit below as simple rows instead of one long form.
  • Reputation at a glance. A kept rate with kept, open and broken counts makes accountability the center of the profile.
  • Status you can scan. Each oath shows a clear status, the deadline and its witnesses in the feed.
  • Familiar navigation. A segmented feed, a floating create button and a tab bar.
Concept oath feed
Feed
Concept new oath sheet with plain language input
Making an oath
Concept profile with a 94 percent kept rate
Reputation