One of the most important aspects of working with OEM software is to ensure that you’re getting the most out of your integration. The last thing you want is for your users to experience any kind of disconnect between the core application content and the OEM components or features you’ve chosen. If the OEM features feel like a separate experience for your users, it will lead to the low adoption of those features and could even lead to outright confusion. That’s why it’s important to not just understand how to customize OEM software to meet your needs, but also to understand the integration tools so you’re able to embed the software in the right way.
White-Labeling and Customization
Integration goes way beyond basic branding that makes sure the colors and fonts between the two applications match. You also want to ensure that the experience is seamless, that means looking for OEM software that supports responsive design concepts. This will ensure any visuals and other embedded output components will easily be able to transition across all of your end-users' devices and formats, and easily fit in with any application interface.
Utilize Single Sign-On and Shared Credentials
One of the best ways to prevent confusion among users is to make sure they never have to log in more than once. Single Sign-On (SSO) has been a staple of integrated application environments for some time. When selecting tools, make sure they support your desired sign-on methodology and also check to see if you can both pass and utilize additional credentials as variables or tokens within the app. Displaying user-specific information or feedback directly within the integrated components can help with presenting a more personalized experience that lets the user know they haven’t left the application.
APIs and Embeddable Widgets
Make sure you take advantage of any developer APIs and/or embeddable widgets to get the maximum amount of control over your software integration. If the APIs or widgets don’t allow for certain concepts or behaviors, don’t be afraid to ask your OEM partners to provide additional API endpoints or widget features. The goal of the API is to ensure you can access what you need to create a seamless integration. Your OEM vendors should welcome any feedback on how to make improvements.
Finally, a good integration requires that information and data flows in two directions, both from the parent application into the embedded application and vice-versa. This can be a simple workflow that sends data created in the embedded application back to the datasource, often called a "write back," or it can be a more complex set lof workflow rules that handle everything from data flows to actions such as messaging, alerts, file management and more.
The next time you're considering OEM features for your application, be sure to also consider how well those features will integrate with your platform. Features alone are not enough in today's world unless they look, and act, like they belog there. To learn more about integrating Qrvey’s self-service data collection, analytics or workflow automation to your application, sign up for a demo today at QrveyOEM.com