Alternatives to Android SDK logo

Alternatives to Android SDK

Android Studio, Ionic, React Native, Flutter, and Xamarin are the most popular alternatives and competitors to Android SDK.
22.8K
17.7K
+ 1
787

What is Android SDK and what are its top alternatives?

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.
Android SDK is a tool in the Frameworks (Full Stack) category of a tech stack.
Android SDK is an open source tool with GitHub stars and GitHub forks. Here’s a link to Android SDK's open source repository on GitHub

Top Alternatives to Android SDK

  • Android Studio
    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
    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

    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

    Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android. ...

  • Xamarin
    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
    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

    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

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

Android SDK alternatives & related posts

Android Studio logo

Android Studio

21.6K
16.9K
355
Android development environment based on IntelliJ IDEA
21.6K
16.9K
+ 1
355
PROS OF ANDROID STUDIO
  • 173
    Android studio is a great tool, getting better and bet
  • 101
    Google's official android ide
  • 36
    Intelligent code editor with lots of auto-completion
  • 25
    Its powerful and robust
  • 5
    Easy creating android app
  • 3
    Amazing Layout Designer
  • 3
    Great Code Tips
  • 3
    Great tool & very helpful
  • 2
    Easy to use
  • 2
    Built in Emulator
  • 2
    Keyboard Shortcuts are Amazing Out of the box
CONS OF ANDROID STUDIO
  • 4
    Slow emulator
  • 4
    Huge memory usage
  • 2
    Complex for begginers
  • 2
    No checking incompatibilities
  • 1
    Using Intellij IDEA, while Intellij IDEA have too
  • 1
    Lags behind IntelliJ IDEA
  • 1
    Slow release process

related Android Studio posts

Gustavo Muñoz
Senior Software Engineer at JOOR · | 8 upvotes · 414K views

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.

See more
Julien DeFrance
Principal Software Engineer at Tophatter · | 8 upvotes · 383.8K views

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.

See more
Ionic logo

Ionic

8.3K
7.6K
1.7K
A beautiful front-end framework for developing cross-platform apps with web technologies like Angular and React.
8.3K
7.6K
+ 1
1.7K
PROS OF IONIC
  • 246
    Allows for rapid prototyping
  • 227
    Hybrid mobile
  • 208
    It's angularjs
  • 185
    Free
  • 179
    It's javascript, html, and css
  • 108
    Ui and theming
  • 76
    Great designs
  • 74
    Mv* pattern
  • 70
    Reuse frontend devs on mobile
  • 65
    Extensibility
  • 31
    Great community
  • 29
    Open source
  • 22
    Responsive design
  • 20
    Good cli
  • 13
    So easy to use
  • 13
    Beautifully designed
  • 13
    Angularjs-based
  • 12
    Widgets
  • 11
    Typescript
  • 11
    Allows for rapid prototyping, hybrid mobile
  • 10
    Quick prototyping, amazing community
  • 10
    Easy setup
  • 8
    Angular2 support
  • 7
    Base on angular
  • 7
    So much thought behind what developers actually need
  • 7
    Because of the productivity and easy for development
  • 7
    Fast, easy, free
  • 6
    Super fast, their dev team is amazingly passionate
  • 6
    Easy to use
  • 6
    It's Angular
  • 4
    Hot deploy
  • 4
    UI is awesome
  • 3
    Amazing support
  • 3
    Easy setup, development and testing
  • 3
    Material design support using theme
  • 3
    It's the future
  • 3
    Angular
  • 3
    Allow for rapid prototyping
  • 3
    Ionic creator
  • 2
    User Friendly
  • 2
    It's angular js
  • 2
    Complete package
  • 2
    Simple & Fast
  • 2
    Removes 300ms delay in mobile browsers
  • 2
    Fastest growing mobile app framework
  • 2
    Best Support and Community
  • 2
    Material Design By Default
  • 2
    Cross platform
  • 2
    Documentation
  • 2
    Because I can use my existing web devloper skills
  • 1
    Ionic conect codeigniter
  • 1
    Fast Prototyping
  • 1
    All Trending Stack
  • 1
    Native access
  • 1
    Typescript support
CONS OF IONIC
  • 20
    Not suitable for high performance or UI intensive apps
  • 15
    Not meant for game development
  • 2
    Not a native app

related Ionic posts

Saber Hosney
Senior software engineer at Shortcut · | 7 upvotes · 152.8K views

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!

See more
Melanie Verstraete
Shared insights
on
IonicIonicFlutterFlutter

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!

See more
React Native logo

React Native

27.8K
24.2K
1.1K
A framework for building native apps with React
27.8K
24.2K
+ 1
1.1K
PROS OF REACT NATIVE
  • 207
    Learn once write everywhere
  • 168
    Cross platform
  • 165
    Javascript
  • 120
    Native ios components
  • 67
    Built by facebook
  • 63
    Easy to learn
  • 44
    Bridges me into ios development
  • 40
    It's just react
  • 39
    No compile
  • 36
    Declarative
  • 22
    Fast
  • 13
    Virtual Dom
  • 12
    Insanely fast develop / test cycle
  • 12
    Livereload
  • 11
    Great community
  • 9
    It is free and open source
  • 9
    Native android components
  • 9
    Easy setup
  • 9
    Backed by Facebook
  • 7
    Highly customizable
  • 7
    Scalable
  • 6
    Awesome
  • 6
    Everything component
  • 6
    Great errors
  • 6
    Win win solution of hybrid app
  • 5
    Not dependent on anything such as Angular
  • 5
    Simple
  • 4
    Awesome, easy starting from scratch
  • 4
    OTA update
  • 3
    As good as Native without any performance concerns
  • 3
    Easy to use
  • 2
    Many salary
  • 2
    Can be incrementally added to existing native apps
  • 2
    Hot reload
  • 2
    Over the air update (Flutter lacks)
  • 2
    'It's just react'
  • 2
    Web development meets Mobile development
  • 1
    Ngon
CONS OF REACT NATIVE
  • 23
    Javascript
  • 18
    Built by facebook
  • 12
    Cant use CSS
  • 4
    30 FPS Limit
  • 2
    Generate large apk even for a simple app
  • 2
    Some compenents not truly native
  • 2
    Slow

related React Native posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 2.1M views

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.

See more

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.

See more
Flutter logo

Flutter

12K
12.1K
1.1K
Cross-platform mobile framework from Google
12K
12.1K
+ 1
1.1K
PROS OF FLUTTER
  • 127
    Hot Reload
  • 106
    Cross platform
  • 98
    Performance
  • 82
    Backed by Google
  • 69
    Compiled into Native Code
  • 54
    Fast Development
  • 54
    Open Source
  • 49
    Fast Prototyping
  • 44
    Expressive and Flexible UI
  • 43
    Single Codebase
  • 35
    Reactive Programming
  • 31
    Material Design
  • 26
    Widget-based
  • 25
    Dart
  • 24
    Target to Fuchsia
  • 17
    IOS + Android
  • 14
    Easy to learn
  • 14
    Great CLI Support
  • 13
    Tooling
  • 13
    You can use it as mobile, web, Server development
  • 12
    Have built-in Material theme
  • 11
    Target to Android
  • 11
    Good docs & sample code
  • 11
    Community
  • 11
    Debugging quickly
  • 10
    Support by multiple IDE: Android Studio, VS Code, XCode
  • 9
    Easy Testing Support
  • 9
    Written by Dart, which is easy to read code
  • 8
    Target to iOS
  • 8
    Real platform free framework of the future
  • 8
    Have built-in Cupertino theme
  • 7
    Easy to Unit Test
  • 7
    Easy to Widget Test
CONS OF FLUTTER
  • 28
    Need to learn Dart
  • 10
    No 3D Graphics Engine Support
  • 9
    Lack of community support
  • 7
    Graphics programming
  • 6
    Lack of friendly documentation
  • 2
    Lack of promotion
  • 1
    Https://iphtechnologies.com/difference-between-flutter

related Flutter posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 2.1M views

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.

See more
Shared insights
on
DartDartFlutterFlutter

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

See more
Xamarin logo

Xamarin

1.2K
1.5K
783
Create iOS, Android and Mac apps in C#
1.2K
1.5K
+ 1
783
PROS OF XAMARIN
  • 121
    Power of c# on mobile devices
  • 81
    Native performance
  • 78
    Native apps with native ui controls
  • 72
    No javascript - truely compiled code
  • 67
    Sharing more than 90% of code over all platforms
  • 45
    Ability to leverage visual studio
  • 44
    Mvvm pattern
  • 44
    Many great c# libraries
  • 36
    Amazing support
  • 34
    Powerful platform for .net developers
  • 19
    GUI Native look and Feel
  • 16
    Nuget package manager
  • 12
    Free
  • 9
    Enables code reuse on server
  • 9
    Backed by Microsoft
  • 8
    Faster Development
  • 7
    Best performance than other cross-platform
  • 7
    Use of third-party .NET libraries
  • 7
    Easy Debug and Trace
  • 7
    Open Source
  • 7
    It's free since Apr 2016
  • 6
    Xamarin.forms is the best, it's amazing
  • 6
    Mac IDE (Xamarin Studio)
  • 5
    That just work for every scenario
  • 5
    Power of C#, no javascript, visual studio
  • 5
    C# mult paradigm language
  • 4
    Microsoft stack
  • 4
    Great docs
  • 4
    Compatible to develop Hybrid apps
  • 4
    Microsoft backed
  • 3
    Small learning curve for Mobile developers
  • 3
    Well Designed
  • 2
    Ability to leverage legacy C and C++
  • 2
    Ionic
CONS OF XAMARIN
  • 9
    Build times
  • 5
    Visual Studio
  • 3
    Complexity
  • 3
    Scalability
  • 3
    Price
  • 2
    Nuget
  • 2
    Maturity
  • 2
    Build Tools
  • 2
    Support
  • 0
    Maturidade
  • 0
    Performance

related Xamarin posts

Greg Neumann

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...

See more
William Miller

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.

See more
Corona SDK logo

Corona SDK

15
32
4
Cross-platform development platform for 2D apps and games
15
32
+ 1
4
PROS OF CORONA SDK
  • 2
    Also potentially build for OS Apple
  • 2
    Lua code better than java code
CONS OF CORONA SDK
  • 4
    Not Very popular
  • 2
    Very Poor System

related Corona SDK posts

Node.js logo

Node.js

153.5K
129.6K
8.5K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
153.5K
129.6K
+ 1
8.5K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 801
    Open source
  • 485
    Great for apis
  • 475
    Asynchronous
  • 420
    Great community
  • 390
    Great for realtime apps
  • 295
    Great for command line utilities
  • 81
    Node Modules
  • 81
    Websockets
  • 68
    Uber Simple
  • 59
    Great modularity
  • 58
    Allows us to reuse code in the frontend
  • 42
    Easy to start
  • 35
    Great for Data Streaming
  • 32
    Realtime
  • 28
    Awesome
  • 25
    Non blocking IO
  • 18
    Can be used as a proxy
  • 17
    High performance, open source, scalable
  • 16
    Non-blocking and modular
  • 15
    Easy and Fun
  • 14
    Easy and powerful
  • 13
    Same lang as AngularJS
  • 13
    Future of BackEnd
  • 12
    Fullstack
  • 11
    Fast
  • 10
    Scalability
  • 10
    Cross platform
  • 9
    Simple
  • 8
    Mean Stack
  • 7
    Easy concurrency
  • 7
    Great for webapps
  • 6
    Fast, simple code and async
  • 6
    Typescript
  • 6
    Friendly
  • 6
    React
  • 5
    Fast development
  • 5
    Control everything
  • 5
    Great speed
  • 5
    Scalable
  • 5
    Easy to use and fast and goes well with JSONdb's
  • 5
    Its amazingly fast and scalable
  • 4
    Isomorphic coolness
  • 4
    It's fast
  • 4
    Easy to use
  • 3
    Not Python
  • 3
    Less boilerplate code
  • 3
    One language, end-to-end
  • 3
    Scales, fast, simple, great community, npm, express
  • 3
    TypeScript Support
  • 3
    Sooper easy for the Backend connectivity
  • 3
    Performant and fast prototyping
  • 3
    Great community
  • 3
    Easy
  • 3
    Easy to learn
  • 3
    Blazing fast
  • 2
    Lovely
  • 2
    Event Driven
  • 2
    Npm i ape-updating
  • 0
    Node
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 43
    New framework every day
  • 37
    Lots of terrible examples on the internet
  • 31
    Asynchronous programming is the worst
  • 23
    Callback
  • 18
    Javascript
  • 11
    Dependency hell
  • 11
    Dependency based on GitHub
  • 10
    Low computational power
  • 7
    Very very Slow
  • 7
    Can block whole server easily
  • 6
    Callback functions may not fire on expected sequence
  • 3
    Unneeded over complication
  • 3
    Unstable
  • 3
    Breaking updates
  • 2
    No standard approach
  • 1
    Bad transitive dependency management
  • 1
    Can't read server session

related Node.js posts

Nick Rockwell
SVP, Engineering at Fastly · | 44 upvotes · 2.1M views

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.

See more
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.3M views

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

See more
Django logo

Django

31.8K
28.6K
4K
The Web framework for perfectionists with deadlines
31.8K
28.6K
+ 1
4K
PROS OF DJANGO
  • 649
    Rapid development
  • 478
    Open source
  • 411
    Great community
  • 364
    Easy to learn
  • 270
    Mvc
  • 221
    Beautiful code
  • 215
    Elegant
  • 198
    Free
  • 196
    Great packages
  • 184
    Great libraries
  • 73
    Restful
  • 71
    Comes with auth and crud admin panel
  • 71
    Powerful
  • 67
    Great documentation
  • 63
    Great for web
  • 51
    Python
  • 39
    Great orm
  • 37
    Great for api
  • 28
    All included
  • 25
    Fast
  • 23
    Web Apps
  • 20
    Used by top startups
  • 20
    Clean
  • 19
    Easy setup
  • 17
    Sexy
  • 14
    Convention over configuration
  • 13
    ORM
  • 13
    Allows for very rapid development with great libraries
  • 12
    The Django community
  • 10
    King of backend world
  • 9
    Great MVC and templating engine
  • 7
    Full stack
  • 7
    Batteries included
  • 7
    Its elegant and practical
  • 6
    Have not found anything that it can't do
  • 6
    Very quick to get something up and running
  • 6
    Cross-Platform
  • 6
    Fast prototyping
  • 6
    Mvt
  • 5
    Zero code burden to change databases
  • 5
    Easy Structure , useful inbuilt library
  • 5
    Easy to develop end to end AI Models
  • 4
    Map
  • 4
    Easy to change database manager
  • 4
    Easy
  • 4
    Great peformance
  • 4
    Many libraries
  • 4
    Python community
  • 4
    Modular
  • 4
    Easy to use
  • 3
    Just the right level of abstraction
  • 3
    Scaffold
  • 3
    Full-Text Search
  • 1
    Scalable
  • 1
    Node js
  • 0
    Rails
  • 0
    Fastapi
CONS OF DJANGO
  • 25
    Underpowered templating
  • 22
    Autoreload restarts whole server
  • 21
    Underpowered ORM
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 8
    Not nodejs
  • 7
    Admin
  • 7
    Configuration hell
  • 5
    Not as clean and nice documentation like Laravel
  • 3
    Bloated admin panel included
  • 3
    Python
  • 3
    Not typed
  • 2
    InEffective Multithreading
  • 2
    Overwhelming folder structure

related Django posts

Dmitry Mukhin

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.

See more

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?

See more