samuk1000k wrote:
I am a fairly new paid up user and grateful for the free time spent using 2.2.1.
I want to urgently request that further syncing options are made available on the app particularly sync.com which I use instead of Dropbox.
Is this feasible?
Thanks
Dr S B. User.
Hello all,
Actually, I would myself be thankful of a generic sync method that would not lock us to a specific provider. I sure am NOT fond of having to struggle with WiFi or USB connectivity to launch a manual process when all of my data outside TR is sync by SyncThing in the background, without effort from my part. By the way, this is how I sync TR between my desktop and my laptops.
To put it bluntly, sync as it is implemented now prevents me from even considering the use of the mobile app. It makes me feel that the mobile app is a second class citizen, what is a real issue for a tool that by nature I would like to be able to use seamlessly on the go.
* Hypothesis 1 - the mobile app is compatible with the file format of the desktop app
In that case, it is only a matter of exposing and documenting what folder needs be synchronized on the Android file system. Warn us about concurrent accesses in the same way it is done with current sync schemes, and let the user manage one's data. From there anyone could use SpiderOak, Syncthing, Bittorrent Sync, Owncloud or any other provider without additional work from your part. This is how I intend to use Syncthing to keep TR in sync between my desktop PC and my 2 laptops, for example. I can't tell if this scheme would be possible on iOS, since I know that iOS does not let one easily access the underlying FS. My guess would be that no, and another guess is that it may be the very reason we currently have no simple file based sync mechanism on Android. With Android having more than 80% of the market share today, I don't think that iOS flaws remain a valid reason to cripple Android apps down anymore.
* Hypothesis 2 - the mobile app uses an incompatible (stripped down?) file format/data store.
There are still many solutions. Implement a dropbox like scheme (up/down exchange) based on standard WebdDAV integration. Adapt the current dropbox scheme to use the filesystem (e.g. push "up" file to a sync'd folder, poll until it disappears or wait for a notification of deletion if supported, wait for the "down" file, process it, use timeouts and transactions to handle exceptions).
Best regards,
Xavier