Flutter Heroes
📈 Analytical overview of Telegram channel Flutter Heroes
Channel Flutter Heroes (@flutterdev) in the English language segment is an active participant. Currently, the community unites 21 959 subscribers, ranking 6 053 in the Technologies & Applications category.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 21 959 subscribers.
According to the latest data from 14 November, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -219 over the last 30 days and by -8 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 6.45%. Within the first 24 hours after publication, content typically collects N/A% reactions from the total number of subscribers.
- Post reach: On average, each post receives 1 416 views. Within the first day, a publication typically gains 0 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 1.
- Thematic interests: Content is focused on key topics such as developer, firebase, widget, hemantpra389, engineer.
📝 Description and content policy
Channel description not provided.
Thanks to the high frequency of updates (latest data received on 15 November, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
yield state.copyWith( user: user, ); add(const MyBloc.privateEvent1()); }, privateEvent1: (event) async* { List<Post> posts = await loadPosts(); yield state.copyWith( posts: posts, ); if (something) { add(const MyBloc.privateEvent2()); } }, privateEvent2: (event) async* { List<Draft> drafts = await loadDrafts(); yield state.copyWith( drafts: drafts, ); }, ); ```This method seems to ensure that the code in each event is short and readable. It also more or less respect the single responsibility principle by allowing one API call per event.A drawback I find with this method is that the more private events and condition you have the more complex it becomes to keep in mind how the entire logic flow. I have to admit that I had to use drawio to have a visual representation of the logic flow.I haven't been able to found any significant performance issues even with 10+ consecutive private events.One event - One stateThis one is the simplest way to structure your bloc. An event is triggered, you fetch/load all the data you need for this event and then you yield them all.Here's a visual representation of how it works:Event Data loaded Data loaded Data loaded Yield stateHere a code example:```dart yield* event.map( publicEvent: (event) async* { User user = await loadUser(); List<Post> posts - await loadPosts(); List<Draft> drafts = <Draft>[]; if (something) { drafts = await loadDrafts(); } yield state.copyWith( user: user, posts: posts, drafts: drafts, ); }, ); ```This method has the merit of being direct. You have everything you need in one place and it's easy to have a visual representation of the logic flow.The problem I personally have with this method is having this much calls in one place. The more data you need to fetch/load and the more condition you have, the more bloated the code becomes.Overall I don't have a preference for either of these methods and I use them as I see fit but I would like to have a method that I can use all over my codebase for consistency reason.If you have your own way of structuring blocs please feel free to share, hopefully, we'll be able to find a "universal" structure.
December 02, 2020 at 12:02PM by SSebigo
https://ift.tt/3lzCs2B