Laravel PHP Framework vs. Power Apps

This framework's pros are more than cons. It can be used for many purposes; building e-commerce is one of them.

1. Code is clean and simple because of its routing.

2. Connection to database and query optimizing.

3. The amazing automatic memory to remember past queries is a big plus.

4. Migrations is the most crucial feature of this framework.

5. Supporting unit tests out of the box.

6. Artisan to use command line.

7. Large community to support your queries.

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

• Many libraries available which simplify integration of SaaS APIs within your application (eg, MailChimp, Mandrill, Stripe, Authorize.net)
• Pre-packaged tools to facilitate common tasks when building applications (eg, User Authentication and Authorization, Background Jobs, Queues, etc)
• Support for a broad set of technologies out of the box (eg, PostgreSQL, MySQL/MariaDB, MemcacheD, BeanstalkD, Redis, etc)

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

• There isn't a whole lot to dislike about the framework, honestly. If I am forced to say something is that sometimes the authors change the directory layout and it's not always easy to deal with. That being said, I've never not been able to upgrade within a few hours.
• Sometimes using the artisan CLI - it requires additional tweaking to get it running on non-standard application rollouts.

Incentivized

• PowerApps has a great coding option, but there are some pieces of the tool that the requirement to understand code is a barrier to fun if the user doesn't code.
• MUCH time can be spent looking for solutions on this young platform and the body of forum/help/lessons learned is not as robust as it will be in a few years.
• Like many early-stage Microsoft products, PowerApps is a relatively blank slate that will be improved by the feedback of their users and ongoing feature development. Right now it seems that the product lacks a critical mass of use-case driven templates (there are some, but I haven't yet found one that didn't require more work to customize it to my need that it would take to build my own tool).

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.

Originally, it was a decision between Zend, CodeIgniter, and CakePHP for me. I chose CakePHP and used it as my main PHP framework for at least a couple of years before noticing and giving Laravel a fair try. Ultimately I selected Laravel because I felt it fit with my preferred development style, it utilized many of the modern best-practices I wanted to follow, and I felt that it allowed me to build better things in less time that seemed more maintainable. I have used, and still do use, Symfony directly for certain things, but I think of it (and use it) more as a code library than as a full application framework. When I'm building a web application, I tend to prefer Laravel.

Incentivized

1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to create workflows without thinking about the price for each workflow and we use only some workflow and relative easy workflows and forms as a medium-sized company. 3. PowerApps provides a lot of functionality without needing to invest in premium features directly.

Incentivized

• Positive: Our delivery time for PHP application is faster than usual.
• Positive: Developers are happy and they write better code with their usual development tools. No tool-upgrade necessary.
• Negative: Initial delivery took 6 months extra and had to rewrite project several times.

Incentivized

• Automation of manual processes brings an ROI on labor costs.
• Intake of data provides clean database design.
• Connectivity to data-lake provides insights and trends into the data.
• Able to scale operations with efficiencies provided by the app.
• Can mature the process and workflows to do more.

Incentivized