I've developed using both. Dropbox is much more well-known overall where Box is much more well-known in the enterprise area. From the iOS developer side of things I much prefer Dropbox and here's why:
- Box's SDK authentication uses a modal view controller with a web view to authenticate. Its appearance is somewhat unpolished and glitchy. Dropbox redirects to the Dropbox app if installed and if not uses a modal view controller. Box used to use this method but no longer does for some reason. It's much more cumbersome to log in without it.
- Dropbox is path-based and all actions are based on a path. Box requires that you recursively iterate from the root to get each level's unique ID if all you have is a path.
- Box's SDK has had a much slower development cycle than Dropbox. There are many operations that are not yet coded.
- Box refreshes the login token frequently, which has a tendency to slow things down.
All of these make something as common as a file chooser much, much easier to implement on Dropbox.
- Box's SDK authentication uses a modal view controller with a web view to authenticate. Its appearance is somewhat unpolished and glitchy. Dropbox redirects to the Dropbox app if installed and if not uses a modal view controller. Box used to use this method but no longer does for some reason. It's much more cumbersome to log in without it.
- Dropbox is path-based and all actions are based on a path. Box requires that you recursively iterate from the root to get each level's unique ID if all you have is a path.
- Box's SDK has had a much slower development cycle than Dropbox. There are many operations that are not yet coded.
- Box refreshes the login token frequently, which has a tendency to slow things down.
All of these make something as common as a file chooser much, much easier to implement on Dropbox.