Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariReact Native vs zeep
When comparing React Native vs zeep, the Slant community recommends React Native for most people. In the question“What are the best frameworks for developing iOS apps with JavaScript?” React Native is ranked 4th while zeep is ranked 6th. The most important reason people chose React Native is:
React Native allows you to create native apps by generating native views with JavaScript instead of using a web wrapper.
Question Ranking
Pros
Pro Allows you to develop native apps
React Native allows you to create native apps by generating native views with JavaScript instead of using a web wrapper.
Pro Large, supportive community
Despite being such a young framework (early 2015), the support for React Native grew quickly. There is a forum, active tag on Stackoverflow and many other ways to get help from the community.
Pro Backed by Facebook
Facebook writes their mobile apps in React Native so the code base gets pretty thoroughly used in some highly demanding scenarios.
Pro More predictable control of the state
The one way data flow, makes it more predictable and easy to control.
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 If core team doesn't use a certain feature, it's not developed
Whenever there's functionality you need that they don't use in their apps, it's not going to get developed by them, even if it's obvious it should be in the core. They always say to either submit a PR or create a separate module.
Con Steep learning curve
React Native is not the most beginner-friendly framework for creating mobile apps with JavaScript. It requires that the developer know React, which is known to have a steep learning curve.
Con Many existing JS libraries are not usable on React Native; not exactly a 1-to-1 experience to writing React either
Example: Library that provides a full calendar with agenda view.
In the end it's much easier to develop in actual JavaScript with a solution such as Ionic, especially if your app needs to work well on the desktop.
Con React native only supports react which is getting old
React native is only based on react which is getting old. An old tech developer can't take much breaking changes so it gets more patchs. There is a limit, and react is too verbose and complex. better alternatives available today.
Con Buggy
In some cases, received XML is not correctly parsed into objects.
