Need advice about which tool to choose?Ask the StackShare community!
Django REST framework vs NativeScript: What are the differences?
Django REST framework: Web APIs for Django. Django REST framework is a powerful and flexible toolkit that makes it easy to build Web APIs; NativeScript: Build truly native apps with JavaScript. NativeScript enables developers to build native apps for iOS, Android and Windows Universal while sharing the application code across the platforms. When building the application UI, developers use our libraries, which abstract the differences between the native platforms.
Django REST framework can be classified as a tool in the "Microframeworks (Backend)" category, while NativeScript is grouped under "Cross-Platform Mobile Development".
Some of the features offered by Django REST framework are:
- The Web browsable API is a huge usability win for your developers.
- Authentication policies including OAuth1a and OAuth2 out of the box.
- Serialization that supports both ORM and non-ORM data sources.
On the other hand, NativeScript provides the following key features:
- 100% Access to Native Platform API
- NativeScript is free of charge as an open source project
- Code with JavaScript. Style with CSS
"Browsable api" is the primary reason why developers consider Django REST framework over the competitors, whereas "Access to the entire native api" was stated as the key factor in picking NativeScript.
Django REST framework and NativeScript are both open source tools. It seems that NativeScript with 17.1K GitHub stars and 1.26K forks on GitHub has more adoption than Django REST framework with 14.5K GitHub stars and 4.29K GitHub forks.
According to the StackShare community, Django REST framework has a broader approval, being mentioned in 159 company stacks & 77 developers stacks; compared to NativeScript, which is listed in 10 company stacks and 23 developer stacks.
My journey to developing REST APIs started with Flask Restful, and I've found it to be enough for the needs of my project back then. Now that I've started investing more time on personal projects, I've yet to decide if I should move to use Django for writing REST APIs. I often see job posts looking for Python+Django developers, but it's usually for full-stack developers. I'm primarily interested in Data Engineering, so most of my web projects are back end.
Should I continue with what I know (Flask) or move on to Django?
If you want to be a Web developer with knowledge in another frontend and NoSql technology, maybe continue with Flask. However, if you want to create very fast solutions to grow up with a new business and merge these with data analysis and other tools, Django is the answer. Basically read more about the service architecture where you feel more comfortable, Microservice or Monolithic, but please will not married with any because they solve issues to different contexts.
I have just started learning Python 3 weeks ago. I want to create a REST API using python. The API will be used to save form data in an Oracle database. The front end is using AngularJS 8 with Angular Material. In python, there are so many frameworks to develop REST APIs.
I am looking for some suggestions which REST framework to choose?
Here are some features I am looking for:
Easy integration and unit testing, like in Angular. We just want to run a command.
Code packaging, like in java maven project we can build and package. I am looking for something which I can push in as an artifact and deploy whole code as a package.
Support for swagger/ OpenAPI
Support for JSON Web Token
Support for test case coverage report
Framework can have features included or can be available by extension. Also, you can suggest a framework other than the ones I have mentioned.
For starters flask provides a beautiful and easy way to create REST APIs. Also its supported by excellent beginner docs as well as a very active community. Another good thing with Flask is its widely available list of plugins which allow you to build as you go. Its also good in performance and can scale to a quite decent level. However, if you are sure your project is going to be fairly big, it would be better to start with Django as it provides a lot of features out of the box and is extremely stable in performance. Both these frameworks have support for Swagger, JWT, Coverage Report although you have to install plugins for them. Deploying both of these are fairly simple and there is huge documentation available. Django has one of the best documentations I have come across. I hope I was able to answer your queries.
Pros of Django REST framework
- Easy to use66
- Browsable api65
- Great documentation53
- Customizable50
- Fast development42
- Easy to use, customizable, pluggable, serializer9
- Python8
- Django ORM7
- FastSerialize5
- Less code3
- Easy implementation2
Pros of NativeScript
- Access to the entire native api75
- Support for native ios and android libraries47
- Support for javascript libraries46
- Angular 2.0 support46
- Native ux and performance44
- Typescript support37
- Backed up by google and telerik35
- Css support29
- Cross-platform declarative ui and code27
- Fully open source under apache 2.0 license25
- Vuejs support11
- 60fps performance9
- Powerful data visualization with native UI6
- VS Code integration5
- Angular, typescript and javascript support5
- No need for Mac to build iOS apps in Telerik Platform5
- Extended CLI support4
- Cloud builds as part of Telerik PLatform4
- Truly Object-Oriented with Typescript4
- On-device debugging4
- Extensibility4
- Access to entire native api3
- Live reload3
- Easiest of all other frameworks3
- Easy to learn3
- Backed by google3
- 0 day support for new OS updates3
- Publishing modules to NPM3
- Vue.js support out of the box2
- VueJS support2
- Svelte support2
- Powerfull mobile services as part of Telerik Platform2
- Native ui with angular2
- Vue support2
- Playground1
- Hot Reload1
- HMR via webpack1
- Very small app size1
- Write once, use anywhere1
- Easy to use, support for almost all npm packages1
- Rich ecosystem1
- Compile to Apple/Google Stores via CloudCompiler1
- Has CSS ;-)1
- It works with Angular1
- Code reuse with your website1
- Dart0
Sign up to add or upvote prosMake informed product decisions
Cons of Django REST framework
- Bad documentation2
- Reimplements Django functionality2
- No support for URL Namespaces1
- Bad CSRF handling0
Cons of NativeScript
- Lack of promotion5
- Slower Performance compared to competitors1
Sign up to add or upvote consMake informed product decisions
What is Django REST framework?
What is NativeScript?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Django REST framework?
What companies use NativeScript?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with NativeScript?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+42
+47+46
+3