What is Android SDK and what are its top alternatives?
Top Alternatives to Android SDK
- 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. ...
- Corona SDK
It is a cross-platform framework ideal for rapidly creating apps and games for mobile devices and desktop systems. It builds rich mobile apps for iOS, Android, Kindle and Nook. Build high quality mobile apps in a fraction of the time. ...
- Node.js
Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...
- Django
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...
Android SDK alternatives & related posts
- Android studio is a great tool, getting better and bet173
- Google's official android ide101
- Intelligent code editor with lots of auto-completion36
- Its powerful and robust25
- Easy creating android app5
- Amazing Layout Designer3
- Great Code Tips3
- Great tool & very helpful3
- Built in Emulator2
- Easy to use2
- Keyboard Shortcuts are Amazing Out of the box2
- Cc1
- Slow emulator4
- Huge memory usage4
- Complex for begginers2
- No checking incompatibilities2
- Using Intellij IDEA, while Intellij IDEA have too1
- Lags behind IntelliJ IDEA1
- Slow release process1
related Android Studio posts
In my modest opinion, Flutter is the future of mobile development. The framework is as important to mobile as React is to the web. And seeing that React Native does not finish taking off, I am focusing all my efforts on learning Flutter and Dart. The ecosystem is amazing. The community is crazy about Flutter. There are enough resources to learn and enjoy the framework, and the tools developed to work with it are amazing. Android Studio or Visual Studio Code has incredible plugins and Dart is a pretty straight forward and easy-to-learn language, even more, if you came from JavaScript. I admit it. I'm in love with Flutter. When you are not a designer, having a framework focused on design an pretty things is a must. And counting with tools like #flare for animations makes everything easier. It is so amazing that I wish I had a big mobile project right now at work just to use Flutter.
As a Engineering Manager & Director at SmartZip, I had a mix of front-end, back-end, #mobile engineers reporting to me.
Sprints after sprints, I noticed some inefficiencies on the MobileDev side. People working multiple sprints in a row on their Xcode / Objective-C codebase while some others were working on Android Studio. After which, QA & Product ensured both applications were in sync, on a UI/UX standpoint, creating addional work, which also happened to be extremely costly.
Our resources being so limited, my role was to stop this bleeding and keep my team productive and their time, valuable.
After some analysis, discussions, proof of concepts... etc. We decided to move to a single codebase using React Native so our velocity would increase.
After some initial investment, our initial assumptions were confirmed and we indeed started to ship features a lot faster than ever before. Also, our engineers found a way to perform this upgrade incrementally, so the initial platform-specific codebase wouldn't have to entirely be rewritten at once but only gradually and at will.
Feedback around React Native was very positive. And I doubt - for the kind of application we had - no one would want to go back to two or more code bases. Our application was still as Native as it gets. And no feature or device capability was compromised.
Ionic
- Allows for rapid prototyping246
- Hybrid mobile227
- It's angularjs208
- Free185
- It's javascript, html, and css179
- Ui and theming108
- Great designs76
- Mv* pattern74
- Reuse frontend devs on mobile70
- Extensibility65
- Great community31
- Open source29
- Responsive design22
- Good cli20
- So easy to use13
- Beautifully designed13
- Angularjs-based13
- Widgets12
- Typescript11
- Allows for rapid prototyping, hybrid mobile11
- Quick prototyping, amazing community10
- Easy setup10
- Angular2 support8
- So much thought behind what developers actually need7
- Because of the productivity and easy for development7
- Fast, easy, free7
- Base on angular7
- Super fast, their dev team is amazingly passionate6
- Easy to use6
- It's Angular6
- UI is awesome4
- Hot deploy4
- Material design support using theme3
- Amazing support3
- It's the future3
- Angular3
- Allow for rapid prototyping3
- Easy setup, development and testing3
- Ionic creator3
- User Friendly2
- It's angular js2
- Complete package2
- Simple & Fast2
- Fastest growing mobile app framework2
- Best Support and Community2
- Material Design By Default2
- Cross platform2
- Documentation2
- Because I can use my existing web devloper skills2
- Removes 300ms delay in mobile browsers2
- 11
- Native access1
- Typescript support1
- Ionic conect codeigniter1
- Fast Prototyping1
- All Trending Stack1
- Not suitable for high performance or UI intensive apps20
- Not meant for game development15
- Not a native app2
related Ionic posts
Greetings!
I have been searching lately for frameworks to build mobile apps.
We are trying to make something like a quiz app as a way for customers to contact us. I considered Ionic and React Native because we use JavaScript most of the time in websites, e.g., Vue.js/Nuxt.js. But Flutter seems a decent choice as well, especially since you can use Android/iOS-like components. We are looking for something that works in the long term, something that's time and cost-effective, especially when paired with backend services like Firebase or a GraphQL server. I would like to know your opinions and recommendations. Thank you!
Hi community, I am looking into how I should build my tech stack for a business/analytics platform. I am not very familiar with frontend development; when looking into cross-platform frameworks, I found a lot of options. What is the best cross-platform frontend framework to go with? I found Flutter interesting, but Ionic also looks promising? Thank you for the advice!
- Learn once write everywhere204
- Cross platform166
- Javascript162
- Native ios components118
- Built by facebook67
- Easy to learn62
- Bridges me into ios development43
- It's just react40
- No compile39
- Declarative36
- Fast21
- Virtual Dom12
- Livereload12
- Insanely fast develop / test cycle11
- Great community10
- Easy setup9
- Backed by Facebook9
- It is free and open source9
- Native android components8
- Highly customizable7
- Scalable6
- Everything component6
- Awesome6
- Win win solution of hybrid app6
- Great errors6
- Not dependent on anything such as Angular5
- Simple5
- OTA update4
- Awesome, easy starting from scratch4
- Easy to use3
- As good as Native without any performance concerns3
- Web development meets Mobile development2
- Hot reload2
- Over the air update (Flutter lacks)2
- 'It's just react'2
- Many salary2
- Can be incrementally added to existing native apps2
- Nigger1
- Cons1
- Ngon1
- Ful0
- Javascript23
- Built by facebook18
- Cant use CSS12
- 30 FPS Limit4
- Slow2
- Some compenents not truly native2
- Generate large apk even for a simple app2
related React Native posts









I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.
















I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.
We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.
Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis for cache and other time sensitive operations.
We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.
Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.
- Hot Reload124
- Cross platform104
- Performance97
- Backed by Google80
- Compiled into Native Code66
- Fast Development52
- Open Source51
- Fast Prototyping46
- Expressive and Flexible UI43
- Single Codebase40
- Reactive Programming35
- Material Design30
- Widget-based24
- Target to Fuchsia23
- Dart23
- IOS + Android17
- Easy to learn14
- Tooling13
- You can use it as mobile, web, Server development13
- Great CLI Support13
- Good docs & sample code11
- Debugging quickly11
- Have built-in Material theme11
- Target to Android10
- Support by multiple IDE: Android Studio, VS Code, XCode10
- Community10
- Easy Testing Support9
- Written by Dart, which is easy to read code9
- Have built-in Cupertino theme8
- Target to iOS8
- Easy to Widget Test7
- Easy to Unit Test7
- Real platform free framework of the future7
- Flutter is awesome7
- F1
- Need to learn Dart28
- No 3D Graphics Engine Support10
- Lack of community support9
- Graphics programming7
- Lack of friendly documentation6
- Lack of promotion2
- Https://iphtechnologies.com/difference-between-flutter1
related Flutter posts









I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.
Hi, I'm considering building a social marketplace app on android, ios and web, Flutter seems to be a good UI framework for cross-platform apps, it's safe type, hot reload, and native compiling on native machine code (thanks to Dart). My question is, for an MVP product is it a good choice? if yes, will it be on the mid-term, long term? Or will I have to change as the users grow?
thank you
- Power of c# on mobile devices120
- Native performance80
- Native apps with native ui controls77
- No javascript - truely compiled code71
- Sharing more than 90% of code over all platforms67
- Ability to leverage visual studio45
- Many great c# libraries44
- Mvvm pattern43
- Amazing support36
- Powerful platform for .net developers34
- GUI Native look and Feel19
- Nuget package manager15
- Free11
- Backed by Microsoft9
- Enables code reuse on server9
- Faster Development8
- Easy Debug and Trace7
- Use of third-party .NET libraries7
- It's free since Apr 20167
- Best performance than other cross-platform7
- Open Source7
- Mac IDE (Xamarin Studio)6
- Xamarin.forms is the best, it's amazing6
- Power of C#, no javascript, visual studio5
- C# mult paradigm language5
- Compatible to develop Hybrid apps4
- Microsoft backed4
- Microsoft stack4
- Great docs4
- That just work for every scenario4
- Well Designed3
- Small learning curve for Mobile developers3
- Ability to leverage legacy C and C++2
- Ionic2
- Build times9
- Visual Studio5
- Complexity3
- Scalability3
- Price3
- Nuget2
- Maturity2
- Build Tools2
- Support2
- Maturidade0
- Performance0
related Xamarin posts
Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.
This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!
But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?
I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.
Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...












We are developing an AWS IoT app for large boats. The IoT devices have sensors all over the boat for engine oil pressure, position, water depth, fuel level, crew location, etc. When the boat has internet, we interact with AWS cloud using lambda and Amazon DynamoDB. When the boat is offshore, the captain and crew still need normal and emergency alerts and real-time sensor information. The crew might have an Android or IoS phone or a Windows or macOS PC to receive alerts and interact with sensors. We may use the AWS GreenGrasss edge computing solution and either MQTT or HTML for that function.
Question: We want to develop a cross-platform client to run on Windows, Mac, Android, IOS, and possibly Linux. We are primarily Python programmers, so PyQt or Kivy are options for us, but we have heard good things about React Native, Flutter, Xamarin, and others. We think an AWS Greengrass core on an RPI4 could communicate to the client with MQTT or a local webserver with a client web interface.
Any thoughts would be much appreciated.
- Also potentially build for OS Apple2
- Lua code better than java code2
- Not Very popular3
- Very Poor System2
related Corona SDK posts
Node.js
- Npm1.4K
- Javascript1.3K
- Great libraries1.1K
- High-performance1K
- Open source799
- Great for apis485
- Asynchronous475
- Great community420
- Great for realtime apps390
- Great for command line utilities295
- Websockets81
- Node Modules81
- Uber Simple68
- Great modularity59
- Allows us to reuse code in the frontend57
- Easy to start42
- Great for Data Streaming35
- Realtime32
- Awesome28
- Non blocking IO25
- Can be used as a proxy18
- High performance, open source, scalable17
- Non-blocking and modular16
- Easy and Fun15
- Easy and powerful14
- Future of BackEnd13
- Same lang as AngularJS13
- Fullstack12
- Fast11
- Scalability10
- Cross platform10
- Simple9
- Mean Stack8
- Great for webapps7
- Easy concurrency7
- Typescript6
- Fast, simple code and async6
- Friendly6
- React6
- Easy to use and fast and goes well with JSONdb's5
- Fast development5
- Control everything5
- Great speed5
- Scalable5
- Its amazingly fast and scalable5
- It's fast4
- Isomorphic coolness4
- Easy to use4
- Blazing fast3
- Easy to learn3
- Easy3
- Javascript23
- Great community3
- Not Python3
- Sooper easy for the Backend connectivity3
- TypeScript Support3
- Scales, fast, simple, great community, npm, express3
- One language, end-to-end3
- Less boilerplate code3
- Performant and fast prototyping3
- Lovely2
- Npm i ape-updating2
- Event Driven2
- Bound to a single CPU46
- New framework every day42
- Lots of terrible examples on the internet37
- Asynchronous programming is the worst29
- Callback23
- Javascript18
- Dependency based on GitHub11
- Dependency hell10
- Low computational power10
- Can block whole server easily7
- Very very Slow7
- Callback functions may not fire on expected sequence6
- Unneeded over complication3
- Unstable3
- Breaking updates3
- Bad transitive dependency management1
- Can't read server session1
- No standard approach1
related Node.js posts
When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?
So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.
React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.
Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.











How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:
Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.
Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:
https://eng.uber.com/distributed-tracing/
(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)
Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark
- Rapid development641
- Open source473
- Great community406
- Easy to learn357
- Mvc266
- Beautiful code217
- Elegant212
- Free196
- Great packages194
- Great libraries182
- Restful71
- Powerful67
- Comes with auth and crud admin panel67
- Great documentation64
- Great for web61
- Python48
- Great orm38
- Great for api36
- All included27
- Web Apps22
- Fast22
- Used by top startups19
- Clean17
- Easy setup16
- Sexy16
- Convention over configuration13
- ORM12
- Allows for very rapid development with great libraries9
- The Django community9
- Great MVC and templating engine7
- King of backend world7
- Its elegant and practical7
- Mvt6
- Full stack6
- Fast prototyping6
- Have not found anything that it can't do6
- Cross-Platform6
- Batteries included5
- Very quick to get something up and running5
- Easy Structure , useful inbuilt library5
- Easy to develop end to end AI Models5
- Python community4
- Great peformance4
- Easy4
- Easy to use4
- Modular4
- Many libraries4
- Full-Text Search3
- Map3
- Zero code burden to change databases3
- Scaffold3
- Just the right level of abstraction3
- Easy to change database manager2
- Node js1
- Asdasd0
- Rails0
- Aaaa0
- Fastapi0
- Underpowered templating25
- Autoreload restarts whole server21
- Underpowered ORM20
- URL dispatcher ignores HTTP method15
- Internal subcomponents coupling10
- Not nodejs7
- Configuration hell7
- Admin7
- Not as clean and nice documentation like Laravel5
- Bloated admin panel included3
- Not typed3
- Python3
- Overwhelming folder structure2
- InEffective Multithreading2
related Django posts
Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.
Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.
For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.
However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.
All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.
Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?