Evernote rebuilt on Bending Spoons Engine

The important shift is that Evernote stopped being a standalone app with its own aging plumbing and became one product riding on a common engine that Bending Spoons can improve once and reuse across the portfolio. In practice, that means note syncing, login, payments, analytics, and experimentation move onto shared services, while Evernote also changed its note format and sync model so edits propagate faster across devices with fewer conflicts.

• The infrastructure change was not cosmetic. Bending Spoons says its internal Spoon Engine gives acquired apps more than 50 shared services, including authentication, payments, A/B testing, analytics, and AI inference. Rebuilding Evernote on that base cuts duplicate backend work and makes speed improvements part of a repeatable integration playbook.
  1 sacra 2 evernote
• On the product side, Evernote replaced the old HTML-style note format with a CRDT based system using Yjs. That is the technical reason sync can feel faster. Each device can merge edits at a finer level instead of passing around heavier note blobs, which matters when users jump between phone, desktop, and web.
  3 evernote
• This is also how the acquisition model works economically. Bending Spoons cuts local app specific infrastructure, moves teams into a central operating model in Europe, and then uses one platform across Evernote, Remini, Splice, WeTransfer, and others. The gain is lower operating cost per app and faster rollout of shared upgrades.
  1 sacra 4 evernote

Going forward, the same shared stack should make Evernote easier to bundle with other Bending Spoons products and easier to keep improving without rebuilding core systems again. The more products that move onto the engine, the more the company can turn backend speed, reliability, and AI features into a portfolio wide advantage instead of a one app project.