Questions MenuAppController

[Marthianfred]

How can I implement this to change the widgets on the screen, when clicking on the menus of the side_menu the intention is not to reload the page but to go removing and putting components while you look at the options, I don't know if I explain myself.

[Marthianfred]

How can I implement this to change the widgets on the screen, when clicking on the menus of the side_menu the intention is not to reload the page but to go removing and putting components while you look at the options, I don't know if I explain myself.

i solve this.. using flutter_bloc very cool

[Dantechdevs]

It sounds like you want to implement a dynamic user interface that changes components on the screen based on user interaction with the side menu. To achieve this, you can use a front-end framework like React or Vue.js, which allow you to build dynamic user interfaces with reusable components. You can then use state management to keep track of which components to display based on user interaction with the side menu. Would you like more information on how to get started with this approach?

[Marthianfred]

Really, what intention does it have that we use Flutter for this beautiful template and its life form, and then change it to another language like Vue or React, wouldn't it be a lack of respect for creation?

Honestly I'm implementing the view with BlocPrider and I've been able to do visual and data changes with backend in Laravel and I'm liking how it works.

if you really want to contribute to this. Why not continue with Flutter?

[Dantechdevs]

Your concern about switching from Flutter to another language like Vue or React and the idea of respecting the work put into the Flutter project is valid. Choosing a technology stack for a project should depend on various factors, including the project's specific needs, the team's expertise, and long-term considerations.

Here are some points to consider:

1. Technology Fit: The choice of technology should align with your project's requirements and objectives. If you find that Flutter is a suitable choice for the front-end development and Laravel for the backend, and you are satisfied with the development progress, it's a valid approach.

2. Team Expertise: If your team is comfortable with Flutter and has made significant progress, it might be more efficient to continue with it. Consistency in the technology stack can lead to better productivity and code quality.

3. Maintenance and Scalability: Consider long-term maintenance and scalability. If Flutter and Laravel meet your project's needs and are sustainable over time, there's no compelling reason to switch to a different technology.

4. Community and Ecosystem: The strength of the community and the available ecosystem for a technology can also influence your decision. Flutter has a growing community and a rich set of packages and libraries.

5. Cost and Resources: Changing technologies can be costly in terms of time and resources. It may involve retraining your team, rewriting code, and adapting to new development patterns.

In essence, the decision to stick with Flutter or switch to another technology should be based on a careful evaluation of your project's unique circumstances. While Flutter is a powerful framework for building cross-platform mobile apps, if you feel that Vue or React would better suit your project's requirements and constraints, and if you have the expertise to do so effectively, it's a valid choice.

Ultimately, the respect for creation lies in delivering a successful and maintainable product that meets your users' needs, and the technology you choose should support that goal.