Stories
Evidence from rooms where a notebook was late.
These comments name a specific study and a specific behaviour. They are not scores. One of them includes a timing complaint we still agree with.
They asked our writers to open the same notebook on the phone and then on the laptop, and they timed the gap without making a show of it. We had been arguing about retry logic; the sessions showed people photographing the note and leaving the app. That is a different problem.
Nadia Hassan, Product lead, family notes app, Kuala Lumpur — Cloud Sync Usage Study
The language review was uncomfortably specific. “All changes saved” was the line I was proud of. Two participants read it as a promise about the other device, then got angry when the laptop was behind. I would have liked the memo a few days earlier — we had already translated the old strings into Malay.
Eugene Loh, Independent developer, Ipoh — Onboarding and sync language review
We only booked conflict observation because a lecturer kept losing seminar questions from a shared notebook. Cloud Pulse Point sat through four messy evenings and listed the order people tap: keep mine, keep theirs, copy both into a new note, then WhatsApp the paragraph to themselves. We still have the WhatsApp habit. At least we know why.
Dr. Siti Mariam, Course notes feature, public university in Negeri Sembilan — Conflict and merge observation
The release brief after 1.9 was shorter than I expected, which I mean as praise. It named three notebooks people had stopped sharing and one they had started treating as a dump for photos that never finished uploading. No theatre.
Arun Nair, Small journal-app team, Penang — Release-cycle usage brief
Extended story
The journal app whose writers kept a paper book by the bed.
A small journal app in Penang asked us for a usage study after reviews mentioned “notes missing in the morning.” The team believed the overnight pass was reliable. The writers we sat with believed the opposite, and had already arranged a workaround: a paper notebook on the nightstand, filled before sleep, photographed only if the morning laptop copy looked complete.
Over four weeks we watched eight people open the same journal on phone and laptop. Two never opened the laptop at all; they judged the phone copy by whether yesterday’s last line was still there after a restart. Three photographed the screen when a photo attachment stayed grey. One person, a nurse on night shift, wrote the same paragraph in the app and on paper every time, because a single lost condolence draft had been enough.
The report did not claim a percentage of “successful syncs.” It described the paper book, the grey photos, and the restart check. The team used that order to decide what to change first. They later booked a release-cycle brief after 1.9, which is the short note Arun Nair left on this page.
If your writers already have a paper twin, say so when you write to us. It changes who we ask to recruit.
Second story
Seminar questions that existed twice, then not at all.
A public university in Negeri Sembilan had a notes feature inside a course product. Lecturers shared a notebook of seminar questions. Two people would edit on the same afternoon; the later save sometimes erased a question that had been spoken in class and never stored anywhere else.
Conflict observation did not invent a merge. It recorded the order lecturers already used: keep the longer version, paste a remembered question into WhatsApp, then abandon the shared notebook until the next semester. Dr. Siti Mariam’s comment on this page is the short version. The longer version is that the feature still exists, and the WhatsApp thread is still the real notebook for two of the four people we sat with.
We do not present that as a success. We present it as a record. Teams who want a different record can arrange observation of their own shared notebooks, with adult consent only.