Kony Development Cloud vs React

• Cross-platform mobile development - we used this for developing the app on a native platform (which could be iOS, Android). Kony offers tools that are useful because they decrease costs and increase the speed at which apps are developed. In addition, cross-platform mobile development tools are generally quite simple to use as they are based off of the common languages for scripting, including CSS, HTML, and JavaScript. It has become easy to find resources with the skill set especially because this is based out of common languages.
• In Kony mobility platform Visualizer makes app development quick and easy. Tons of documentation online.
• Used Kony to develop an amazing app that serves our customers well. WYSIWYG interface is great for building interfaces quickly. Build and test quickly for many different targets.

Read full review

• React is designed around the notion of generated html as opposed to templated html. This provides more flexibility in building elements on a page, and allows developers to create html that is programmatically configured based on runtime considerations.
• React uses JSX, which is HTML templating integrated into javascript code. This simplifies the generation of complex structures, especially those that vary based on runtime and interactive data.
• React is more efficient because it generates a virtual DOM rather than directly building in in the actual DOM. By building 'offline' in this manner, the DOM generation is faster. After building, it can be installed in one operation.
• React only builds those portions of the display that have changed, making display updates more efficient.

Read full review

• Manuals or instructions need to be streamlined with its high pricing.
• It's a very intricate platform. It only performs moderately while the app is currently in operation.

Read full review

• React could get very frustrating unless you start thinking in React. React enforces a top down hierarchy of data flow and offers no way for the data to communicate backwards. This is a big shift in mindset coming from Angular 1.x. This constraint is really a big factor that determines how to organize your code and how you might want to write your own Components.
• Because of the self imposed top down hierarchy, you end up having a heavy parents with dumb children. Because parents would need to the bulk of the work, they usually manage the state, while passing callbacks to the child components. If not properly designed, this could lead to the callback hell, where you could have callbacks passing through like multiple children.
• As with any library, you will have to iterate through multiple designs to come up with a ways to avoid "heavy parent components" in React. One obvious solution is using some open source tools like Redux, but we opted for a variation of it to suit our needs.

Read full review

• Positive on ROI. I'm constantly utilizing Kony since it's a robust tool capable of publishing.
• It also shares prototype creations of apps in a highly intuitive and customizable environment. It provides a preview of apps in real-time. Collaboration is seamless. Important functionality includes smartphone features (without any written code involved) and accessibility to a browser, maps, and SMS.
• Trying to understand the user manual can be challenging since there are way too many features available. All of them aren't really necessary for beginners. And they've yet to offer them in a "phased" approach.

Read full review

• React sped up the time to implement new features, providing much better code-reuse across the team
• React's excellent performance made it so new components ran faster in the browser
• Since React is so popular, it's been easy to recruit new developers to the team who already have a familiarity with the library

Read full review