Replies: 1 comment
-
|
Great news guys, I've done some experimental refactoring with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks to all of your support & advises Spotube has become a huge project for Flutter Community & an example displaying the capabilities of Flutter in the Desktop Platform/arena
From the very beginning, I was thinking about using
flutter_hooksfor the project. But at the time the project was super small (0 stars) & I never thought it'd grow as big as now. At that time, these packages didn't feel relevant for the project. But everything has changed now. The project is big, has a lot of user & need better consistencyIt's becoming harder to manage bigger & logically complex components (e.g
Player). Because of Flutter's nature of being a "bit" verbose (no offense, it's an universal truth), code reuse specifically "Logic Reuse" is hard to do. This is where Hooks shine. Encapsulating logic in smaller functions, increasing code re-usability & using them in all other hooks/components is the main purpose of hooks which can be enormously useful for the upcoming v2 RoadMap's Android supportBut let's be real guys, Flutter's not React/Vue & there must be some reason why The Flutter Team didn't choose Hooks over traditional mixins/Widget Builders/InheritedWidget
As this project is driven by the community for the community, I want the suggestion/answer from the community
Should I use
flutter_hooksor not? (For yes react "👍" for no react "👎")Please don't hesitate to comment the benefits/problems of using
flutter_hooksBeta Was this translation helpful? Give feedback.
All reactions