Joe Huang wrote:
First you would need to deploy the application in "Release Mode". This requires you to create a Java Keystore and a certificate using the Java keytool, and then you would use it to compile the app. If you have done that, then can you please help explain what these pages are doing, and observed performance?
Unfortunately Galaxy Tab 2 is a bit old - if you have done everything to optimize the app, this could be due to older Android OS. Android OS (especially version 2.x) does not support HTML5/JS well, and performance is much worse than HTML5/JS running on Android 4.x devices. This is more than just HW differences - this is primarily due to the web engine used by the webview.
Currently I also facing this problem too as Performance in Android is totally slow, even using a newest android version with and fast device a Nexus 4 and also deployed in "Release" mode as Oracle said to improving performance(but seems nothing to improve).
It seems normally to waiting around 2 minutes for start-up screen before showing default page. but this performance problem is not applied to iOS.
btw My company still be aware about performance issue in Android as depended to user-experience. and I am still looking forward to seeing more improvement in the future.
Well, It's not about 2 minutes, as I was tested with my application and it seems forever showing splashscreen. except you tried to switch application and go back to ADF Mobile application
Only Navigation Bar in bottom shown but content for amx page doesn't show anything.
btw this application is working properly in iOS, so wried with Android. I might be made something wrong, because I was tested with Oracle sample application or freshly created application, It's working properly in Android but might be waiting for splash screen more than iOS