Acquia Digital Experience Platform vs PowerApps

• The Acquia Cloud Hosting (enterprise) provides a three-server solution. You have a Development, Staging (or UAT), and Production servers with a clear path of deployment straight up the chain. You may use Acquia's own Cloud Hooks, or their web admin UI interface to deploy to any or all of the servers.
• Git is one of the foundation services built-in to the management of the website codebase. Allowing a developer, or well-trained end user (university employee) to easily deploy a tag or branch to any one of the servers, makes it very easy for us to offload the server / account management to the school, while we focus on improving their site.
• Not only does Acquia Cloud provide a multi-datacenter failover disaster recovery solution, but they also maintain a multi-region failover as well, which allows for a fully redundant enviroment to be maintained in two geographic regions. No fear of losing any database changes or form submissions from students.
• Lastly, the onboarding process is constantly being improved, and as I have been a third-party vendor involved in many of our hosting negotiations, I have seen it firsthand. Each enterprise client is assigned a small team of engineers, technical leads, and a pseudo-project-manager to explain the process in layman's terms to the client (university / college for my example), but they also perform a number of code reviews and best-practice analysis of a site prior to launch.

Read full review

• Because PowerApps is tied to the Office365 environment, it does a very good job at talking to source information in SharePoint. For those considering PowerApps, there is something to be said for the seamless handshakes that Microsoft authors between their own tools.
• If you are wanting to parse down the fields requested (again, in relation to SharePoint) and get away from messing with content types or default forms behind the curtain in SharePoint, PowerApps is a good buffer to selecting exactly what you want to capture and nothing that you don't (that isn't required).
• While still in its early deployment, PowerApps does have good flexibility because of the coding opportunities in the tool. Coding can be a barrier of entry, but it balances code and common sense entry pretty well.
• PowerApps works pretty well on a Mac. Of course, everything Microsoft functions better in Microsoft products (IE, Windows, Edge), but the online authoring tool for PowerApps is just fine for Mac.

Read full review

• Responses from tickets aren't always from the same person, and can vary in effectiveness of solving your problem
• While documentation is robust, it can be difficult to find exactly what you need
• Provided forums are not monitored frequently, and are not as useful as they could be

Read full review

• Customizing interface for phones and tablets.
• You are limited in layout, either phone or tablet, no desktop support.
• The "Code Editor" could use some work. Giving you a bigger canvas so to speak.
• It can be buggy if you make changes to data sources and flows outside of PowerApps. I have had one or two controls "break" because I made changes outside of PowerApps.

Read full review

• Our website isn't a revenue generator, so we don't have specific ROI calculations.
• The new website is helping us move off of a legacy on-prem server environment. The reduction of cost in maintaining those will be beneficial.
• We have had to invest in some training for our developers to learn Drupal.

Read full review

• I am still developing my application but assuming everything works the way I have laid it out then PowerApps will help us to turn a 10yo marcro-powered Excel workbook with mostly static work-flows into a streamlined and less mistake-prone workflow while utilizing a single database.
• The application will allow us to access dynamic project information in the field via tablet. Previously this could only be done via phone call or email.

Read full review