What types of projects or tasks would you prefer to avoid in your work?

Preferences regarding project or task types may depend on personal interests and experience, but in the context of Flutter, several situations can be identified that often cause difficulties or reluctance to work:

• Very complex native integrations. If a project requires deep interaction with platform-dependent code (e.g., complex native SDKs, non-standard hardware capabilities), this can complicate development in Flutter.

• Projects with very limited device resources. Flutter applications may consume more memory and resources compared to native ones, so for very weak devices or specific embedded systems, other technologies are preferable.

• Highly specific UI/UX that are difficult to implement in Flutter. If the design requires non-standard animations or components that are difficult or time-consuming to implement, this may be undesirable.

• Projects with very tight deadlines and a large amount of native code. If the project is heavily tied to native technologies, migration or support in Flutter may be inefficient.

Overall, it is advisable to avoid projects where Flutter does not provide clear advantages or where its limitations could lead to issues with quality or deadlines.