If you’re a software developer, you know that the IDE, and specifically the editor, you use becomes a natural extension of the way you think and work.
So often, the editor we use is a factor of the project we’re working on … we use the right tool for the job (or more specifically … the editor in the IDE we’re using). The question of “what is your favorite editor?” can only be answered when there is no pragmatic environmental factor influencing us. You just need to edit some file .. it’s not a C# file, it’s not a Java file, it’s not an XML file … its just some text file (the issue comes up more often than you might think).
I’ve been a dev for nearly 30 years now and a good deal of that was in Microsoft space. I actually worked with Visual C++ 1.0 (the predecessor to Visual Studio), released in Feb. 1993, back when it was installed from 20 floppy disks because not everyone had the ability to read a CD (DVD’s weren’t even around yet). I’ve worked with every version of Visual C++ & Visual Studio since then. As a result, Visual Studio was my go-to editor.
Over the past few years, I’ve been dug in hard in the Android space. Until the past few weeks, JetBrains IntelliJ IDEA (the tool that Android Studio is built on) was my preferred Android dev environment but as much as I liked IntelliJ, Visual Studio was the tool I used to edit an arbitrary text file.
With the release of Android Studio, I feel like the IntelliJ environment (already fantastic) is even better. And just the other day it occurred to me … why am I firing up Visual Studio to edit a text file when I already have Android Studio open. I love working in Android Studio and as I said … I pretty much always have it open.
So with that I realized … after nearly 20 years of using Visual Studio as my go-to editor … Android Studio is now my Editor-Of-Choice.
Here’s looking forward to another 20 years.!!
For information on getting started developing Android applications or working with Android Studio, checkout Jim’s Android programming courses on Pluralsight including his latest course.
There’s no question that smartphones and tablets have become the computers of choice for most users. Android has been the leading smartphone for some time and now Android leads in tablets as well.
According to Google, nearly 900 million Android devices have been activated. This presents an incredible opportunity for both individual developers and organizations to create software with a reach and impact beyond anything previously possible.
Android development is, of course, very different from the web-based and/or desktop app development most of us have been doing for years. But this difference doesn’t mean we can’t take part in such a great opportunity.
People will often point to Android’s use of Java rather than .NET being the biggest challenge in becoming an Android developer. I disagree. If that were the case, environments like Mono that enable the use of C# and .NET libraries on Android would enable us all to immediately become Android developers. But in my experience, developers with a .NET background who use Mono don’t become effective Android developers any faster than those who take the plunge and use Java. Why is that?
The challenge in creating Android apps is not the programming language, class libraries, or runtime. The challenge in creating Android apps is that it’s an entirely different way of thinking and an entirely different approach to application development.
To be successful on such a different platform, developers need to adopt and ultimately embrace the way-of-thinking of the Android platform.
The new series from Pluralsight, Android for .NET Developers, strives to do exactly that. We focus on guiding developers to fully embrace the tools, language, libraries and, most importantly, mindset of Android development by building on your skills as a .NET developer. Although this series assumes a .NET background, the series is appropriate for anyone with existing programming experience who wants to start working with Android.
In the first course in the series, Android for .NET Developers: Getting Started, we walk through the process of setting up your environment, using the Android development tools, and deploying apps to both real devices and emulators. We talk briefly about the long-standing development environment, Eclipse, but focus throughout the series on the new development environment, Android Studio, announced by Google just a few days ago.
The first course in the series is now available with a new course from the series being released every few weeks. The series is made up of the following courses.
Android for .NET Developers: Building an Android App
Android for .NET Developers: Android data management
Android for .NET Developers: Adopting the Android mindset
Android for .NET Developers: Embracing the Android platform
I hope you’ll join me in this experience of leveraging your existing skills to empower you to take part in the opportunity offered by the success of Android. At the end of this series, I’m confident that you will have adopted the Android mindset and will be embracing the Android platform.