🔥 Wow... We just tried the Dart macros that were recently released on GoogleIO. Just look at their power!

You can also check the official update 👀

🙅‍♂️ When NOT to use Flutter:

1. Your app requires complex background processing.
2. App size is a critical factor for your target audience.
3. The app relies heavily on platform-specific APIs.
4. The app needs advanced video or audio features.
5. Your team lacks experience with Flutter or Dart.

P.S. We often talk here about how good Flutter is (and that's actually true 😏). But there are still a few cases where we'd rather not use our favorite technology.

⚡️ 2 formulas we use to estimate Flutter projects.

All variables represent time in hours. For higher or lower risks, the coefficients may vary, but the most commonly used ones are shown in the picture.

🙀 FlutterFlow: Yes or No?

✅ Why Yes:
- Rapid Prototyping: Create MVPs quickly with drag-and-drop.
- Minimal Coding: Ideal for people with no coding experience.

❌ Why No:
- Limited Customization: Complex features may need extra coding.
- Performance: Direct Flutter usage results in better performance.
- Cost Consideration: FlutterFlow requires subscription payments.

👨‍💻 We prefer coding over drag-and-drop.

🔥 Why to choose ReactNative over Flutter in 2024.

We thought about this for a while and came up with all the possible reasons why someone might pick React Native over Flutter today:

1. None.
2. None.
3. None.

We tried our best to add more points to the list, but we couldn't 😏

❌ Flutter is not always Material design.

Here is 3 more libraries our clients use in production:

👉 Cupertino: Not only for iOS, highly customizable;
👉 Fluent UI: Frequently used for desktop first apps;
👉 Shadcn UI: Unique design option for a fresh look.