What is our primary use case?
My main use case for Android SDK is writing code and developing apps, including developing some Java apps, Kotlin apps, and apps using Flutter and Dart.
In addition to that, I also use the integrated Gemini Code Assist with Android SDK, which helps me in debugging and writing code snippets.
What is most valuable?
The best features Android SDK offers are its Flutter integration, the LogCat feature, and especially the Gemini Code Assist integration that helps me in logging all the errors and bugs.
Gemini Code Assist helps me in my workflow by managing boilerplate code; it assists me, for example, when I have to write the same code snippet multiple times, or when I need to handle redundant tasks such as creating base pages with nothing on them.
It is worth mentioning that Gemini Code Assist has the context of the whole project within Android SDK, so I do not need to tell it what the project is; it understands everything due to its integration.
Android SDK has positively impacted my organization by saving a lot of time with its built-in emulators, and the LogCat feature helps tremendously in debugging since it is specifically made for app development.
Considering those benefits, such as built-in emulators and smoother debugging, I have noticed specific outcomes such as faster release cycles and fewer bugs.
What needs improvement?
Android SDK could be better if its integration for Flutter was improved; I understand it is tailored for Kotlin and Java apps, but many of us are using Flutter.
When working on a Flutter project, I find it lacking since I have to go through extra steps to create or build a new Flutter project or customize the Flutter app, which is not required for normal Java or Kotlin apps.
For how long have I used the solution?
I have been using Android SDK for more than eighteen months now.
What do I think about the stability of the solution?
Android SDK's stability for me varies depending on the type of computer used.
If you are using a low-end device, it might crash, whereas a high-end device will not have that issue.
What do I think about the scalability of the solution?
Android SDK handles bigger projects smoothly, and so far it has been quite smooth.
Again, how Android SDK handles larger projects depends on the type of computer being used; with a low-end device, the project size could cause it to lag or crash, but a high-end device will scale well without lagging.
How are customer service and support?
The customer support for Android SDK has been sufficient; I have not needed to reach out for help from Google or the community since I found most of my answers in frequently asked questions, forums, or Stack Overflow.
How was the initial setup?
The setup part for Android SDK was not as simple as other IDEs, as there is a small amount of configuration and setup required, but overall it was still easy; I would not say very easy, but it was not hard either.
What was our ROI?
I have definitely seen a return on investment from using Android SDK; it saves a significant amount of time and we have saved a lot on testers; time is money after all.
What's my experience with pricing, setup cost, and licensing?
In terms of pricing, setup cost, and licensing for Android SDK, it is quite cheap; I did not spend much and even received vouchers for Gemini Pro.
Which other solutions did I evaluate?
Before choosing Android SDK, I did evaluate other options.
The options I looked at before landing on Android SDK included VS Code and IntelliJ IDEA, but I wanted to specifically use an IDE for Android projects, so Android SDK felt like the best choice.
What other advice do I have?
My advice to others considering Android SDK is that if you are working on Android apps, you should use Android SDK, but if you have a low-end device, you should avoid the internal emulator and use your own device; if you have a high-end device, then use the built-in emulator, but I would still recommend using another device if possible, and when developing specifically for Flutter apps, be aware there are other IDEs available.
I have no additional thoughts about Android SDK; I just really appreciate it, it helps me a lot, and I have been using it for more than a year now, and it is great. I gave this review a rating of nine out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
"Best SDK"
You should try out other mobile SDK as well before terming the Android SDK as the best.
"Simulator support"
Every mobile SDk has simulator support what makes it a pros for Android SDK.
Can program in java
You can also use C / C++ code.
IDE support.
Again, It uses Eclipse which integrates Android SDK as an add-on.
Suggestion: Try out XCode if you get a chance and see for yourself how different and easy to use it is from the Android IDE.