Android SDK vs Play: What are the differences?
Developers describe Android SDK as "An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps for Android". Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment. On the other hand, Play is detailed as "The High Velocity Web Framework For Java and Scala". Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications.
Android SDK and Play belong to "Frameworks (Full Stack)" category of the tech stack.
"Android development", "Necessary for android" and "Android studio" are the key factors why developers consider Android SDK; whereas "Scala", "Web-friendly architecture" and "Built on akka" are the primary reasons why Play is favored.
Play is an open source tool with 11.2K GitHub stars and 3.77K GitHub forks. Here's a link to Play's open source repository on GitHub.
According to the StackShare community, Android SDK has a broader approval, being mentioned in 1083 company stacks & 905 developers stacks; compared to Play, which is listed in 112 company stacks and 47 developer stacks.
What is Android SDK?
What is Play?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Android SDK?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
When we first built the ArifZefen app our focus was around validating our business assumptions and finding a good product fit. Once we got to a few thousand users, it became clear that we needed to make quality a priority and that meant we needed a reliable tool that will allow us to monitor the health of our app. Crashlytics (now Fabric by Twitter ) was on a short list of solutions we closely explored and we were very happy with its ease of integration and the consistency it brought to our Cocoa Touch (iOS) and Android SDK crash monitoring.
Its daily pulse emails were also super informative in giving us a good sense of how each platform was doing in terms of crash-free and new users, daily actives and other relevant session data. These emails also surfaced any anomalies in daily trends, alerting us of any reason for concern. Overall, Crashlytics was instrumental in allowing us to quickly discover and diagnose crashes and it is one of the main reasons we were able to keep our app store ratings reasonable high. But perhaps even more importantly, we were able to set a high quality bar for our users that absent Crashlytics would have been difficult to maintain.
Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?
So we very, very early on, we were iOS only, then we thought, well we’re missing out on half of the market. We need to add Android. So we had a friend of ours start working on the Android app, and I had to build the API for him, but I was having a really hard time doing that because I didn’t know what he needed exactly, so I built the first version of the web store over the weekend because I wanted to have a client to consume myself for the API I was building.
Play is a central framework/component/library (not sure what to call things these days) in Scala. We <3 Scala, and therefore we <3 Play.
Play is on of several frameworks we are prototyping and vetting for various public-facing websites, and may ultimately be the framework behind the main datapile.io website.
Self taught : acquired knowledge or skill on one's own initiative. Unity and app compatible porposes : software development kit that enables developers to create applications for the Android platform.
The Android SDK is the key-component of all Android-based development and had to be included in this stack for sure. We work with the SDK through IntelliJ IDEA and the command-line.
last time i used the android sdk was converting the tiktok app to ios. what a mess it was back then. the developer nature of the sdk was apparent vs apples offering.
I used Play to build a configuration UI for the service, which let you create and manage the menus (a hierarchical tree of options and actions).
Uso del Android SDK para el desarrollo de aplicaciones para Android con geolocalización, multimedia y almacenamiento en la base de datos.