Answered: Feature Request: Offline timeout of the Space application
I've been playing with Space for a few weeks now and I really love it.
The reason I've been playing with it is that I hope it will make the creation of offline applications for multiple platforms a much easier endeavour at the company I work for. So far I've been very impressed with what is possible. However, I have recently run into a catch 22. The problem is that Space will only allow a device to remain active if it can connect back to the space.sencha.com cloud service once every 12hrs or so. Normally this probably isn't an issue, but for me it is.
The offline applications I envision are intended to be used while employees are away from the office and most likely away from an internet connection. For example, they may take a device (an iPad) out of the office in the evening the first day, then take it to the work site the next day and expect to be able to use it. Offsite field-work may even last 3-4 days. During that time it may not have the opportunity to connect back to Sencha and will therefore "timeout" while the user is still away.
I understand that there are likely to be issues with allowing developers to modify the timeout period of the Space application, however, I think it is probably important to many of us that we have this level of control.