1. if our current applications will eventually cease to work in time.
Yes, if your app dont get updated skd (using a wrapper for core sdk)
2. Will we still be able to continue developing for Dropbox or we need to start looking for alternatives..
We still able. No need for alternatives.
As of now there are different APIs. Some are only for mobile platforms. Some are already using the core v1 api.
Sync- and Datastore-APIs will end of april 2016. Till this date Dropbox encourages us to update the SDK used changing to use the new upcoming core sdk v2 which will be relesed in the next 6 months. Core v2 will have support to sync and datastores i believe...
So we need to switch to use another SDK in future but we CAN continue to develop with Dropbox
See
V2-Preview too.
As far as i can say the following seems the base-statement of the new v2 API
"
Use whatever you want! It’s just HTTP."
There are three categories of endpoints.
- RPC-style: The request and response bodies are both JSON.
- Upload-style: The request has JSON in the Dropbox-API-Arg header and bulk binary data in the body. The response body is JSON.
- Download-style: The request uses the GET method and has JSON in the Dropbox-API-Arg header and nothing in the body. The response has JSON in the Dropbox-API-Result header and bulk binary data in the body.
So we are able to upload files, download files, list folder contents, get metadata from file
just by using http. So, developing an app using Dropbox can be made by using just httputils2