6 Reviews and Ratings
92 Reviews and Ratings
No answers on this topic
You should go for using it in particular if you are going to be build code once run everywhere kind of things and you want to not write most of the backend on your own. As AWS Amplify can take care of a lot of backend things for you and you can manage most of the stuff from front end coding. perfect for using in react/ flutter apps. Additionally better to use when you are going to use other AWS service and don't want to scatter things aroundIncentivized
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 and design of the AWS Amplify for easier setuppainless user flow for react, angular etceasier setup using CLI with effective questions.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
AWS Amplify init ends up changing the cloud. there should be deploy kind of thingconfusions between Front end backend as both codes get mixed. this should be kept separatebetter documentation with use casesIncentivized
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.
Its AWS take on the Firebase kind of system for providing backend as a service. Although Firebase has advantage of bigger community, better documentation and code examples; AWS Amplify is creating its own space where you will be going to use AWS products and Infrastructure in your project. Amplify Dynamo DB and GraphQL have clear cut advantages that have no direct alternative in Firebase as real time db and firestore documents both lack versioning.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
saves time on righting backend interfaceseasier to setup with react/ react nativelambda functions can be used to extend functionalityIncentivized
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