{"id":15024,"date":"2023-07-06T11:02:52","date_gmt":"2023-07-06T16:02:52","guid":{"rendered":"https:\/\/www.mrc-productivity.com\/blog\/?p=15024"},"modified":"2023-07-06T13:26:33","modified_gmt":"2023-07-06T18:26:33","slug":"low-code-integration-9-questions-to-ask","status":"publish","type":"post","link":"https:\/\/www.mrc-productivity.com\/blog\/2023\/07\/low-code-integration-9-questions-to-ask\/","title":{"rendered":"Low-code integration: 9 questions to ask"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Looking for a good low-code platform is a lot like buying a car. There are many options out there, and they\u2019re all different. Some look flashy. Others are plain. <\/p>\n\n\n\n

But, over time, we care more and more about one thing: How it was made. <\/p>\n\n\n\n\n\n\n\n

For instance, will you care about all of your car\u2019s bells and whistles if it\u2019s always in the shop? What if it only uses expensive, specialty parts that must be special ordered? What if it\u2019s constantly giving you problems?<\/p>\n\n\n\n

Low-code development tools are the same. There are many options out there, and they\u2019re all different. <\/p>\n\n\n\n

But, over time, you\u2019ll care more and more about how it was made. The underlying architecture will play a massive role in your success or failure with the tool.<\/p>\n\n\n\n

\"extensibility\"How so? The architecture determines how well the tool integrates with other software\/systems. If it\u2019s not built for openness and flexibility, you\u2019ll run into countless integration problems.<\/p>\n\n\n\n

Why is that so important? If you\u2019ve ever used development software of any kind, you know how important integration is to your success. After all, do you really want another tool that lives on an island? Do you want more software that doesn\u2019t really fit into your business? <\/p>\n\n\n\n

Probably not.<\/p>\n\n\n\n

The problem<\/strong>: How do you know which low-code tools are built on flexible architecture before you buy? How do you know whether or not you\u2019ll run into integration issues? <\/p>\n\n\n\n

The answer<\/strong>: Ask the right questions. Here are some of the most important integration questions to consider before investing in low-code: <\/p>\n\n\n\n

    \n
  1. How will this low-code software fit into our existing tech stack?<\/strong>
    Will it tie into your existing databases, ERP systems, CRM systems, etc\u2026? Make sure you understand what this process will look like.<\/li>\n\n\n\n
  2. How will the applications it creates tie into our existing applications?<\/strong>
    Can you embed the generated applications into your existing systems? Can you white-label the applications so they look and feel like they belong?<\/li>\n\n\n\n
  3. Will this work with both legacy and modern (and future) systems?<\/strong>
    This speaks to how flexible the tool is when it comes to integration.<\/li>\n\n\n\n
  4. How difficult is it to integrate with third-party tools?<\/strong>
    Many low-code tools have built-in integrations with other tools. But, integration isn\u2019t always straightforward. Can you create your own API calls or web services? You don’t want to only rely on the vendor’s pre-built integrations.<\/li>\n\n\n\n
  5. Will this work with a hybrid-cloud (or even a multi-cloud) environment?<\/strong>
    Many businesses use one or more cloud services in combination with their on-premise data\/systems. Will the low-code tool seamlessly integrate with modern cloud environments like this?<\/li>\n\n\n\n
  6. Is it built on proprietary code or open standards\/frameworks?<\/strong>
    Many low-code tools operate as a \u201cwalled garden.\u201d They\u2019re built on proprietary architecture that limit your integration options. You need tools that are built on open code and standards. <\/li>\n\n\n\n
  7. Does it generate standard, human-readable code?<\/strong>
    Now, most low-code tools won\u2019t require you to dig into the generated code. But, it\u2019s nice to have that option available. For instance, suppose you need to make a customization that\u2019s not possible through the interface. You want the option to edit the code, even though that will rarely be necessary.<\/li>\n\n\n\n
  8. Do the applications run independently of the platform?<\/strong>
    This speaks more to vendor lock-in than integration, but it\u2019s still an important question. What happens if you ever stop using the platform? Will your applications stop functioning? To avoid this, make sure the applications run (and can be maintained) independently of the platform.<\/li>\n\n\n\n
  9. Do you have a services team that can help with integration if necessary?<\/strong>
    Every business is different and has different integration needs. A services team that can help you through any custom integrations you might need is a valuable asset to have.<\/li>\n<\/ol>\n\n\n\n

    <\/p>\n\n\n\n

    Of course, I\u2019m just touching on these points. If you\u2019d like to see a more in-depth look at what types of customization options you need in low-code tools, check out this video: <\/p>\n\n\n\n

    \n