Make vs. Power Apps

Integromat is the best tool for business automation in my opinion because unlike Zapier it allows us to integrate with any API even if the app is not available which allows us to create automation even with the less known apps that we use or the ones that we built internally for our own company.

Incentivized

PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams. PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution

• UI/UX Simplicity and Features
• Workflows are explained in details and even people without IT background can use the tool.
• Consumption is nicely tracked.
• Myriad of existing templates, solutions, and readymade connectors.

• Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
• We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
• The online learning resources and tutorials are helpful as well for those who are tech savvy.

Incentivized

• There are always new platforms and connections that we'd like to see
• More flexibility in paying for operations (tasks) on a sliding scale, instead of by tier
• More thorough support documentation on connecting various platforms and troubleshooting errors

Incentivized

• More complicated to understand in comparison with Nintex Forms.
• Complicated to find errors.
• Using PowerApps for SharePoint Forms is a bit complicated by setting up the start and load scenario with a lot of JavaScript.
• Load values, change them by code, and save them back could be easier. Actually quite complicated to handle a lot of variables.

Incentivized

At this point, it is firmly embedded in the DNA of the business and to give up the ability to automate workflows and create integrations on the fly would be a terrible idea.

Make's easy to understand user interface helps you to visualize what's happening at all times. Could use some tweaks around the navigation from a scenario specifically in the folders and back navigations. I can't tell you the amount of time wasted in that area. When you branch, you can't bring a branch back together in the same scenario which is kind of a bummer as well.

Incentivized

PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.

Incentivized

The pricing schema is very attractive, almost 50% lower than the competition. You could start from free and then grow. It has a pretty big library of connections to other apps and services, which really helps you when everything is a mess. Integromat has a really easy-to-use interface. You could do almost everything with fewer than 5 clicks. Scenarios (automation steps to complete a routine) have graphics so you can configure them more easily.

Incentivized

The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.

Integromat allows us to do everything we used to do on Zapier but it doesn't limit us to only the popular apps, with Integromat we're integrating custom APIs and we get data from different servers through GET requests and it's exactly what we needed and Zapier couldn't provide it.

Incentivized

Much cheaper, much more customizable, and easier to use. There is not much of a learning curve and the licensing cost is much cheaper. PowerApps does one thing very well, whereas other platforms are mediocre. There is much more customization possible for your in-house workflows that you can build yourself vs using NetSuite engineers to build it for you.

Incentivized

• We used too many credits multiple times and had to buy them additionally, there are no prevention systems to setup to alert before it happens.
• Some consumption is difficult to understand and requires time and digging.
• It requires heavy internal effort to simplify things in Make in order for it to operate cheaper.
• Initial IT setup is paramount and determines a lot.

• It has given us a focal point for development. We now have the possibility of connecting to mobile and the default SharePoint online interface isn't always easy to manipulate. PowerApps has given us an opportunity to improve our user experience.
• An improved user experience has given us a better shot at compliance. When users don't fight the environment, they don't gravitate towards workarounds or non-compliance.
• As lists and libraries change, the platform scales pretty well.
• Having users with the capability to create their own forms and tools has dialed back the app dev need (there is a balance though) and distributed power to the process architects and people who actually need the solutions in the first place—much more efficient model of service delivery: self-service.

Incentivized