Apparently people have been waiting for things such as bulk delete and faster syncing for some time. Supposedly we now have it… Well if we do it is very lame. I say this as someone who has written software for forty years and understand the need for immediate user feedback and interaction.
The bulk delete worked for me once or twice and failed after a few MINUTES, and the syncing is still taking forever and restarts when the App gets priority, seemingly from the beginning.
Way back when during the User Interface wars thirty years ago it was recognized that THREE seconds was the maximum you can make anyone wait for any feature to complete. This was studies done by Digital Equipment Corporation.
What the Tablo is doing can easily be accomplished in this time frame for interactive responses. Your software “staff” apparently does not understand how to architect for this process.
So for BULK DELETE. When I say “delete” anything you simply MARK it as deleted in your database / file system. Don’t do the delete at that time! You have a background task that does the delete sometime later. You can have an idle process that just deletes one item at a time when nothing else is ongoing with the system. Garbage collection.
For Synch you are sending all the same data over and over again to the App running. All you need to do is query the LAST SYNC DATE OR ORDINAL and then send any updates. You don’t need to send anything it already has accumulated. And if the sync stops because the app goes to the background, when it goes to the background it WRITES OUT the last entry to a field it got so it can START at that point again when the App runs again.
For Queuing a recording you send the info on what you want to queue and the Tablo just returns that it has gotten the recording request. The App doesn’t wait until the Tablo does whatever is needed to setup the recording, it should IMMEDIATELY be available for more use.
I have written plenty of firmware for small devices in addition to Android apps and mostly big big programs which are running many complex tasks. What you guys are doing is really in many ways trivial in the regard to user interaction. But you are not looking at the solution correctly. This is not a lot of work in any regard but basically if the user has to wait for this interaction forget getting more users. Goodby Tablo.
This message is done in a constructive way because it just seems your software people are totally missing how to architect for the user experience. If you were working for me or anyone I have worked for they would not find what is released acceptable. My last commercial software was Onscreen Display for forty HDTV manufacturers so I understand what am talking about.
Feel free to contact me via email and perhaps phone if you desire further input. I do not monitor your forums.