1
0 Comments

Day 30: I did not ship the exit survey on mobile.

Day 30 of building MeetDone.

One decision I made today:

I did not ship the exit-feedback survey on mobile.

At first that felt a bit wrong.

"Same feature everywhere" sounds clean.

It sounds complete.

It sounds like the disciplined thing to do.

I think it would have been the lazy version.

Because exit intent on desktop and mobile is not the same thing.

On desktop, the signal is clearer:

- mouse leaves the tab

- the session feels like it is ending

- there is space for the question

On mobile, it gets messy fast:

- app switching looks like exit

- scroll behavior is noisier

- a popup feels heavier

If I copy the same pattern across both, I am probably not collecting better feedback.

I am just creating more friction in the worse context.

So for now the survey is desktop only.

That means less coverage.

I think it also means better fit.

This is one of those product choices that keeps coming up:

do I want consistency,

or do I want the feature to make sense where it lives?

I am starting to think a lot of early products make the wrong call here.

We chase parity because unevenness looks incomplete.

But sometimes shipping it everywhere is what actually makes the feature worse.

The rule I am using more now is:

do not copy the mechanic.

Copy the intent.

If the intent is good feedback with low friction, the implementation does not have to look identical on every device.

What would you choose more often:

ship everywhere for consistency, or only where the UX actually works?

posted toAvatar for product MeetDone
MeetDone