34105204aaa754e8367c41b235ec4f3d92494be6
wiki/mobile-development.md
| ... | ... | @@ -2,6 +2,8 @@ |
| 2 | 2 | |
| 3 | 3 | See [On Boarding](onboarding#Additional-steps-required-for-Android-projects) how to set up your build environment for mobile development. |
| 4 | 4 | |
| 5 | +## Emulation |
|
| 6 | + |
|
| 5 | 7 | Besides running the application on a plugged-in device there are multiple options for using an emulator: |
| 6 | 8 | |
| 7 | 9 | * Android Virtual Device (AVD) |
| ... | ... | @@ -15,4 +17,8 @@ Besides running the application on a plugged-in device there are multiple option |
| 15 | 17 | * Currently in free beta phase; way faster than AVD; better support for Google Apps (e.g. Maps) and easy access to sensor features (e.g. setting GPS info) |
| 16 | 18 | * Register at http://www.genymotion.com/, download and install virtual device "WXGA 10.1 Tablet - 4.1.1 - with Google Apps - API 16 - 1280x800" with 160dpi |
| 17 | 19 | * If you want to run the app against your locally-running server, check the IP address of your host machine for the VirtualBox network interface. Use this IP when you are configuring the app. |
| 18 | - * Use virtual device as described in [[On Boarding|wiki/onboarding]] |
|
| ... | ... | \ No newline at end of file |
| 0 | + * Use virtual device as described in [[On Boarding|wiki/onboarding]] |
|
| 1 | + |
|
| 2 | +## Mocking the server |
|
| 3 | + |
|
| 4 | +For rapid development of the mobile applications using a mocked server has proven to work best. One can use [Fiddler](http://fiddler2.com/)'s AutoResponder feature to quickly try out new mobile features and easily test some edge cases. |
|
| ... | ... | \ No newline at end of file |