Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariNativeScript vs zeep
When comparing NativeScript vs zeep, the Slant community recommends NativeScript for most people. In the question“What are the best frameworks for developing iOS apps with JavaScript?” NativeScript is ranked 2nd while zeep is ranked 6th. The most important reason people chose NativeScript is:
Used by Svelte framework for native development.
Question Ranking
Pros
Pro Svelte Native
Used by Svelte framework for native development.
Pro Leverages knowledge in Angular
Angular is a very popular framework, and teams already developing angular will feel right at home with Nativescript + Angular
Pro Works great with vue.js
Pro Compatible with multiple Python versions
Compatible with Python 2.7, 3.3, 3.4, 3.5, 3.6 and PyPy.
Pro Build on top of lxml and requests
Pro Supports automatic retry on error
Retries can be configured in Requests transport for a wide variety of errors.
Pro Caches WSDL files by default
Local cache is configurable and can be disabled (e.g. using all wsdl files from local disk).
Pro Handles correctly circular dependencies in WSDL files
Pro Supports WSDL files according to the standard
Identifies errors in WSDL files; uses without errors standard-compliant files.
Pro Support for WSA and WSSE
Pro Support for Asyncio
Support for asyncio via aiohttp (Python 3.5+).
Pro Support for Soap 1.1, Soap 1.2 and HTTP bindings
Cons
Con Nativescript + Angular apps for Android tend to have long startup times.
It's very difficult to have acceptable startup times with NS+Angular in Android. It's not uncommon to see apps taking 6 sec or more to start AFTER having been optimized with Webpack (mandatory!). The same app in iOS takes only 2-3 sec. Also, this seems to happen only with the NS+Angular flavour. People using plain NS (without Angular) don't seem to have the issue.
Con Buggy
In some cases, received XML is not correctly parsed into objects.
