Product · In development
nestry+
nestry is money for two, made quiet — and it's also the app that taught us our own rule. We built it twice: once on a hosted realtime backend, and again with no backend at all. nestry+, the local-first rebuild, is the version shipping.
The problem
Couples split costs constantly, but logging them is tedious enough that people stop. The first build solved that — a two-tap custom keypad, live sync, on-device AI reading a spend from plain text. But it carried a hosted backend and an account system for what is fundamentally a two-person, private dataset. That's a monthly bill and a login for data that never needed to leave the couple.
Our approach
nestry+ keeps everything that made entry fast and drops everything that made the app dependent: Core Data with iCloud (NSPersistentCloudKitContainer) instead of a hosted database, partner sharing as a CKShare instead of accounts, a one-time purchase instead of a subscription. No login, no server, no analytics. The app costs nothing to keep alive — which means it never has to die.
Where it stands
In development and headed for the App Store. The honest version of this story — why we killed our own backend — lives on the founder's build log.
