Javonet’s market researchers have identified a great opportunity for all the component vendors who offer their controls for just one of the two leading technologies (Java or .NET). We are monitoring many different technological markets seeking for new opportunities for our prospects. The work we do allows us to reveal the new undiscovered fields where the robust integration between Java and .NET may provide the certain benefits for the customers. This led us to the UI and back-end controls vendors.
We have examined the UI and back-end controls market and this became clear that there is a significant number of UI and back-end controls that are available for one technology only which the controls’ end-user would desire to use in their applications developed in the different programming languages.
The PoCs that we have conducted revealed that Javonet is a perfect match for both UI and back-end controls and it allows to expose any kind of the control to the other programming language in a matter of days. Thanks to the Javonet’s performance and the ability to connect .NET and Java within single OS process, any controls’ vendor can offer their customers the control which was dedicated to one technology in the other. It will allow preserving entire current functionality and the performance without touching the original code base of the existing control. This means that any Java or .NET control can become respectively .NET or Java control instantly at minimal investment. The benefit here is a single code base (the original code of the control, no need of maintaining both Java and .NET code), no need of creating the new documentation, the same functionality set remains, and there is no compromise when it comes to the user experience of the control, doubling the market capacity.
Whatever functionality the control provides for the original technology it has been destined for, regardless of it’s complexity it can be reflected 1:1 in the other technology.
Universal Framework Component Vendor
By joining the Universal Component Vendors notion the controls vendors can offer their controls in different models:
#1: The simplest approach assumes the creation of ready-to-play Java versions of controls, with limited functionality. This means a pure Java API maps only part of the methods exposed by the .NET implementation. However, the source code of the wrapper is shared with customers as open source. More advanced customers can extend the wrapper on their own using Javonet development guides.
Customers can download the control, run the sample Java project, and verify the reliability and performance through hands-on experience. In this model, the end-customer needs both a Javonet and component trial or commercial license.
The process of wrapping UI controls is very easy and intuitive. To provide a glimpse of how easily it can be achieved, we provide the samples below for more technical readers:
#2: The second approach assumes that the UI controls vendor provides full coverage of the .NET component API and embeds a Javonet license inside it, meaning that the end-customer does not need to make any changes to the wrapper or even have access to its source code, as a ready-to-use Java package with a pure Java API is provided. Customers do not need to purchase a Javonet license, either, because with each purchase, the license cost is included in the component license and is settled between the component vendor and Javonet.
#3: In the third model, the component vendor purchases a Javonet Enterprise license which is issued per component libraries instead of customers and guarantees flat fees regardless of the component sales volume.
Note: More details about the components integration can be found in our previous article about the UI Components Revolution – embedding .NET UI components in Java
How to join the Universal Framework Components Vendor notion?
It is very easy to become the Universal Framework Components Vendor. The simple process assumes choosing the vendor level and signing the document that confirms the Universal Framework Component participation. After the document is signed the Javonet team will prepare the basic strongly typed wrapper of your component library with the limited, basic functionality to be used by your customers for the demo purposes and will guide you through next steps.
From Javonet you will receive:
– Java sample how to use your component (to be included in your product package, it will also be published on our github i.e.: https://github.com/Javonet/YourCompanyName)
– Instruction for developers explaining how to extend the wrapper (to be included in your product package)
– Strongly-typed Java package (wrapper) with limited functionality required to run the sample. Source code is hosted on public GitHub (i.e. https://github.com/Javonet/your-control-name) with instructions how to extend it. Compiled version is supposed to be included in your product package
– Wording proposal how to update your listings in ComponentSource
Please see our Unversal Framework Components Vendor document for the details, it is available here:
How to Become Cross-Platform Component Vendor PDF.
combit’s Success Story
combit List & Label .NET control has been successfully opened to the Java customers by joining the Universal Framework Components Vednor notion. Now combit offers their customers the List & Label control for Java with the limited functionality as a demo. Any customer can download Java version of combit’s control from the Conponent Source website and play with it to prove it’s efficiency. After the evaluation the customer may purchase Javonet’s license and add the remaining functionality to the Demo control which will result in the fully functional Java version of the control. All the instructions how to work further with the control’s code in order to extend it’s functionality will be provided by Javonet along with the full support.
If you are a component vendor, you can join the revolution today by contacting our sales team.