Proxy Vertex Grid Kuala Lumpur

Reviews & stories

What product teams said after the readout

These notes refer to specific engagements — measurement studies, observation sittings, checkpoint workshops, and remeasurement — rather than generic praise for “analytics.”

“They timed every permission ask against when people first saw a useful station list. We had been debating copy; the report showed the order was the real problem.”

Siti Rahim Product lead, regional transit app · Onboarding Flow Measurement Study

“The observation memo was blunt about our account wall after “save to list.” I wanted softer wording in the readout, but the timestamps were hard to argue with.”

Daniel Khoo Growth manager, shopping app · First-Session Observation Sitting

“Checkpoint mapping forced us to stop calling every open an activation. First value for us is a verified balance view, not the welcome animation.”

Mei Ling Ong UX researcher, retail banking app · Activation Checkpoint Mapping

“Remeasurement after we delayed notifications showed the first-session path clearing earlier. The comparison note named the two screens that still stalled people.”

Arun Patel Mobile product owner, lifestyle app · Post-Change Remeasurement

“Their permission review caught a contacts ask that only mattered for invite friends — a feature nobody reaches in minute one.”

Farah Ismail Associate PM, social consumer app · Permission Prompt and Account-Creation Review

“We booked them because our funnel looked healthy until day seven retention collapsed. The first-session report explained the early compromise we were making for sign-up volume.”

Hannah Brooks Head of product, travel marketplace app · Onboarding Flow Measurement Study

Longer accounts

Two measurement stories

Onboarding Flow Measurement Study

Transit app: location ask before the first map

A regional transit consumer app with riders in Kuala Lumpur and Johor Bahru

The team believed splash duration caused first-session loss. Our three-week measurement study of the Android path showed something else: the precise-location dialog opened on a nearly empty canvas, before any nearby stations rendered.

Of the eleven first installs we observed in the window, six denied the dialog. Four of those six never recovered a usable map because the app offered no browse-by-station fallback. The written report sequenced splash, soft-ask, system dialog, empty map, and exit.

After the readout, the team shipped a station list that loads on city defaults, then asks for precise location. A later remeasurement is planned; the first change already removed the blank-canvas ask.

First-Session Observation Sitting

Shopping app: account wall after the first favourite

A fashion retail app selling to Malaysian shoppers

During a one-day observation sitting we watched ten first installs. People browsed happily as guests until they tapped a heart icon. The account wall then demanded email, phone, and a password before restoring the product page.

Three people created accounts. Four abandoned. Three tried guest checkout later and hit the same wall. The memo did not claim a conversion rate miracle; it described the interruption in the first ten minutes with timestamps.

Daniel’s team kept the account requirement for favourites but restored the product page state after sign-in and removed the password field in favour of OTP. That narrower change came directly from the sitting notes.

Bring your own first-session disagreement

If your team already argues about splash, OTP, or permissions, we can measure which story the installs support.

Enquire