Retiring the Sync and Datastore APIs: a year's notice, then dead apps
April 2015 (Sync deprecated Oct 2015, Datastore shut April 2016)
In April 2015 Dropbox announced it would retire the Sync API and the Datastore API, giving developers about a year to rewrite onto the Core API — apps that did not migrate stopped working when the Datastore API was shut down on 29 April 2016.
What happened
On 24 April 2015 Dropbox announced it was deprecating two of its developer products — the Sync API (a higher-level file-syncing SDK for mobile apps) and the Datastore API (a structured-data sync service launched in 2013). The company framed it as simplification: having multiple overlapping ways to do the same thing, it said, had confused developers, and the Datastore API in particular had never seen the adoption Dropbox hoped for.
Developers were told to migrate to the lower-level Core API and its SDKs. The Sync API stopped being supported on 23 October 2015, and the Datastore API was fully shut down on 29 April 2016. Apps that relied on Datastores for cross-device structured data — note-takers, to-do apps, and similar tools — had to either rebuild that functionality themselves on top of file storage or move to an entirely different backend. Some open-source and hobby projects that depended on the Sync SDK simply broke.
The retirement was an early, clear signal that Dropbox was narrowing its platform ambitions and would not keep maintaining developer surfaces it considered under-used, regardless of the apps already built on them.
Impact
The shutdown forced a wave of unplanned engineering work across the third-party ecosystem and stranded apps whose authors had moved on. It marked the beginning of a multi-year pattern — deprecate, give notice, shut down — that repeatedly taught developers that building on Dropbox carried migration risk, and pushed some toward self-hosted or open-source sync alternatives.