Why is the Xcode Simulator called "Simulator" while the Android Studio Emulator is called "Emulator" when they bot basically do the same.
I'm not really sure if they are both simulators or emualtors.
Not even after reading this discussion:
Simulator or Emulator? What is the difference?
Emulator:-
In computing, an emulator is hardware or software that enables one computer system (called the host) to behave like another computer system (called the guest). An emulator typically enables the host system to run software or use peripheral devices designed for the guest system.
Performance Emulators are really slow. Emulating the actual hardware usually makes the software run slower than it would natively.
Example:- Google's Android SDK
MORE INFO IN WIKI
Simulator:-
A mobile simulator is a software application for a personal computer which creates a virtual machine version of a mobile device, such as a mobile phone, iPhone, other smartphone, or calculator, on the computer. This may sometimes also be termed an emulator.
MORE INFO IN WIKI
Faster than emulators
Example :-Apple's iOS Simulator
Related
I live in a shared apartment and share WiFi with many other people. Is it safe to do wireless debugging on real Android or iOS devices?
If I'm not mistaken, wireless debugging to an android device is done with RSA, so there is nothing to worry about (please correct me if I'm wrong).
But how is it with iOS? Will there be any security risks if I use my real iPhone for iOS debugging and do it wirelessly?
We have a dozen or so mobile devices for testing. Emulators in SDK's like Android's or Xcode have quirks. So, we use actually devices.
I've tried browser synchronization like browser-sync but that routes everything through a proxy.
I'm looking for a way to remotely view and control these devices from a desktop. I've tried running a VNC server on the mobile devices, but VNC is just too slow. Not to mention, the devices themselves lack any real processing power.
Any ideas?
You can try seeTest Manual tool http://experitest.com/support-2/seetest-pricing-manual/. It is a free tool. Very easy to install and setup.
You can remotely connect and control your android and iphone devices from PC. It is just like interacting with the mobile phone from desktop.
I am a windows phone app developer. My PC do not have enough graphics to support windows phone emulator. So I am developing application by using the windows phone device (HTC HD7) for debugging and testing from almost 5 months now. Now my device is so hanging and switch-off automatically sometimes. Is it bad for the device to use the developing purpose rather than using emulator ?. Is my device have problem because of the continuous use for developing ?
I think it is not a problem in using device for the developing purpose.
Looks like a fault in the device - I'd send it in for repair. I've certainly not heard of debugging causing issues with devices.
Do check if your internal storage is about getting full. Also if you have minimum RAM config, try not using multiple apps while debugging. Probably this should help.
And nonetheless, you can just visit a technician and get your phone thoroughly checked for issues.
I use Mac OSX. I now want to try and develop an app on windows 8 for the Imagine Cup.
But i dont want to switch back to windows.
Is there any way to develop apps for windows 8 from mac?
Preferably free option....
The only available way is to use Virtual Machine because one cannot develop Windows 8 Modern UI app(Windows Store app) even with lower version of windows than windows 8. There are many virtual machines are available for free. Virtualbox maybe a good start.
www.techspot.com/guides/503-windows-8-virtual-machine ,A Tutorial to create vm of windows 8.
Assuming that windows phone is the platform you chose to develop app, again you need windows to create windows phone app.
Kick start your windows phone app development here .
I actually use VMWare on a Mac to do all of my Win32 development on Windows 7 and VS2010.
You will need:
a powerful mac (i7)
lots of RAM (I have 8G, I wish I had 16G)
a 7200rpm HDD or SSD.
With that, it's really great for me. I've been doing this for a few months now without a single kernel panic or blue screen at all.
Note: You cannot really develop for WP7 using this sort of configuration. The WP7 simulator uses VirtualBox, which either runs extremely slowly or not at all in other VMs, based on our experience. Will need a real Windows machine for that ^_^
It's a workable scenario. Good luck!
I have been long interested to develop on the platform. I even got the tools installed already on my desktop but I can't upgrade my WDDM from 1.0 to 1.1. To make things simple: my graphics chips are not up to the task of running the emulator.
If I still buy a Windows Phone (e.g. a Nokia Lumia) for development purposes, can I sideload and test my apps there efficiently instead of going against the emulator?
If I still buy a Windows Phone (e.g. a Nokia Lumia) for development purposes, can I sideload and test my apps there efficiently instead of going against the emulator
Yes, of course. It's very easy and convenient. You have debugger and all the goodies. Advantage of the emulator is the test option for 256MB devices.
That's exactly what I used to do prior to upgrading my devstation. The nominal min spec says 3G but with a real phone it worked fine in 2G and as you say this also sorts out graphics limitations.
Note that the setting for whether the emulator or physical device is used is stored in the project, so if you accept a project from someone else you will have to set it once prior to debugging.
Well there are 2 sides of the coin. With the physical device you can test most of the things, but with a few limitations
You will not be able to test internet related test cases - For example, if you have an app which uses internet connectivity then you will not be able to test it on the device easily because
The device does not use the machine internet connectivity
When connected to the PC the device's internet connectivity(Data connection 3G/ wifi/GPRS) is broken.
You will have to purchase an account right from the first day you want to test your app. If you have the emulator working then you could postpone this for atleast few days.