Flow (discontinued) vs. Power Apps

If you are used to using apps such as Slack, Box or Harvest, you will have an easy time getting use to Flow's UI. Drag and drop features, messaging between users, @tagging for notifications that alert you not only on your desktop but your as well email are particularly useful. If you need projects done fast and easily between multiple teams this is a great application for your business. A particular scenario where Flow is NOT suitable would be if you are used to working soley from your phone. Flows mobile app is slow, not user friendly at all and hard to navigate. Also, you cannot use a mobile site because it directs you to using the app. This IMO is a great desktop project manager, but NOT mobile.

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

• Design: very easy to discern what is important at a glance. The UX just works; it's very well thought out.
• Ease of use: onboarding was a breeze. Was up and running in less than an hour.
• Support: in-app support is great, nice website too to find exactly the solutions we needed.

Incentivized

• 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

• Better integration with Google Calendar -- it could be a bit clunky
• The mobile app didn't have as much functionality as one would like - you had to download two apps to access the features used on a desktop version

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

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 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.

Flow, unlike Trello, offers its users a more organized interface and much more complete tools to carry out project management, which is why I consider that for the management of business projects of medium or large companies this tool covers the needs of each. In addition, its ease of use makes it much easier to adapt to this tool because it does not require a very learning curve

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

• Our biggest issue prior to flow was scrambling at the last minute to meet a project deadline. Flow has helped us manage tasks towards a deadline to execute more successful events and projects.
• Since Flow is being used across our entire organization, the speed at which we can collaborate cross-departmentally has increased. This is especially true of our communication and collaboration with our Marketing team.
• Flow has allowed our leadership team to be able to see the progress of a project at any time just by looking at that projects dashboard. This has both given them confidence as well as let them know when they need to intervene.

Incentivized

• 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