Appium and Calabash both are very useful in Android application development. Let’s have a detailed comparison. 

Appium

1. There is no language requirement. The tests can be written in any language of your choice. My experience with Python, Java, and Ruby bindings has been excellent.
2. You never have to recompile the app. With Appium, whatever build you are working on can go to production.
3. The Appium community is very active. Once you call for help in any situation, you will get help from all over.
4. Unlike traditional selenium webdrivers, it is built on top of them. In addition to this, it also has its own set of APIs that are very helpful in automating mobile test cases. In this way, you are able to use all Selenium APIs as well as many additional utilities.
5. There is only one tool to work with both Android and iOS (Firefox OS is also on the roadmap). Cool, huh?

Aside from the above pointers, the use of CS and your preferred tools is up to you. Appium is not a limiting factor.

Calabash

1. To work with Ruby, you will need to learn it.
2. Compilations need to be recompiled.
3. In comparison to Appium, I didn't find the community support as extensive.
4. Calabash's iOS and Android versions are different. It doesn't come in a single package.
5. In my experience, Calabash emphasizes highly on BDD-style test writing.
6. While working with calabash, it can be helpful to have experience with Capybara.

What are some good practices in Android application development?

As a result of Android's reputation, Android application development is in high demand. It is the responsibility of Android developers to ensure that mobile apps don't lead to a poor user experience. Here are a few Android application development tips and practices that will ensure best-in-class performance.

1. Learn XML and JAVA

Android's user interface (UI) and components are built on XML (Extensible Markup Language). Java is used for the back-end code of the Android platform and to bind XML layouts with the Java code.

2. Switch to Android Studio

The official Android development IDE is now Android Studio. Suppose you're still on Eclipse and that isn't enough to convince you to change. Luckily, Android Studio uses Gradle. There is support for Maven repositories, as well as multiple build types, numerous app flavors, and customized apk signing configurations. It also comes with a 9-patch creator. Preview mode allows you to view resources such as strings, colors, and other drawables. The keyboard shortcuts and navigation of IntelliJ IDEA are accessible from the preview mode.

3. Understand Memory Limitations

To program for mobile devices, you need to learn how to program with smaller memory limits. If you misuse memory on an Android device, you run the risk of your app crashing due to "out of memory" errors.

4. Use the Default Keyboard Based on Required Input

An app should automatically display the correct type of input characters when the user clicks on an input text box. As an example, a numerical keyboard should be the default if the user enters a mobile phone number. You'll need a keyboard that includes characters, @ symbols, and a .com key if the app requires an email address.

5. Use an HTTP library like Volley, Retrofit

In the process of creating a big application, boilerplate code can make our networking code very large. This complicates not only maintenance but also debugging.