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.
If you want a customizable solution that can be adapted for just about any scenario, I recommend using Notion. If you need a solution that's easy to share with people outside your organization, Notion is great and allows individual or team permission-setting. If you want a turnkey solution, Notion might not be the best since it requires a fair bit of set-up. There are templates that can be purchased to handle this, but I haven't found them very helpful.
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.
I use Notion on my personal tablet, and unlike on the computer, I have a lot of difficulty editing backgrounds, GIFs, and page dividers. It's not as user-friendly, and often the elements end up cut off or misaligned, which is frustrating.
While the current calendar feature is helpful, I'd love to see more customization options. The Google Calendar style isn't always ideal, especially for tasks without specific times or for ongoing projects that require daily maintenance.
It would be fantastic to have more flexibility in customizing Notion pages. For example, I'd love to create planners with the freedom to add illustration boxes, stickers, or GIFs without being restricted to a fixed layout.
Very easy to use (I learned how to use everything on my own) and I was able to set up an entire ecosystem without any courses or other tools. I often say that Notion is like Lego for adults, because there we can use all the available tools to create a multitude of things, from funnels to projects with calculated deadlines and tags.
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.
The company uses both Notion and Trello within the company. Notion is more for North America employees while Trello is used between Operation team overseas and in North America. Sometimes it's a preference of how the tools look like for project management. I would say both Notion and Trello are nice tools and serves our needs.
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.
