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.
16.9K
12.3K
+ 1
782

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鈥檚 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鈥檚 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鈥檚 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

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

related Android Studio posts

Gustavo Mu帽oz
Web UI Developer at Globant | 8 upvotes 路 351.2K 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 路 284.1K 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

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

related Ionic posts

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
Gaurav Patil
Software Developer at PLMTECH LOGIX Pvt. Ltd. | 3 upvotes 路 382.5K views

Which hybrid framework I should for my upcoming mobile application project?

Options: 1. Flutter 2. Ionic 3. React Native

See more
React Native logo

React Native

18.7K
15.7K
1.1K
A framework for building native apps with React
18.7K
15.7K
+ 1
1.1K
PROS OF REACT NATIVE
  • 197
    Learn once write everywhere
  • 159
    Cross platform
  • 158
    Javascript
  • 115
    Native ios components
  • 66
    Built by facebook
  • 60
    Easy to learn
  • 43
    Bridges me into ios development
  • 39
    It's just react
  • 39
    No compile
  • 36
    Declarative
  • 20
    Fast
  • 12
    Virtual Dom
  • 12
    Livereload
  • 10
    Insanely fast develop / test cycle
  • 9
    Great community
  • 9
    It is free and open source
  • 9
    Easy setup
  • 9
    Backed by Facebook
  • 8
    Native android components
  • 7
    Highly customizable
  • 6
    Awesome
  • 6
    Scalable
  • 6
    Great errors
  • 6
    Win win solution of hybrid app
  • 6
    Everything component
  • 5
    Simple
  • 5
    Not dependent on anything such as Angular
  • 4
    Awesome, easy starting from scratch
  • 4
    OTA update
  • 3
    Easy to use
  • 3
    As good as Native without any performance concerns
  • 2
    Can be incrementally added to existing native apps
  • 2
    Many salary
  • 2
    Hot reload
  • 2
    Over the air update (Flutter lacks)
  • 2
    'It's just react'
  • 2
    Web development meets Mobile development
  • 0
    Ful
  • 0
    Nigger
CONS OF REACT NATIVE
  • 22
    Javascript
  • 17
    Built by facebook
  • 11
    Cant use CSS
  • 2
    Some compenents not truly native

related React Native posts

Vaibhav Taunk
Team Lead at Technovert | 31 upvotes 路 1.3M 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

4.7K
5.2K
730
Cross-platform mobile framework from Google
4.7K
5.2K
+ 1
730
PROS OF FLUTTER
  • 92
    Hot Reload
  • 77
    Cross platform
  • 72
    Performance
  • 63
    Backed by Google
  • 53
    Compiled into Native Code
  • 40
    Open Source
  • 36
    Fast Prototyping
  • 34
    Expressive and Flexible UI
  • 34
    Fast Development
  • 28
    Single Codebase
  • 26
    Reactive Programming
  • 18
    Material Design
  • 15
    Widget-based
  • 15
    Dart
  • 15
    Target to Fuchsia
  • 11
    Great CLI Support
  • 10
    IOS + Android
  • 9
    Tooling
  • 7
    Debugging quickly
  • 7
    Easy to learn
  • 7
    Have built-in Material theme
  • 7
    Target to Android
  • 7
    You can use it as mobile, web, Server development
  • 6
    Support by multiple IDE: Android Studio, VS Code, XCode
  • 6
    Target to iOS
  • 6
    Easy Testing Support
  • 5
    Have built-in Cupertino theme
  • 5
    Good docs & sample code
  • 4
    Easy to Widget Test
  • 4
    Written by Dart, which is easy to read code
  • 4
    Easy to Unit Test
  • 4
    Community
  • 3
    Real platform free framework of the future
CONS OF FLUTTER
  • 22
    Need to learn Dart
  • 9
    Lack of community support
  • 8
    No 3D Graphics Engine Support
  • 5
    Lack of friendly documentation
  • 4
    Graphics programming
  • 2
    Lack of promotion
  • 1
    Https://iphtechnologies.com/difference-between-flutter

related Flutter posts

Vaibhav Taunk
Team Lead at Technovert | 31 upvotes 路 1.3M 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've been juggling with an app idea and am clueless about how to build it.

A little about the app:

  • Social network type app ,
  • Users can create different directories, in those directories post images and/or text that'll be shared on a public dashboard .

Directory creation is the main point of this app. Besides there'll be rooms(groups),chatting system, search operations similar to instagram,push notifications

I have two options:

  1. React Native, Python, AWS stack or
  2. Flutter, Go ( I don't know what stack or tools to use)
See more
Xamarin logo

Xamarin

1.1K
1.2K
758
Create iOS, Android and Mac apps in C#
1.1K
1.2K
+ 1
758
PROS OF XAMARIN
  • 119
    Power of c# on mobile devices
  • 79
    Native performance
  • 76
    Native apps with native ui controls
  • 70
    No javascript - truely compiled code
  • 66
    Sharing more than 90% of code over all platforms
  • 44
    Ability to leverage visual studio
  • 43
    Many great c# libraries
  • 42
    Mvvm pattern
  • 35
    Amazing support
  • 33
    Powerful platform for .net developers
  • 18
    GUI Native look and Feel
  • 14
    Nuget package manager
  • 11
    Free
  • 9
    Enables code reuse on server
  • 9
    Backed by Microsoft
  • 8
    Faster Development
  • 7
    It's free since Apr 2016
  • 7
    Best performance than other cross-platform
  • 7
    Easy Debug and Trace
  • 7
    Open Source
  • 7
    Use of third-party .NET libraries
  • 6
    Xamarin.forms is the best, it's amazing
  • 6
    Mac IDE (Xamarin Studio)
  • 5
    C# mult paradigm language
  • 4
    Microsoft backed
  • 4
    Microsoft stack
  • 4
    Power of C#, no javascript, visual studio
  • 4
    That just work for every scenario
  • 3
    Small learning curve for Mobile developers
  • 3
    Compatible to develop Hybrid apps
  • 3
    Great docs
  • 2
    Ionic
  • 2
    Well Designed
  • 1
    Ability to leverage legacy C and C++
CONS OF XAMARIN
  • 8
    Build times
  • 4
    Visual Studio
  • 3
    Complexity
  • 3
    Price
  • 3
    Scalability
  • 2
    Nuget
  • 2
    Build Tools
  • 2
    Maturity
  • 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
CEO at Stealth Startup | 5 upvotes 路 12.8K views

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

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

related Corona SDK posts

Node.js logo

Node.js

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

related Node.js posts

Nick Rockwell
SVP, Engineering at Fastly | 42 upvotes 路 1.4M 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 | 37 upvotes 路 3.5M 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

22K
18.7K
3.5K
The Web framework for perfectionists with deadlines
22K
18.7K
+ 1
3.5K
PROS OF DJANGO
  • 604
    Rapid development
  • 448
    Open source
  • 388
    Great community
  • 338
    Easy to learn
  • 250
    Mvc
  • 203
    Elegant
  • 202
    Beautiful code
  • 181
    Free
  • 180
    Great packages
  • 168
    Great libraries
  • 56
    Restful
  • 53
    Comes with auth and crud admin panel
  • 52
    Powerful
  • 49
    Great documentation
  • 47
    Great for web
  • 37
    Python
  • 32
    Great orm
  • 28
    Great for api
  • 22
    All included
  • 18
    Web Apps
  • 16
    Fast
  • 14
    Used by top startups
  • 12
    Clean
  • 11
    Easy setup
  • 10
    Sexy
  • 8
    Convention over configuration
  • 5
    ORM
  • 5
    Allows for very rapid development with great libraries
  • 5
    The Django community
  • 3
    Mvt
  • 3
    Its elegant and practical
  • 3
    Great MVC and templating engine
  • 2
    Easy to use
  • 2
    Easy
  • 2
    Easy to develop end to end AI Models
  • 2
    Cross-Platform
  • 2
    Fast prototyping
  • 2
    Full stack
  • 2
    Batteries included
  • 2
    Easy Structure , useful inbuilt library
  • 1
    Great peformance
  • 1
    Many libraries
  • 1
    Zero code burden to change databases
  • 1
    Have not found anything that it can't do
  • 1
    Map
  • 1
    Scaffold
  • 1
    Modular
  • 1
    Very quick to get something up and running
  • 1
    Just the right level of abstraction
  • 1
    Python community
  • 1
    Full-Text Search
  • 1
    King of backend world
CONS OF DJANGO
  • 24
    Underpowered templating
  • 19
    Underpowered ORM
  • 18
    Autoreload restarts whole server
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Not nodejs
  • 6
    Admin
  • 4
    Configuration hell
  • 3
    Not as clean and nice documentation like Laravel
  • 2
    Python
  • 2
    Overwhelming folder structure
  • 2
    Not typed
  • 2
    Bloated admin panel included
  • 1
    InEffective Multithreading

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鈥檚 worth mentioning Uploadcare is not a front-end-focused SPA: we aren鈥檛 running at high levels of complexity. If it were, we鈥檇 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