I've decided to take a closer look at Phonegap, which means currently I'm not developing anything, but trying different things, e.g. the camera. Apparently this can't be tested with Ripple for Chrome - as far as I know it needs to be tested either in the emulator or on the device itself. My computer isn't slow, but building an app and installing it either on the emulator or the device still takes "a lot" of time (if you're just playing around).
So my question now: Is there any way of speeding up the process of testing applications e.g. in the computer's browser even if you are using things like camera?
Here are the things I've tried so far:
Using my Sony Xperia Mini Pro
Using Intel-Android-Image
Booting emulator from snapshot
Ripple (which can emulate a lot, but not the camera)
Thanks :)
I ended up building the app each time, it's kind of fast if you use build scripts.
But you can also try cordova browser https://play.google.com/store/apps/details?id=com.eas.cordova.browser
or Cordova Fast https://play.google.com/store/apps/details?id=org.Bellinux.CordovaFast
I haven't tried the latter myself though.
cheers
Related
I am working on a Unity project, and I want to export it on Android, and WebGL. For stability purposes I have to use the profiler provided by Unity, and I managed to make it work with an APK version of my project, running on an Android device. But when I want to export my app on WebGL, it freezes on the first frame, and then stops my web browser.
I checked the checkbox for the profiler to be connected to launch, but nothing seems to be happening on it, and I think it's not working at all...
Have you ever experienced this kind of problem? And how did you manage to solve it?
I have already tried to use the Firefox profiler, but it doesn't work like I was expecting (the Unity profiler is more useful regarding the different processes like GPU CPU Audio etc...)
The version of Unity I am currently using is "Unity_2020.2.4f1"
Can you try running your WebGL version on google chrome?
if you run this app on chrome, you can check the issue on the chrome console.
recently i've found this plugin can preview many device of Android or iOS device in one installed apps,
gif of the plugin is at https://github.com/aloisdeniel/flutter_device_preview
does react native has something like this?
I know there's some similar plugin like Expo and Appetize but i need something like this,
i mean i can preview of many device in my apps, not installing my app on many devices.
I think Apptize seems to be the most similar option available.
flutter_device_preview is certainly a more practical/simple solution. You change the parameters or device, the app is rendered instantaneously. However, it provides a first-order approximation, as said in flutter_device_preview repo:
Think of Device Preview as a first-order approximation of how your app
looks and feels on a mobile device. With Device Mode you don't
actually run your code on a mobile device. You simulate the mobile
user experience from your laptop, desktop or tablet.
But with Apptize you will be able to run a native app, with no approximations, using a the true mobile-OS on any PC/Mac/Linux OS via web. But of course, has some limitations (currently 7 devices only), and has another purpose.
Here you can generate an iframe to start the testing:
https://appetize.io/docs#embed-your-app
I just started to learn how to program an Android applications. Coming from a C# world, one thing that bothers me greatly about Android programming is the fact that it takes forever to actually test your app because you have to fire up AVD or wait until the app is installed on your actual device whereas for Winforms/WPF applications, you just hit that debug button and everything loads within split seconds.
My first question is, which is a more preferred way of developing to maximize efficiency? Develop on AVD or an actual device? Are there any suggestions on how I can improve my development speed?
A few things, most people leave the AVD open whilst they are developing so that they don't have to wait ten minuets every time they open it, however if you have a very slow computer and this is not an option then yes it will talk a while
If you have a faster computer then AVD is likely to be less laggy, but for a completely lag free testing place, use your actual device.
If you are making games you should look into libgdx because it allows you to test your apps on your desktop, then by changing one line, export them as .apk files and test on you android device
For a lot of apps and features within apps you will be left with no option but to test on your real device. Because it can take a while moving the .apk file to the actual device, I would recommend using an on device IDE to make small edits to your code whilst testing certain hardware features such as the volume buttons or the accelerometer. As for on device IDEs I would recommend AIDE - https://play.google.com/store/apps/details?id=com.aide.ui&hl=en
On the whole, I would recommend using eclipse with AVD, for the majority of your development on the majority of your apps, but for any apps that you need hardware functions for, I would recommend using an on device IDE (search the play store for android development for more options if you don't like my recommendation). Most importantly don't list your app until you have tested it on multiple screen sizes on the AVD, and you have tested it on you physical device
Keep the AVD open, you can keep doing debugs and test on it, it will automatically close and reopen with new code, that’s how I do at least, and I am the same, came from C# no experience with Android.
What is the recommended way of testing an app on a device? The emulator is slow, mostly unresponsive and a cpu beast on my machine, so I use my phone to test my app. When I make a change to code, Eclipse builds it automatically, and then I debug it on the device. Is this the most efficient way to test small changes in code?
Android has some information on testing here. Personally I've found that testing code is much faster on a device. Other options without a device is to use something like Android x86 and run it in virtual environment like VirtualBox - this can be faster than the emulator. In my opinion, to really make sure your application is working as expected (especially with graphics and memory usage) is to test with the device(s) you intend to deploy the application on.
That's how I test my code, the emulators and on an actual device are the only ways I know of. I usually use an actual device, but I think you can keep an emulator running to speed up time a bit, but not too much.
It's in my opinion a good way to check the general functionality of your application. If everything works fine, I would use the emulator to check with different versions of android/screen sizes/resolutions etc. Maybe you can ask a friend who has a more powerful PC. The best possible thing is of course that friends/family/relatives etc. own Android devices so you can test your application / let it be tested on real devices.
I have created an iPhone app which works perfectly smooth on my simulator. Now I try to deploy it on an android device (i've tried it on the simulator and also on an android device) and my app runs very slow. It laggs like hell when you even just scroll down, and it takes like 5 seconds to load a page.
Is there anything that could cause this slow behavior?
I'm using Titanium SDK 1.6.2, and when running on the emulator I'm using Android 2.3. - API level 10.
Thanks!
The Titanium Mobile SDk v1.8 from the continuous build seems to speed up the the tableviews.
You can download it from http://builds.appcelerator.com.s3.amazonaws.com/index.html .
Also, I hooked-up my Android device to my Mac and have Titanium Studio install my app there. Much faster than doing so to the Android emulator.
Moreover, some features like playing movies from remote sources don't work on the emulator, but work on the Android device.
The Titanium Appcelerator TableViews are just dead slow on android. Go look through their Q&A section and you'll find ou're not the only one having this issue. Your best bet is to remove as much complexity as you can or possibly pre-render every row as an image and put it in a scroll view.