Well there’s good news and bad news. Good news: I set a reminder, walked away, and my Android phone buzzed at exactly the right time, app fully closed. The whole point of InSave, working on real hardware, not in a test. After weeks of “it passes 198 tests,” watching it actually go off in my hand hit different.
iPhones refuse to cooperate tho, I built the iPhone capture so you share a reel, tap a shortcut, it saves. It did save. Reel captured and everything looked fine. Except it wasnt. Turns out on iPhone, the website you open from a link and the app you installed to your home screen are treated as two completely separate things with separate memories. The shortcut saved my reel into one; my reminders live in the other.
Looks like I have to do the hard part now InSave never had logins. Every phone, every browser, quietly invented its own anonymous identity, and they never talked. It worked fine when I only tested on one device. The moment I used two, like in the case for Iphone where 1 device shows 2 (curse you apple). My own database is sitting here with three different “me”s in it. The main bug
So the next build is the one I kept putting off because it felt boring: actual accounts. One login, one library, everything in one place no matter which phone or app you opened. It’s the thing that makes iPhone actually work, and the thing that means you never lose your reels switching phones.
Where it stands: 198 tests green, live on real servers, Android reminders confirmed firing on a real phone. iPhone capture works mechanically but needs accounts to be useful.