Yea, that is what I did. But shouldn't there be a cancel function? If not, I think it would be great if you have a number indicator below the download bar, as the user can see exactly how long left, and if it is even moving.
Anyway, while downloading the user should not be able to press Back, and even so, the bottom of the main screen should not indicate Disconnect which would be misleading.
Not sure what you mean. If you kill the app and start it again, it does not remember what you were doing previously and should just start up. It will certainly not "crash every time" as that implies you can't ever use the app again?
I mean if you are downloading something, and you press Home button, then you try to openup NBRemote again, it will crash. You will have to kill it. Shouldn't the correct procedure be letting me back in and show me the downloading box thingy?
Yeah, that is not recommended. In fact I wouldn't recommend using the NB user interface at all while using NBRemote.
Would it be possible to handle this disconnection gracefully without crashing? And will the temporary downloaded file be deleted, or will it be left on the filesystem (either to be continued or abandoned)?
Also I think you forgot to address this bug: And when adding a computer, and the serial number field is blank, Test connection will just show the rotating loading icon forever, without notifying the user that a field is missing or connection timeout.
Thanks!