Android SDK Reviews

My company uses Android SDK for building Android-based applications for clients and customers.

The most valuable feature of the solution stems from the fact that it is a stable product. There are many tools in Android SDK to build applications. In Android SDK, there are too many templates to start with, which are easy to code and design since you just need to drag and drop and write code. You can directly database, like a Firebase Realtime Database.

There isn't a need for any improvement in Android SDK since they provide users with two or three updates in a year, making it quite stable.

The security part in Android SDK depends on how you build an application using the tool so you can apply some security to your application. The reason why Temenos Quantum is the best security tool is because it uses a middleware named Fabric, so the APIs are connected from Fabric to Temenos Quantum. The middleware offered by Temenos is really strong. If I compare the security offered by Android to that of Temenos Quantum, Android will lose in terms of security. You can create a secure application with Android SDK. The amount of security offered by Android SDK is less when compared to Temenos, making it an area of concern where improvement can be made.

I don't think Android SDK needs to add any features because they give updates frequently.

I have been using Android SDK for three years. I am an end-user of Android SDK.

Stability-wise, I rate the solution a nine to ten out of ten.

It is quite a scalable solution.

I am the only person who works on Android SDK since my organization is not much into mobile application development.

The product's initial setup is very straightforward and simple since you just download the setup and install it by following the steps.

The solution is deployed on an on-premises model.

Android SDK can be cheap and can go high in terms of prices, and it all depends on who the customers are and what kind of application you want. One application may cost 5,000 USD and can go up from 1,00,000 to 2,00,000 USD.

Android SDK is definitely worth the money.

I chose Android SDK since I started my career with Android, and I was really into mobile application development. I needed something to start with, so I decided to go ahead with Android. Actually, I needed to go for native mobile app development, which Android and iOS offered. I plan to move on to iOS as well.

I recommend Android SDK to those who plan to use it.

Since there are no lags in Android SDK while mostly remaining stable and ensuring that everything is on the IDE, it is quite easy to use, providing an overall good experience to users.

I rate the overall product a nine out of ten.

I have not particularly or dedicatedly been working with Android SDK. When you work with Temenos retail application, you sometimes have to build certain functionalities that are not implemented in the retail application as of now, because of which you need to create applications with Android SDK and embed them into the retail application.

Android SDK is essentially like an open box. You can build on an Android platform whatever you want to build as per your imagination, meaning the product has no limit, and its use is based upon your capabilities.

The most valuable features of the solution are the easy deployment and development life cycle, meaning you can easily build and complete an end-to-end application within three months. Android SDK is very scalable, secure, and fast.

Android SDK is perfect the way it is right now. The security implementation is the only area of concern in Android SDK where a bit of enhancements can help.

I have been using Android SDK for around two years. Right now, my company works with the client version of the product.

It is a completely stable solution that has been working for many years.

It is a scalable solution. You make an application with Android SDK from scratch, and it can be infinitely scalable depending on the architecture you use.

I don't know how many people in my organization use the product, but I am sure millions of people worldwide use the platform.

Android SDK is an open-source product with multiple online forums, like Stack Overflow or ChatGPT. You can use unlimited resources to debug and resolve your issues.

Android SDK is an open-source platform that is relatively easy to deploy. You just need to build and deploy the application onto Google Play Console.

Android SDK is essentially an open-source product on which anybody can work.

Compared to iOS, Android SDK is a little bit far behind on security. But other than that, Android SDK is pretty good.

If you use Android SDK to create and deploy an application onto an Android OS, you will see that it's very fast, stable, and secure. With Flutter, you can deploy one codebase onto multiple channels, like iOS, Android, and Android Web apps. With Android SDK, you can only create an Android-based application.

Every platform, including Android SDK, requires maintenance. Android SDK provides upgrades, and it is very easy to embed them into your system.

Android SDK is an open-source platform. You can just Google for a bunch of courses to learn about Android SDK before getting started.

I rate the overall product a nine out of ten.

Our organization has two developers working on the solution, one working in the local branch and the other, me, working in the international branch. We have used Android SDK to draw on applications like LAMIS Lite. LAMIS Lite contains office ID testing and biometrics. We use Neurotechnology and SecuGen SDKs.

Outside my current organization, I have been contracted to develop the OXYGEN mobile application for Access Bank, which is used for loan requisitions by account holders.

The best thing about Android SDK is its extensive graphics compared to iOS. Moreover, Android SDK is open-source, so anyone can develop any application because it is easy to get resources on the solution. Suppose I'm developing retail management software for an online ordering business. In that case, I can easily check existing applications online and access code, such as the XML layout or the Java code, to start building the app. Android SDK has modern libraries for animations, and the UI is easy to use. Many countries, even those with fewer resources, prefer using Android SDK because it is cheap and easy to use. Anyone can pick it up. I am in love with the solution, and I appreciate its flexibility.

Android SDK could use some new features, for example, picture-in-picture, because you cannot do that in Android now. In iOS, by comparison, you can do picture-in-picture. With this feature on iOS, I could play videos in the background from TikTok, Facebook, or Instagram. The video appears as a small thumbnail. Android SDK should have picture-in-picture enabled automatically or allow the user to enable it from settings so that if they are playing videos on one application, they should be able to have a picture-in-picture thumbnail in the background. There are lots of things Android SDK could upgrade, but this is a feature they should upgrade to compete with iOS.

I have been using Android SDK for about ten years now. I started developing from KitKat, Lollipop, Marshmallow, and Nougat, version 7.0.

Android SDK is very stable.

The solution is very scalable because it's open-source. As a software engineer, you can analyze libraries in the SDK and customize the SDK to do what you want after downloading it. You can go deeper and explore the solution, and that's why many companies use Android.

The initial setup is easy. You have to go to Android Studio and download the SDK, and once you have downloaded the SDK, you can open Android Studio and import it.

Sometimes, Android Studio automatically picks the SDK up because of the location, and the setup becomes very slow because Android SDK is very large. It takes a long time and consumes high Internet bandwidth, especially when installing heavy features like the solution's graphic features.

Android SDK is on-premises, but it can also work on the cloud. Working on-premises, you can download Android SDK locally into Android Studio, integrate it into your IDE, and then start creating projects. SDK can be downloaded and packaged with Android Studio. SDK is also on the cloud because there are functionalities and libraries you can download into SDK from Google Cloud. For instance, after downloading and installing SDK from the cloud, you need the Internet to access the cloud to install the Android version you want.

To download the version you want, select SDK in your IDE, where all the versions will be listed, and then download the version you want locally.

You don't need to contact customer support because they have built many communities around Android SDK. If you want to know anything, it is better to use Google, ChatGPT, or whatever you want to use, and you can get information from Stack Overflow. The community is so big that once you start developing with Android SDK, you can use YouTube to resolve any error. Copy the error onto Google, and you will receive answers immediately.

If you wanted to use Android SDK, I would recommend it to you directly because I've seen it work, I've seen it do magic, and there are many applications I have built singlehandedly, and Android SDK is one of the reasons why I am where I am today.

Android SDK has almost all the features any smart technology can have. It has AI, biometrics, facial recognition, and voice recognition. There's nothing you cannot do with Android SDK. They are still upgrading the SDK, but the current one supports any application. Moreover, Android applications and the SDK can be automatically rewritten. For example, I can buy an Android phone today or a machine that supports Android technology, and using DOS, I can write a whole Android OS on SDK directly into the phone. When I reboot the phone, it will come up with all the icons. So they have given room for you to do anything, which is why I recommend them.

I give the solution an overall rating of ten out of ten.

We use the product to manage digital payments for our mobile application.

It is an Android platform which has a global reach. Additionally, the Near Field Communication feature is its most valuable feature.

We encounter compatibility issues between the product and the device from the manufacturer. There are some limitations on Google Play Store availability as well. These particular areas need improvement.

We have been using Android SDK for ten years.

I rate Android SDK's stability an eight out of ten.

We have two Android SDK users in our organization. I rate its scalability an eight out of ten.

The initial setup is very easy. It requires knowledge of software installation. Although, they have good documentation that simplifies the process for non-IT people.

It is an open-source platform.

I rate Android SDK a nine out of ten. I advise others about starting an application development project to refer to Google documentation for easier understanding.

I use Android SDK for development and as a library.

Android SDK's best feature is its ease of use.

Google has a monopoly on tools for Android app development, so Android SDK is the only choice available.

I've been using Android SDK for five to six years.

Android SDK is stable.

The initial setup is easy - it can be done with a single key press.

I would rate Android SDK eight out of ten.

We have around 40 developers in the company and we are users of this product. 

The best thing about Android SDK is that it supports a lot of devices. It supports mobile devices as well as IOT devices. Once you learn Android, it can be developed for many solutions like TV and applications for set top boxes.

There are security issues in the Android platform, so it is more vulnerable to attack. So that is something that is known to Google as well, right? So compared to Apple. 

I've been using this product for several years. 

The solution is stable. 

We haven't needed any technical support because once the software is released, it has its own documentation. Google releases all the details and there's a huge community out there. 

The initial setup is moderately complex. 

The product is open source. 

The Apple operating system is slightly different from Android because the Apple ecosystem is container-based, so each application is a container of its own. It has its own sandbox, which makes it very difficult for an attacker to get into the sandbox of an application. There's an architectural difference between iOS and Android.

I rate this product nine out of 10. 

We use the Android SDK for our application development, and our customers are looking for a mobile application for their Android phones. So we use the Android SDK to develop the application. There are no other alternatives to Android SDK and the performance is good.

It is a fantastic platform for the development of native applications. The look, ease of use, sturdiness, and reliability are excellent.

It is an excellent solution, and it would be nice to get fewer updates.

We used this solution for about four months. It is deployed on-premises. Android SDK has to be on-premises and cannot be on cloud. Although SDK is on-premises, you need to install it and then use it in your development.

It is a stable solution.

Scalability isn't applicable for this solution because it's a mobile application platform. We also have a lot of customers who all have to use the Android SDK.

We've never needed technical support, so we have not used them before.

The initial setup is straightforward, and there is a set procedure for installing the solution. There is no deployment with Android SDK. The SDK needs to be downloaded on a local machine and used in an application.

There is no licensing because it is open source.

I rate this solution an eight out of ten because no solution is perfect. 

We are using Android SDK for commercial purposes to develop file applications for healthcare and eCommerce. Additionally, we develop applications related to customer support, et cetera.

I have found the functions related to the services to the community for applications to be the most valuable.

The development environment of Android SDK could improve.

There could be some work done on privacy control. The interactions between application to application, which collecting data should be known to the users that the application is collecting data, or requesting to collect the data from the patient invoice.

I have been using Android SDK for approximately seven years.

The current releases of Android SDK are scalable.

The solution is highly scalable. 

I rate Android SDK a ten out of ten for scalability.

I am searching the internet community support for solutions to issues and I am using Stack Overflow and GitHub for resolving some issues.

The initial setup is easy, but for production equipment, it's complex. The process could be simplified.

I am using the free version of Android SDK.

I rate Android SDK an eight out of ten.

The SDK controls and real time connectivity with the handheld devices.

It helps fast development and debugging.

The simulator comes up pretty slow. In the real time agile environment the simulator is not efficient to launch quickly and has some drawback in receiving the push notification. Also working on the actual device has a pretty good than having simulator not simulate the hand held device.

Four years.

The simulator some times hags and needed to be restarted.

No doubt about the customer service its always great.

Yes. PhoneGap and Kony for development.

For strictly native applications, use Android.

For an application easily deployable on any platform like iOS or Windows, look for the PhoneGap solution.

- Open source SDK is a boon for developers, especially those who like to customize the underlying kernel/OS to suit their needs.
- UI development through the XML template, is very comfortable for beginners.
- Multiple platform support e.g. can be run on Windows, Linux, as well as Macintosh.
- Can be very easily integrated with 3rd party open source libraries
- Thriving user community helps get answers to your queries.
- A large number of supported third party libraries available.
- Supports one of the most popular IDE Eclipse

- Initial loading of emulator takes a lot of time
- Developing apps for tablets is comparatively difficult because the emulator is extremely slow
- Since all the applications need to be developed from scratch, as there is no template available, SDK is not suitable and requires use of various 3rd party libraries that provide ready to use APIs.
- Developing apps based on GPS, video camera, location, etc. cannot be very easily tested on the emulator and require an actual device.

A very good mobile app development platform with support for developing on various platforms like Wiindows, Linux, Mac, etc. Very good support for integrating 3rd party libraries. Development of apps based on camera, location, maps, etc. requires an actual device to test the app and the supplied emulator cannot be relied on completely.