Are you finding it increasingly difficult to debug your Android projects? There are currently many android emulators out there that promise better speeds than the default android emulators but the pain involved in setting them up makes their seeming advantages vanish.
For instance, GenyMotion is one such emulator but the pain involved in setting up an online account with them, launching a VM, installing an emulator then setting up your IDE to use GenyMotion makes it a bit of a stretch.
BlueStacks have been around for a while now and though its gained traction with lots of Windows and Mac users, it is actually an Android emulator and can be configured to test Android Apps.
To do this, head over to the BlueStacks website, download and install a copy. Luckily it’s free and requires no registration.
Next, Launch BlueStacks
If you’re using Android Studio, from the Tools menu, go to Android then Enable ADB integration and launch the Android Debug monitor. The BlueStacks emulator should be listed. Now you can run your application in BlueStacks by choosing Run app in Android Developer Studio and select Bluestacks from the running devices.
If you’re using Eclipse, configure BlueStacks as an Android remote device (default port is usually 5555 or 5554) and viola, you’re off to debugging and testing your Android Apps.
As an emulator, it offers just about all the other options other emulators promote including full integration with the Android Debug Monitor, Logcat and more.
Android bootstrap can serve as a good scaffold in learning and building android apps. A nice tool it is but the documentation on the site is outdated and it currently prefers gradle to maven unlike what the documentation and accompanying video suggests.
I found the source files on Github do not have the pom.xml files to make out of the box development easy. So head over to the Android Bootstrap generation page, enter some details about your app and generate source code specifically tailored for your app. Unzip the files to a location of your choosing.
Install all the needed tools, JDK, Android Studio or IntelliJ, Gradle and all other dependencies the tools may suggest. Add gradle to your paths so you can run gradle commands easily from your terminal. Continue reading
Following John Resig’s post on writing code everyday, I decided to commit to that as well and write code everyday as that will be immensely helpful in crossing items off my ever growing todo list.
Further reading led me to Jerry Seinfeld’s productivity secret, which proved useful. So now I pledge to not only writing code everyday but to cross an X on my calendar each time I fulfill that pledge.
Pledge to blogging everyday? Not now 🙂 though I will do well to update it frequently.