BEM VS Flutter Multi-platform Sample

• Consistency
  BEM enforces a structured way of naming and organizing CSS classes, which promotes consistency across the codebase.
• Scalability
  The methodology is designed to handle large and complex projects by keeping styles modular and reusable, which helps in maintaining scalability.
• Maintainability
  By using a clear naming convention, BEM makes it easier for developers to understand and maintain code, even if they weren't the original authors.
• Flexibility
  BEM allows for flexible and modular component development, making modifications easier without affecting unrelated parts of the codebase.

Possible disadvantages

• Verbose Naming
  The class names in BEM can become quite long and verbose, which might make the HTML markup harder to read.
• Learning Curve
  Developers unfamiliar with BEM may need some time to adapt to its conventions and understand the methodology well.
• No Enforced Hierarchy
  BEM does not inherently enforce any specific hierarchy or structure among elements, which might lead to inconsistencies if not carefully managed.
• Increased Initial Setup
  Implementing BEM from scratch can involve significant upfront planning and setup, which might be seen as an overhead for smaller projects.

• Multi-platform support
  The project demonstrates how to build a single Flutter codebase that runs on Android, iOS, Web, macOS, Windows, and Linux, showcasing Flutter's cross-platform capabilities in a practical example.
• Clean architecture approach
  The sample follows a structured and organized architecture pattern, making it easier for developers to understand best practices for structuring multi-platform Flutter projects with separation of concerns.
• Good reference for beginners
  It serves as a useful starting point and learning resource for developers who want to understand how to set up and configure a Flutter project that targets multiple platforms simultaneously.
• Open source by Mindinventory
  Backed by Mindinventory, a recognized Flutter development company, the project benefits from professional development practices and offers a trustworthy reference implementation for the community.
• Platform-adaptive UI demonstrations
  The sample shows how to adapt UI layouts and behaviors for different screen sizes and platform conventions, which is one of the more challenging aspects of multi-platform Flutter development.

Possible disadvantages

• Limited community engagement
  The repository has relatively low stars, forks, and contributions compared to other Flutter sample projects, which means fewer community-driven improvements, bug fixes, and discussions.
• Sparse documentation
  The project lacks comprehensive documentation, detailed setup guides, and thorough explanations of architectural decisions, making it harder for newcomers to fully understand and leverage the codebase.
• Infrequent updates
  The repository does not appear to be actively maintained with regular updates, which may lead to compatibility issues with newer Flutter SDK versions and outdated dependency usage.
• Limited real-world complexity
  As a sample project, it covers basic multi-platform scenarios but does not address more complex real-world challenges such as platform-specific plugin integration, advanced state management, or production-level error handling.
• Minimal testing coverage
  The project appears to lack comprehensive unit tests, widget tests, and integration tests, which limits its value as a reference for production-quality multi-platform Flutter development practices.

No analysis of BEM yet.

BEM REVIEW! is Bem worth watching?

More videos

No Flutter Multi-platform Sample videos yet. You could help us improve this page by suggesting one.

• Why CSS Is So Hard for Generative AIs to Understand?

  Beyond the countless ways to achieve the same result, there are just as many methodologies for writing CSS itself. Have you ever came across BEM, SMACSS, OOCSS, atomic CSS, etc. If not, then you can add yours to the list. - Source: dev.to / 12 months ago

• hearing Michael Scott.

  SCSS makes it easier to use mixing and variables. I'm exploring it's applications for Codepen as well as the use of BEM to modularize reusable CSS components. - Source: dev.to / about 1 year ago

• The CSS Odyssey: Why I Turned back to CSS After Trying Everything Else

  Style conflicts is one. Although CSS class definitions are placed in reverse import order, problems still occur in Next.js when some pieces only appear in page but not layout CSS bundles. Following BEM (Block Element Modifier) and... - Source: dev.to / over 1 year ago

View more

Tracking Flutter Multi-platform Sample since Sep 2021.