UX Writing for the Handshake Mobile App

For the final project of my UX Writers Collective certification, I updated the copy and suggested pertinent design revisions for the mock “Handshake” app, a time tracker and payment tool for contractors working with clients.

My objective was to guide users and foster ongoing usage. I clarified the post-signup project setup flow for the 2 user types (contractor and client), and created an onboarding email for first-time users.

Client setup flow: mockup from designer


Client setup flow: my updates and suggestions

Edits to copy and some minor layout changes on all screens.

Note to designer:

Where does the “Back” button take the users? This could be where they “Skip” to go to Projects (home).

Note to designer:

Are users able to select multiple options or only one? If only one, then I’d recommend changing to radio buttons, since checkboxes indicate multi-select.

Notes to designer:

I added a description about what the invite message shows and recommend adding a preview.

If there may be more than 1 contractor in a project, it may need to include more than one email address line. In that case we might change the headline and perhaps include a tooltip or more instruction. In addition, does the plus icon have an action to it (such as adding more email address lines below)?

Note to designer:

I recommend placing an “X” button so they can close this window. Otherwise, they may not know where to tap or what to do next.

Note to designer:

I recommend placing an “X” button so they can close this window. Otherwise, they may not know where to tap or what to do next.


Contractor setup flow: mockup from designer


Contractor setup flow: my updates and suggestions 

Edits to copy and some minor layout changes on all screens.

Notes to designer:

Where does the “Back” button take the users? This could be where they “Skip” to go to Projects (home).

It might be early for users to add proposed hours. If kept, it may need to be optional with instruction that the proposal can be set up later. I’d recommend removing the fourth entry field entirely from this screen since it can be done later.

Note to designer:

This screen should include a description about what what the invite message shows: what happens regarding the proposal now and next (such as, if it can be edited later). Determine proposed hours first, because that will affect the description language.

Note to designer:

I recommend placing an “X” button so they can close this window. Otherwise, they may not know where to tap or what to do next.


First time onboarding email version updates

Version 1

SUBJECT LINE

Thanks for choosing Handshake to smoothly manage progress tracking and invoicing.

BODY

Hi {FirstName},

You’ve successfully signed up for your Handshake account. Next, log in to the app to get started on your first project! And if you’re ready, connect your payment method or invite others to the project.

Learn more about using Handshake at support.handshake.com. We’re available and eager to help – open a help ticket if you have any questions.

CTA

GET STARTED

Version 2

SUBJECT LINE

Get started with Handshake to track progress and invoice clients for your contract projects

BODY

Hi {FirstName},

You’ve successfully signed up for your Handshake account. Thanks for choosing to join us! You can log in now to get started.

Take a look at our how-to’s and tips at support.handshake.com. Also, we’re available and eager to help if you get stuck! Open a help ticket if you have any questions.

CTA

GET STARTED

I reframed the message, after considering the basic expectations of a user at this very early stage. The subject line reminds them what they’ll be able to do with Handshake, but the body steps back. They may be trying out different software or only in early talks with a client/contractor. Rather than asking them to do something they’re not ready for, like create a project, I point them to log in and find support. 


“It’s one of the best projects ever submitted – you caught every design flaw and had great insights and suggestions on how to fix them all, plus pointing out even more helpful functionality that the app lacks.”

Bobbie Wood, Founder of UX Writers Collective