roryobryan

Members
  • Posts

    1
  • Joined

  • Last visited

Everything posted by roryobryan

  1. I could see this as a replacement for dropbox and the dropbox API in applications. Also iCloud on iOS. So as an iOS developer I would expect a library I could include in my application and an API to interact with it. In the first instance it may just be a low-level C based API. Followed later by an OO Objective-C API for iOS. In this case the developer is completely responsible for managing the user experience and making the process of syncing simple and secure for the user, in whatever way suits their application: For instance in a hypothetical photo sharing app. I develop a mobile version, a desktop version, and perhaps an online service, and sync the users photos between them. I would be expected to implement some kind of user account system myself and make the process of setting up and linking each device simple for the user. In this case BitTorrent sync would just be plumbing. A next step / alternative might be an API into a BitTorrent Sync library again, however in this case the concept of having apps use BitTorrent Sync for syncing is built into BitTorrent Sync. Perhaps with an alternative BitTorrent Sync desktop client that is specifically tailored to this use and easily understood by the average user. There might be an abstraction built over the top of the existing system that managed a single folder per application on the users behalf. The process of adding an App to your BitTorrent Sync "Cloud" would be standardised and simplified for the user. The library for use by the application would then have a common user interface for linking apps. The user would become familiar with a standard "login" / "authorisation" page that would be common across many apps. In this case the user installs the hypothetical photo sharing app. The user has already installed BitTorrent Sync on their desktop in the past and authorised other applications. In order to sync devices I present a standard BitTorrent Sync screen where the user "authorises", "links", or "logs in", to their BitTorrent Sync "Cloud". As an app developer I then simply have a single folder where i read and write and manage my apps data. The BitTorrent Sync desktop client is then a place where the user can go to see what "Apps" are linked to their "Cloud" perhaps de-authorising them, limiting their bandwidth, disk usage etc.