How do I integrate elm into my products?

To integrate elm, first sign up for an account. In the portal, create a product. This will give you a product ID and public key that you need to use in your code.

Once you have the product ID and public key, download and add a reference to the elm client API library in your code. elm client API is available for a variety of programming frameworks, including .NET, Java, Python, and Javascript (including Typescript typings). The client API libraries are publicly available in popular package management systems for the respective technologies (nuget, Maven, pip, npm, etc.). Follow the instructions in our documentation site to integrate elm into your product. In just a few hours, you can have your existing product integrated into elm.

What technology can I use elm with? What is the code written in? Is there tech that elm isn’t compatible with?

You can use elm with any technology. The client API libraries are available for a variety of programming frameworks, most of which are cross-platform frameworks. elm has been tested across all major desktop and web application platforms.

Does elm use any technology that isn’t industry standard so if it loses market acceptance, I’m stuck with technology that isn’t being updated and serviced?

At the heart of the elm client API libraries are https calls to the elm backend, and industry-standard encryption algorithms that have been in use for decades. The elm client API is written so that there is minimal amount of code required in your product to integrate with the backend. The client API does most of the heavy lifting. In case you want to switch away from elm in the future, you can still keep the same hooks in your code and write an adapter to switch to a different client API of your choice. In fact, we have helped our clients migrate from other licensing providers and the adapter code to migrate to elm was minimal.

How can I take elm for a test drive to see if it works without having to commit to a big rollout?

If you want to trial elm, we will set up an account for you in our staging server. You can either take elm for a test drive using reference implementation code (a simple cross-platform .NET console application) that we provide, or you can integrate it into your own product with minimal effort. Once you are happy with the way it works, you can migrate to production by changing the value of just three variables in your code. We provide the staging account free of charge and recommend to our clients to use compile flags to switch between production and staging environments. This way, when you want to experiment with new licensing models, or modularizing your application, you can first test the new setup on staging and once you are happy, compile the same code with a different compiler flag to push the new code to production.

What do I need to know to license my products and get actionable information on my customers' usage and feedback? Where do I get this information?

Once you integrate elm client API and the feedback API into your product, you can start issuing licenses to your customers from the elm portal. Once your customers install the new version of your product with elm, the elm portal will start lighting up with usage data and user feedback that is sent using the API.

If I’m not happy with elm how do I unwind this? Is this going to be total PITA?

Not at all. As we mentioned earlier, we have designed the client API to have minimal impact on your business logic. You can switch away to a different provider if you choose to by writing an adapter to their API