Normal
Testing it on my desire now but the first little issue I came accross is that the Android app is giving me a hard time letting me type in my MAC adress.It seems like only numeric characters are allowed, which is ofcourse not the case for a hexidecimal thing like a MAC.Just reporting, going to test a bit more, looks great so far !!---EDIT---Just tested the app a bit more and for me it has some issues with responsiveness. Not sure if at all possible with android coding but the downloading of the xml sheets should ideally be done in a background thread, while the GUI displays a loading animation.Same would go for loading image thumbs because that's quite slow when loading large folders. If you would be able to load this asynchronously that would at least make it feel a lot faster.Another approach would be paginating your data (so page 1 shows 50 items, page 2 50 etc), this principle can also be applied in an asynchronous fashion so you would not need actual pagination links/buttons (see the new google image search for example). The last one would also benefit from loading data in a background thread but is most likely a bit hard(er) to implement.Do not get me the wrong way, just trying to give constructive criticiscm. Can't wait to see your next release, it's all really promising.
Testing it on my desire now but the first little issue I came accross is that the Android app is giving me a hard time letting me type in my MAC adress.
It seems like only numeric characters are allowed, which is ofcourse not the case for a hexidecimal thing like a MAC.
Just reporting, going to test a bit more, looks great so far !!
---EDIT---
Just tested the app a bit more and for me it has some issues with responsiveness. Not sure if at all possible with android coding but the downloading of the xml sheets should ideally be done in a background thread, while the GUI displays a loading animation.
Same would go for loading image thumbs because that's quite slow when loading large folders. If you would be able to load this asynchronously that would at least make it feel a lot faster.
Another approach would be paginating your data (so page 1 shows 50 items, page 2 50 etc), this principle can also be applied in an asynchronous fashion so you would not need actual pagination links/buttons (see the new google image search for example). The last one would also benefit from loading data in a background thread but is most likely a bit hard(er) to implement.
Do not get me the wrong way, just trying to give constructive criticiscm. Can't wait to see your next release, it's all really promising.