Case study / Building heykup

Small details.
A stronger product.

A useful idea is only the start. Here’s how real screens, real edge cases, and a closer look shaped heykup.

Inside the build
THE BUILD LOOP
01Define the moment.
02Make it work.
03Try it in real life.
04Make it feel right.
THE PRODUCTHybrid team coordination
THE PLATFORMA mobile-first PWA
THE APPROACHHuman-led, AI-assisted

What the first version taught us

Polish is part
of the product.

A few of the problems that shaped the product as it evolved.

THE PHONE FRAME

A screen should fit
the phone it’s on.

Installed iPhone apps exposed safe-area and bottom-navigation issues. The shell was refined so content and controls follow the available viewport.

Mobile layout & navigation
THE SHARED PICTURE

Loading isn’t
the same as zero.

Attendance views need to distinguish data that is still loading from an actual empty day. Clear states make the team picture easier to interpret.

Attendance & data states
THE RETURN VISIT

Pick up where
you left off.

Returning to the app means restoring team context, refreshing information, and keeping navigation predictable. Recovery became part of the daily experience.

Session & workspace recovery

The decisions behind the experience

Built with intention.

01Put the phone first.

A PWA keeps the browser-to-home-screen journey short. The web introduces the product; the mobile app is where the team uses it.

02Keep one shared picture.

Daily status, weekly plans, and attendance history serve the same purpose: helping a team understand its time together.

03Make room for team boundaries.

Team membership, admin permissions, and data access rules are part of the product’s foundations.

04Check as you build.

Build checks, browser tests, and rule tests sit alongside implementation. Preview and production environments keep validation separate from release.

Making everyday tasks clearer

Less to interpret.
More confidence in each action.

The product’s design decisions follow the work people came to do.

Feedback beside the change

Office plans save as each day is selected. Saving, saved, and retry states make the result clear without a separate Save button.

A journey in clear stages

Ride offers group the journey, seats and vehicle, and final review. Members can go back to edit before publishing.

Trust through clear limits

Rides requires explicit agreement to member responsibilities. Saved locations are private, phone sharing is optional, and no driver verification is implied.

See what we built

The story is better
with the product in hand.

Explore the experience, then bring your team into the picture.