Laravel is ideally suited for fluent PHP developers who want a framework that can be used to both rapidly prototype web applications as well as support scalable, enterprise-level solutions. I think where it is less ideal is where the client has an expectation of using a certain CMS, or of having a certain experience on the admin side that would perhaps be better suited to a full CMS such as Drupal or WordPress. Additionally, for developers who don't want to write PHP code, Laravel may not be the best solution.
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
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.
Significant learning curve. You cannot be an expert in a week. It takes many experimentations to properly understand the underlying concept. We ourselves learned it by using it on the job.
Too much to soak in. Laravel is in everything. Any part of backend development you wish to do, Laravel has a way to do that. It is great, but also overwhelming at the same time.
Vendor lock in. Once you are in Laravel, it would not be easy to switch to something else.
Laracasts (their online video tutorials) are paid :( I understand the logic behind it, but I secretly wish it would be free.
The eloquent ORM is not my recommendation. Let's say you want to write a join, and based on the result you wish to create two objects. If you use Laravel to do automatic joins for you, Laravel internally actually makes two calls to database and creates your two object rather than making one join call and figuring out the results. This makes your queries slow. For this reason, I use everything except eloquent from Laravel. I rather write my own native queries and control the creation of objects then rely on Laravel to do it. But I am sure with time Laravel will make fewer calls to DB.
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.
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.
Supporting unit testing is bigger plus point in Laravel than any other framework. Developing with Laravel is much easier. Other frameworks have value in market, but Laravel has taken the lead in popularity among PHP developers in recent years. The large community supports you if you have problems. Using Laravel, integration became easy with third-party libraries, but it was costly too.
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.
Laravel allows us to rapidly prototype and build complete, scalable applications internally, which saves us time and allows us to have internal tools that fit out precise needs. We use Symfony for a similar purpose, but Laravel is an even higher-level framework that we find saves us substantially more time when building many types of web applications.
Laravel solves many of the underlying concerns of building a large application (such as authentication, authorization, secure input handling) in the right ways. It saves us from handling those low-level concerns ourselves, potentially in a way that could take a lot of time or sets us up for issues in the future. It's tough to assign an ROI to this, but I'm sure it has prevented issues and saved time, which both have an impact on our financial situation.
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.
