Android SDK vs TypeScript

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Android SDK
Android SDK

6.9K
4.9K
+ 1
774
TypeScript
TypeScript

10.3K
7.6K
+ 1
400
Add tool

Android SDK vs TypeScript: What are the differences?

What is Android SDK? 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.

What is TypeScript? A superset of JavaScript that compiles to clean JavaScript output. TypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript.

Android SDK belongs to "Frameworks (Full Stack)" category of the tech stack, while TypeScript can be primarily classified under "Templating Languages & Extensions".

"Android development", "Necessary for android" and "Android studio" are the key factors why developers consider Android SDK; whereas "More intuitive and type safe javascript", "Type safe" and "JavaScript superset" are the primary reasons why TypeScript is favored.

TypeScript is an open source tool with 50.5K GitHub stars and 6.98K GitHub forks. Here's a link to TypeScript's open source repository on GitHub.

According to the StackShare community, TypeScript has a broader approval, being mentioned in 954 company stacks & 1390 developers stacks; compared to Android SDK, which is listed in 1071 company stacks and 878 developer stacks.

- No public GitHub repository available -

What is Android SDK?

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

What is TypeScript?

TypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Android SDK?
Why do developers choose TypeScript?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      Jobs that mention Android SDK and TypeScript as a desired skillset
      What companies use Android SDK?
      What companies use TypeScript?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Android SDK?
      What tools integrate with TypeScript?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Android SDK and TypeScript?
      Android Studio
      Android Studio is a new Android development environment based on IntelliJ IDEA. It provides new features and improvements over Eclipse ADT and will be the official Android IDE once it's ready.
      Ionic
      Free and open source, Ionic offers a library of mobile and desktop-optimized HTML, CSS and JS components for building highly interactive apps. Use with Angular, React, Vue, or plain JavaScript.
      React Native
      React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native.
      Flutter
      Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android.
      Xamarin
      Xamarin’s Mono-based products enable .NET developers to use their existing code, libraries and tools (including Visual Studio*), as well as skills in .NET and the C# programming language, to create mobile applications for the industry’s most widely-used mobile devices, including Android-based smartphones and tablets, iPhone, iPad and iPod Touch.
      See all alternatives
      Decisions about Android SDK and TypeScript
      Eli Hooten
      Eli Hooten
      CTO at Codecov · | 11 upvotes · 51.4K views
      atCodecovCodecov
      Visual Studio Code
      Visual Studio Code
      Vue.js
      Vue.js
      CoffeeScript
      CoffeeScript
      JavaScript
      JavaScript
      TypeScript
      TypeScript

      We chose TypeScript at Codecov when undergoing a recent rewrite of a legacy front end. Our previous front end was a mishmash of vanilla JavaScript and CoffeeScript , and was expanded upon haphazardly as the need arose. Without a unifying set of paradigms and patterns, the CoffeeScript and JavaScript setup was proving hard to maintain and expand upon by an engineering team. During a move to Vue.js , we decided to also make the move to TypeScript. Integrating TypeScript and Vue.js is fairly well understood at this point, so the setup wasn't all that difficult, and we felt that the benefits of incorporating TypeScript would outweigh the required time to set it up and get our engineering team up to speed.

      Choosing to add TypeScript has given us one more layer to rely on to help enforce code quality, good standards, and best practices within our engineering organization. One of the biggest benefits for us as an engineering team has been how well our IDEs and editors (e.g., Visual Studio Code ) integrate with and understand TypeScript . This allows developers to catch many more errors at development time instead of relying on run time. The end result is safer (from a type perspective) code and a more efficient coding experience that helps to catch and remove errors with less developer effort.

      See more
      Befmatic
      Befmatic
      Android SDK
      Android SDK
      Cocoa Touch (iOS)
      Cocoa Touch (iOS)
      Fabric by Twitter
      Fabric by Twitter
      Crashlytics
      Crashlytics

      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.

      See more
      React Native
      React Native
      Java
      Java
      Flow (JS)
      Flow (JS)
      TypeScript
      TypeScript

      I use TypeScript for Web Applications and for both frontend and backend because it has a lot of tooling around it and they really got the types and type safety right. Flow (JS) on the other hand lacks tooling and most of the times I scramble to find the right way of building my contracts in which TypeScript is very intuitive and natural. Additionally TypeScript is very similar to Java so your backend engineers and full stack engineers can work with it without much of context switch.

      The only time I think Flow shines is (based on probably my outdated knowledge) Flow is/was the only option if you want/wanted to build a React Native application mainly because React Native transpiler at the time I was working with it would only work with flow.

      See more
      Jarvis Stubblefield
      Jarvis Stubblefield
      Flow (JS)
      Flow (JS)
      TypeScript
      TypeScript

      I use TypeScript because it isn't just about validating the types I'm expecting to receive though that is a huge part of it too. Flow (JS) seems to be a type system only. TypeScript also allows you to use the latest features of JavaScript while also providing the type checking. To be fair to Flow (JS), I have not used it, but likely wouldn't have due to the additional features I get from TypeScript.

      See more
      David Koblas
      David Koblas
      VP Engineering at Payment Rails · | 9 upvotes · 6.6K views
      atPayment RailsPayment Rails
      TypeScript
      TypeScript
      Flow (JS)
      Flow (JS)
      JavaScript
      JavaScript

      We originally (in 2017) started rewriting our platform from JavaScript to Flow (JS) but found the library support for Flow was lacking. After switching gears to TypeScript we've never looked back. At this point we're finding that frontend and backend libraries are supporting TypeScript out of the box and where the support is missing that the commuity is typically got a solution in hand.

      See more
      Forrest Norvell
      Forrest Norvell
      engineering manager at self-employed · | 6 upvotes · 10K views
      Visual Studio Code
      Visual Studio Code
      Flow (JS)
      Flow (JS)
      ESLint
      ESLint
      TSLint
      TSLint
      TypeScript
      TypeScript

      I use TypeScript because the tooling is more mature (the decision to discontinue TSLint in favor of moving all its checks to ESLint is a thoughtful and mature decision), there's a ton of examples and tutorials for it, and it just generally seems to be where the industry is headed. Flow (JS) is a fine tool, but it just hasn't seen the uptake that TS has, and as a result is lacking a lot of the nicer small things, like thorough Visual Studio Code integration, offered by TS.

      See more
      Tomáš Pustelník
      Tomáš Pustelník
      Visual Studio Code
      Visual Studio Code
      Flow (JS)
      Flow (JS)
      TypeScript
      TypeScript

      We currently use TypeScript at work. Previously we used Flow (JS) but it was sometimes really difficult to make the types work the way you want. Especially non-trivial types were problematic. And the IDE support wasn't good, Flow took too much resources and sometimes remain stuck and do not show errors (I use Visual Studio Code). With TypeScript we almost do not have these problems. IDE support is superb, working with types is much easier and typing system seems more mature and powerful. There are some downsides (like partion inheritance etc.), but TS team is still pushing it forward. So for me TypeScript is clear winner.

      See more
      JavaScript
      JavaScript
      Flow (JS)
      Flow (JS)
      TypeScript
      TypeScript

      If you will start a project from scratch I recommend to use TypeScript. But, If you work with legacy projects written in JavaScript I recommend Flow (JS). Both tools have the same objective: reduce the bad code (which create illegible code, generate bugs e problems to maintenance). Flex helps you to avoid fall in bad codes, but TypeScript prevent you to c you to create bad codes. I believe cause this some JavaScript fans don't like TS, because TS block you to write some types o code. This is the fundamental difference between TS and Flow: Flow avoid problems, but no force. TS force you to prevent problems.

      See more
      .NET Core
      .NET Core
      React
      React
      AngularJS
      AngularJS
      TypeScript
      TypeScript

      I use TypeScript because it's adoption by many developers, it's supported by many companies, and it's growth. AngularJS, React, @ASP.NET Core. I started using it in .NET Core, then for a job. Later I added more Angular experience and wrote more React software. It makes your code easier to understand and read... which means it makes other people's code easier to understand and read.

      See more
      TypeScript
      TypeScript

      I use TypeScript because:

      • incredible developer tooling and community support
      • actively developed and supported by Microsoft (yes, I like Microsoft) ;)
      • easier to make sense of a TS codebase because the annotations provide so much more context than plain JS
      • refactors become easier (VSCode has superb support for TS)

      I've switched back and forth between TS and Flow and decided a year ago to abandon Flow completely in favor of TS. I don't want to bash Flow, however, my main grievances are very poor tooling (editor integration leaves much to be desired), a slower release cycle, and subpar docs and community support.

      See more
      Gustavo Muñoz
      Gustavo Muñoz
      Web UI Developer at Globant · | 2 upvotes · 5K views
      CoffeeScript
      CoffeeScript
      JavaScript
      JavaScript
      Flow (JS)
      Flow (JS)
      React
      React
      TypeScript
      TypeScript
      Angular 2
      Angular 2
      #ECMA
      #Angular

      Long ago when Angular 2 evolved I had to decide between the new #Angular and TypeScript or React. I really love typing my code, but forced to use TypeScript was a bit too much. I prefer the new #ECMA standard and the evolution of the old and reliable JavaScript. So finding Flow (JS) was an incredible milestone in my career as a developer. Finally, I could use types in my code, and JavaScript with the new standard. I already had the experience of CoffeeScript, so TypeScript was not an option.

      See more
      Flow (JS)
      Flow (JS)
      JavaScript
      JavaScript
      CoffeeScript
      CoffeeScript
      TypeScript
      TypeScript

      From a StackShare community member: "We are looking to rewrite our outdated front-end with TypeScript. Right now we have a mix of CoffeeScript and vanilla JavaScript. I have read that adopting TypeScript can help enforce better code quality, and best practices. I also heard good things about Flow (JS). Which one would you recommend and why?"

      See more
      Jason Barry
      Jason Barry
      Cofounder at FeaturePeek · | 4 upvotes · 9.1K views
      atFeaturePeekFeaturePeek
      npm
      npm
      Yarn
      Yarn
      Babel
      Babel
      Sublime Text
      Sublime Text
      JavaScript
      JavaScript
      React
      React
      TypeScript
      TypeScript
      Flow (JS)
      Flow (JS)
      #Frontend

      I think our #Frontend stack is pretty standard – but we have taken some deviations from a typical modern stack:

      • Flow (JS) instead of TypeScript. Flow was an easy choice 2+ years ago, as both flow and React were (and still are) maintained by Facebook. Today, it seems that the JavaScript community has settled on TypeScript as the winner. For new projects, I'd choose TS, but I don't see the point in migrating an existing project from flowtype to TS, when the end result will be roughly the same. Sure, memory usage is a bit high, and every now and then I have to kill some zombie processes, but our text editors (Sublime Text), CI scripts, and Babel are already set up to take advantage of the type safety that flow offers. When/if the React team writes React itself in TS, then I'll take a closer look – until then, flow works for us.

      • Yarn instead of npm. When yarn debuted, we never looked back. Now npm has pretty much caught up with speed and lockfiles, but yarn gives me confidence that my dependency installs are deterministic. Really interested in the plug-n-play (PnP) feature that removes the need for a node_modules folder, but haven't implemented this yet.

      See more
      Interest over time
      Reviews of Android SDK and TypeScript
      Avatar of lpellegr
      Noticeable
      Review ofTypeScriptTypeScript

      Typed JavaScript is just fantastic for medium to large size projects. The type system is well thought and compatible with standard JavaScript. Almost any new Javascript-based development should use TypeScript to save time and prevent technical debt over time.

      How developers use Android SDK and TypeScript
      Avatar of NewCraft
      NewCraft uses TypeScriptTypeScript

      Typescript has been a win because, in general, it makes codebase maintenance less brittle. It's significantly easier to refactor in TS than JS, which encourages incremental improvements, file re-organizing, etc. Our developers are happier with the overall development experience.

      The downside is that TS sometimes exacerbates problems caused by Node's fragmented ecosystem. Sometimes @types/ don't work, other times types are outdated. This can lead to problems with newly-installed libraries.

      If your project is big enough, I'd say TS is nearly always worth it, but it can make selecting libraries a pain.

      Avatar of Instacart
      Instacart uses Android SDKAndroid SDK

      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.

      Avatar of Matt Welke
      Matt Welke uses TypeScriptTypeScript

      Used for Node.js personal projects that I think will have a longer lifetime than others, or that are combined with a web front end component like Angular (to share types).

      Generally a poor developer experience. Usage decreasing recently compared to other preferred programming languages/platforms.

      Avatar of Marc3842h
      Marc3842h uses TypeScriptTypeScript

      TypeScript is used in Kuro (https://github.com/Marc3842h/kuro).

      Kuro is the browser facing portion of shiro. Typescript is the language in which the web server and the frontend scripts are written in. They later get compiled down to vanilla JavaScript.

      Avatar of Ana Phi Sancho
      Ana Phi Sancho uses Android SDKAndroid SDK

      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.

      Avatar of John Harris
      John Harris uses TypeScriptTypeScript

      Excellent design-time type checking and the ability for the Typescript compiler to attach typing information to metadata at compile time allows for relatively simple type checking at run-time as well.

      Avatar of Scrayos UG (haftungsbeschränkt)
      Scrayos UG (haftungsbeschränkt) uses Android SDKAndroid SDK

      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.

      Avatar of Blood Bot
      Blood Bot uses TypeScriptTypeScript

      We, our team can sleep comfortable at night know "x is undefined" will not occur in production. It's also really helpful as IDE help in code completion when they know types.

      Avatar of papaver
      papaver uses Android SDKAndroid SDK

      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.

      Avatar of Grupo Gamma Peninsular, SA de CV
      Grupo Gamma Peninsular, SA de CV uses Android SDKAndroid SDK

      Uso del Android SDK para el desarrollo de aplicaciones para Android con geolocalizaciĂłn, multimedia y almacenamiento en la base de datos.

      How much does Android SDK cost?
      How much does TypeScript cost?
      Pricing unavailable
      Pricing unavailable