Barbara K. Prokop
Product Designer

JL header large
 

 

 
CASE STUDY 

JointLift

A focused space for two collaborators who need to keep one shared project moving.

I designed JointLift in Figma, then built a working iOS MVP through an AI assisted process and took Build 2 through external TestFlight approval.

 

 

ROLE

Product design, interaction design and AI assisted build

 

TIMELINE

2026

 

TOOLS

Figma, React Native, Expo, Supabase, Resend, Claude Code, Codex and ChatGPT

 

STATUS

Approved for external TestFlight testing

Problem

Starting a task alone can be harder than doing it. WhatsApp helped because someone else was there, but it was also where family, work, groups and everything else lived.

User

Two collaborators with different responsibilities who need to keep a shared project moving without turning it into a management system.

Role

I defined the product, designed the interface and built the working app with AI tools.

Solution

One thread per project. Each person owns their own task and shares only the updates that keep the other person moving.

Current state

Build 2 is approved for external TestFlight testing. The key flow works. I am now testing whether it helps people begin.

2

Two people. Not a group and not an audience.

1

One shared ending. Both people have to be done.

Build 2

Approved for external TestFlight testing.

Constraints and Frictions

Constraints
Problem

WhatsApp did the job at first, but it also carried the rest of our lives. It was hard to make a small act of encouragement feel separate from family, work, groups and everything else waiting there.

Solution

JointLift gives two people a place for one thing. Each person has their own task, but both can see that the other person is moving. Nothing more is needed for the idea to work.

Context 

Two ordinary exchanges gave me the idea.

A friend was struggling to clean his apartment and I had some organising of my own to do. We started exchanging updates and encouraging each other over WhatsApp. It helped. What felt wrong was doing a focused task in the same app we used for family, work, groups and everything else.
 
At the same time, I was helping a fifteen year old build his first portfolio while rebuilding mine. We sent screenshots and ideas back and forth. Neither of us was working on the other person’s project, but seeing movement on the other side kept us going.
 
That was the part I wanted to keep. Someone else doing their own thing beside you. Not a productivity system and not a social feed. Just enough connection to get moving.

 

iPhone 16 Pro

One invitation, two tasks, one shared ending.

The flow had to be simple enough to explain in one breath. Create an account. Start a JointLift. Name your task. Invite one person. Then get on with it.

Both people can send messages, images and small updates as they work. Either person can be done first. The shared ending appears only when both people are done.

JL diagram
JL layout

It worked, but I still didn’t look forward to using it.

I first tried to build JointLift through words alone. That was not enough. I made the first screens in Figma and used them to guide the build. Halfway through, I realised the design was not mine, so I changed direction.

The version I kept is quieter and bolder. It gives the app a focused, deliberate feel that I wanted to open. Black and white hold the interface together. Bright orange appears only when something needs attention or action.

JL oldversesnew

Where it got complicated.

JL
Screenshot 2026 07 19 at 19.00.05

Building it exposed the real states.

JointLift is a working iOS MVP. A person can create an account, start a JointLift, invite someone, share updates and reach a shared ending. Build 2 is approved for external TestFlight testing.

I am now testing whether this small amount of connection is enough to help people begin.

Sometimes seeing someone else move their part forward is enough to get you moving.

I did not need to know everything before I started.

Keep moving before you understand everything

I needed to begin, find the next problem and keep going. Not knowing how to do something did not mean I could not work it out.

Stay calm in the messy part

The difficult part was rarely one problem. It was not knowing how many problems were still waiting. Keeping calm became part of the work.

Trust it. Then verify it.

AI became useful once I could give it a clear screen, state and constraint. I checked each result against the working app and changed it when it did not feel right.

 

I built it. Now I have to learn where it helps.

Next I want to see whether small updates can help two collaborators on the same project begin, keep moving and finish their part.

Test it with another person

Does another person’s progress create momentum?

Make the invitation feel simple

The complexity behind the invitation should not become the user’s problem.

Build the awkward states

Expired invitations, failed messages and missing images come next.

Leave the extras alone for now

The basic exchange needs to prove itself first.