I have implemented authentication for my own app that involved Supabase and Oauth login via Google. If you’re interested, I will drop full working code when this post reaches 80 thumbs up 👍

I have implemented authentication for my own app that involved Supabase and Oauth login via Google.

If you’re interested, I will drop full working code when this post reaches 80 thumbs up 👍****

Creating reusable UI components + responsive & adaptive design.

Take a look at how Text widgets are implemented and a Window Size Scope. Really love those ones.

https://lazebny.io/ui-components-adaptive-and-responsive-design/

Just analyzed a pubspec one guy posted on Linkedin of his PAID flutter template :)

Let's review this pubspec.yaml file:

- auto_route: A navigation library with common issues related to templating. Currently, there's no ideal recommendation to replace it, but it's not great. Consider using go_router instead.

- awesome_flutter_extensions: While it might be useful, I don't recommend including it as a dependency in templates. Instead, add it manually if you find it beneficial in specific projects.

- collection: A great library! However, it's better to specify it under "any" versioning, along with other Flutter dependencies like meta, intl, and async.

- flutter_animate: This is a good choice.

- flutter_settings_ui: This library has been archived and only adds a settings screen. It's better to manually create your own settings screen for better control and flexibility.

- hive: This database is unsupported and problematic—avoid it at all costs. I recommend SQLite as a more stable alternative. More details here: https://lnkd.in/d5rGgdfQ.

- hooks: This is difficult to read and prone to errors. Instead, opt for using the lifecycle methods of a StatefulWidget.

- riverpod: A poor state management library with tight coupling, reliance on global variables, and side-effects. A better option would be to use bloc for state management and follow healthy dependency injection practices. More on this here: https://lnkd.in/dJKwbwsK and https://lnkd.in/dneDc5T7. Additional insights about riverpod can be found here: https://lnkd.in/deZpZH_C.

- logger: I'm not familiar with this one, but it’s often better to create your own custom logger, like the one in this template: https://lnkd.in/dha5d-UZ.

Good packages:
- mockito
- image_picker
- intl
- json_serializable
- freezed
- cached_network_image

By the way, I have my own template, that I recommend taking look as well https://lnkd.in/dz9FR5BG (it's free)

Sizzle Starter now includes a robust analytics solution and an implementation for firebase.

Check it out here

The next article will be UI Kit Part 2, where we'll cover custom components, breakpoints, adaptive design, animations, navigation, and more.

After that, I'm considering writing about managing Internet connectivity - specifically, how to detect and handle connection changes, how to implement proper management of data, BLoCs, and widgets, and how to automatically reload the data when the connection is restored.

What do you think? 👍

https://lazebny.io/state-management-and-business-logic

Coming tomorrow

A small example of how a generic bloc looks like:

https://gist.github.com/hawkkiller/c17563201247e53f2c1b0295f37e8903