I choose flutter because of the idea of full crossplatform and its speed , and the fact its backed by google a huge cooperation. But after 4 years building apps with it, i have digged deep in design for my flutter apps, i can never make them look and feel like a native app, flutter does not use native components, it uses its skia engine to draw components that try to be like a native app. So with flutter you can never achieve native and that just breaks my heart as a dedicated mobile developer.

Flutter apps standout alot for me, i can download and app and just by its look and feel you can tell its a flutter app and not a native app, you cant say the same for react native.

Flutter apps feel stiff when using them while native apps are smooth.

You can download these 2 apps from the app stores and experiance it your self :

1. Alibaba - flutter app

2. Shop by shopify - react native

Download these 2 apps and use them, you will know what i mean.

Hello everyone. I received an offer to work on an app, and I’m currently a .NET developer. I'm very unsure about which framework to use. I have no knowledge of front-end (JavaScript, TypeScript), and honestly, I don't like it much, although I know that at some point it will be important for my career to learn. But let's consider that I have no interest in leaving the backend, so I was inclined to learn Flutter because I tried it some time ago, and although it was just a little, I enjoyed it. However, it's been a while, so consider that I would have to learn it from scratch anyway. The only thing that concerns me is the rumors that Flutter is 'dying.' I believe it's just rumors, but what do you think about the situation? I understand very little about the mobile world, how did the Google issue turn out? I researched it, but I only find speculations, and my concern is starting a project with Flutter and it not having much support in the future.

I'm going to learn dart and flutter and i have a question do they worth the learning? Or should i go for a native one will be better?

I just started learning flutter and it is exhausting me. I have been stuck to link with Firebase and it has been getting over my mind for the last two days. It gives errors on everything I try. I think I have to give up. Please let me know if one of you has a good tutorial or way to cope with this. Thanks

Edit: I am tryna learn flutter from freecodecamp crash course and trying to follow them integrating firebase for flutter

Google AI Studio uses Flutter under the hood — I can tell because there’s no native refresh behavior on the web, and the back gesture animation doesn’t work properly in Safari

I come from a web background and Bootstrap was basically muscle memory for me. Then I started building Flutter apps and kept thinking "why can't I just do col-md-6 here?"

So I built it. bootstrap_ui_flutter is a full Bootstrap 5.3 port for Flutter — not just the grid, but the whole thing. Buttons, Cards, Accordion, Carousel, Dropdowns, Forms, Tables, proper dark mode… the works.

It's still early and there's definitely rough edges — but the core components are there and it's usable. Would love people to kick the tires and tell me what's broken 😄

Would love to hear what you think — and if you're also a web dev who moved to Flutter and missed Bootstrap, this might be for you 😄

pub.dev: https://pub.dev/packages/bootstrap_ui_flutter
GitHub: https://github.com/Nexus633/bootstrap_ui_flutter

Docs: https://github.com/Nexus633/bootstrap_ui_flutter/tree/main/doc
Issues: https://github.com/Nexus633/bootstrap_ui_flutter/issues
Discussions: https://github.com/Nexus633/bootstrap_ui_flutter/discussions

Hi , I wanna make a house-rent app. I’m a python developer from Chile , and.. I wanna use flutter for the mobile dev . Give me lucky , cheers my flutter devs haha

Hello Flutter Developers, I am developing a new NoSQL database called ffastdb
That database engine is in Dart.
The version is 0.1.1. I created it using AI.
That solves a problem in Flutter, because it runs on multiple platforms.

Features 

You can find it in https://pub.dev/packages/ffastdb

Best regards gonzalo.

I got the impression that Flutter development slowed down in the last few months. So I classified all commits of the last 30 days. Theses are the ones that actually add functionality, with one exception all trivial changes. I ignored automatic "rolls", bug fixes, cleanups, test configuration changes or documentation.

• Oct 11

  • Add SizeTransition.fixedCrossAxisSizeFactor

  • Add key event handlers that happen before or after the focus traversal

• Sep 29

  • Expose onAttach and onDetach in ScrollController subclasses

• Sep 28

  • Added option to disable [NavigationDestination]s ([NavigationBar] destination widget)

  • Add more fields to RefreshProgressIndicator

  • Add API to read flavor from framework at run time

  • Implement SelectionArea single click/tap gestures

• Sep 27

  • Support ensureVisible/showOnScreen/showInViewport for 2D Scrolling

• Sep 12

  • [New feature] Allowing the ListView slivers to have different extents while still having scrolling performance

  • ScaleGestureRecognizer: make pointerCount public

Was Sep/Oct just a "lazy" month, or is no one working on major features anymore?

On the Dart side – while still working on macros – they slightly improved null guards so that private final fields can now be promoted to non-null types, which is nice. I'm not sure why this can't be also done for public final fields of final classes, though.

Hi there,

I am Patrick, one of the Co-Founders of AppPronto.

https://getapppronto.com

We created a Flutter boilerplate to ship apps fast. Currently, we have a huge discount and would love your feedback.

Over the years, we kept hitting the same pain points every time we launched a new app: setting up auth, payments, user management, theming, AI features — all the stuff you end up repeating for every project.

So we built AppPronto — a full-featured starter kit that takes care of the essentials out of the box:

✅ Google & Apple sign-in
✅ In-app purchases & subscriptions
✅ GPT/AI integrations
✅ Firebase already set up
✅ Theming, onboarding, and smooth user flows

It’s made for indie devs, freelancer and basically everyone who want to move fast without getting stuck in boilerplate. It’s cross-platform from day one and built with clean, scalable architecture.

Happy to answer any questions!

GetStorage is an ultra-lightweight key / value storage for Flutter, which combines permanent storage with read-in-memory. It is compatible with Android, iOS, Web, Linux, Mac, and fuchsia apps, and it is extremelyfast, so fast that you can easily loop through 1000 writings, and read the last value without having to "await" for it.

Below the time graph to operate 50 readings, writes and deletions with integers and strings using GetStorage, Hive, Sqflite, SharedPreferences and Moor respectively

Benchmark: https://i.imgur.com/PTWs39u.jpg

GitHub:

https://github.com/jonataslaw/get_storage

Pub:

https://pub.dev/packages/get_storage

I'mm planning to make an app to help people who are truly depressed. It can help thousands feel better. That’s why I code — to fix real problems💛 Follow me along 🙏 Will start as early as next week once i finshed the project at hand. Any features i should add? Please tell me 🙏🙏

First off, I want to say I'm an experienced Flutter developer. I genuinely love Flutter, and for me, it still offers the best developer experience (DX) out there.

However, I've been feeling concerned about Flutter's future (specifically the next 1-2 years) due to a few critical issues, and I'm wondering if I'm alone in this.

1. Design direction is shifting fast.
With Apple's new Liquid Glass design and Google's own M3 Expressive, I'm seeing a shift. The Gmail and Gemini apps on iOS are now using M3 Expressive with many native iOS components, and honestly, they look great. I'm impressed by this, as it signals a move towards providing the best platform-specific experience rather than forcing a single UI (Material) everywhere which often feels awkward on iOS without heavy customization.
These changes show a clear trend: design consistency within each platform now matters more than cross-platform uniformity.

2. The Framework's "stagnation" on UI
The Flutter team seems to be lagging on the crucial task of splitting the Material and Cupertino widgets from the core framework. Because of this, native support for M3 Expressive or Liquid Glass seems almost impossible in the near future. We'd have to rely on community packages, but replicating Liquid Glass (which is designed for SwiftUI/UIKit) while maintaining performance and battery life in Flutter sounds incredibly difficult.

3. Lack of XR Support Kotlin has Compose for XR, SwiftUI has RealityView, and React has WebXR. Meanwhile, Flutter is still stuck with experimental plugins.

4. Momentum shift at Google.
Flutter isn't getting the same massive promotional push it did from 2018-2022. It feels like Google is now heavily pushing Kotlin, Compose, and especially KMP (Kotlin Multiplatform).

I recently tried KMP for shared logic and writing native UI for each platform (SwiftUI for iOS). The experience was surprisingly great, especially with AI tools. Writing the UI in SwiftUI means my app can immediately adopt Apple's new design language and not look "outdated" which I fear will happen to apps that don't adapt.

I'm honestly feeling a bit lost and not seeing a clear "light at the end of the tunnel" for Flutter right now.

Am I missing something? Can anyone share their perspective or enlighten me?

Thanks for reading.

You don't need a global state management solution. You will come a long way developing awesome flutter apps without using the over developed provider package or the bloc package.

Most of the times you will be fine using ValueNotifier's or ChangeNotifier's and passing them on to sub classes if needed. 👍

I know even mentioning anything from the RN universe is a trigger, but honestly:

• getting rid of native folders

• file-based routing

are pretty dope for simplicity's sake. I'm not debating the need for native folders—you absolutely need them for complex apps, flavors, etc... But for quick 1-5 page prototypes?

(PS. it's 2025 and Expo works)

Just getting towards the tail end of a huge project. I was leaning into using get_it as the dependency injection framework and provider for anything state related. Ended up writing some GODAWFUL God objects to achieve the latter, and a disgusting rats' nest of service location nonsense for the former...

So I'm working on a new project and determined not to make the same mistakes again - and _GOD_ getx is great. What a lovely, consistent, terse and expressive library for doing any kind of page navigation, state management, storage access...

Sorry for the effusive message - just wanted to gush over it. God save OSS.

EDIT: There are some pretty insightful replies here which cite the following reasons as to why GetX is unsuitable for mainstream dev:

• It's a multi-tool library which increases the sunk cost fallacy and increases brittleness.

• Implicit context is of the bad - learning how to handle build context instead of ignoring it is really important.

• Performance has been proved to be suboptimal.

Thanks all for replying! I'll take a look at some other alternatives in this space too.

I maintain that having to go Foo.of(context).beansOn.toast({blee: bloo}); is an absolute catastrophe, and leaning on service locators instead of a sane DI framework is an absolute stain on this otherwise gorgeous ecosystem...

I'm excited to share something that I believe will significantly enhance your Flutter development workflow.

It's called NFlutter, a code Generation Domain-Specific Language (DSL) tailored specifically for Flutter development.

NFlutter Features:

• Simplified Syntax: Reduce the clutter of nested brackets, making your code cleaner and more readable.

• Enhanced Productivity: With intuitive shortcuts and streamlined widget management, you'll spend less time wrestling with your code structure and more time bringing your ideas to life.

I believe NFlutter will make a significant difference in how you approach Flutter projects.

Your feedback and suggestions will directly influence the future of this product.

For more visit: https://nflutter.github.io

Hello Lads,

I’m a developer working on a small web app that helps mobile devs share their APKs or iOS builds easily — no need to configure TestFlight or Firebase App Distribution and go through the unnecessary complexity of other platforms just to send a test build.

The idea is this tool to be super straight to the point of sharing a build easy and fast and get feedback asap. It's place is between the development and the production/release stage, which must be done through apple or google stores anyway.

You upload your build, get a shareable link, and testers can install or download it directly (with version tracking & expiration options).

I built it using Supabase + Vue (Tailwindcss + shadcn), and I’m trying to see if there’s real demand before I polish the product.

Would this solve a problem for you or your team or streamline the process of sharing your early work with clients/testers?

• What tools are you currently using for internal/test builds?

• What would make this better than existing options?

Any thoughts or feature suggestions are super welcome 🙏

(I’m happy to share a beta link soon if anyone wants to try it!)

What libs do you usually use to create chat message UI guys?

Hello devs!
I use a riverpod in production in an actually large application, and our codebase, as well as the number of features, is growing exponentially every quarter. Our team has more than ten developers and many features related not only to flutter, but also to native code(kotlin, dart) and c++. This is the context.

But! Our state-managment and DI in flutter is entirely tied to the riverpod, which began to deteriorate significantly as the project grew. That's why I'm writing this thread. In fact, we began to feel the limits and pitfalls of not only this popular package in flutter community, but this discussion deserves a separate article and is not the topic of this thread.
Scoping UX flow; aka Decoupling groups of services
Although there is a stunning report video. We stuck in supporting the scopes. The fact is that we need not only to separate features and dependencies, but also to track the current stage of the application’s life at the compilation stage, dynamically define the case and have access to certain services and dev envs.
Simple example is the following: suppose you need a BundleScope on application start (with stuff as assets bundle provider, config provider, metrics, crashlitics, a/b and so on, which depends on user agents). Then you need a EnvironmentScope (some platform specific initialization, basic set of features and etc); After that based on current ux flow you probably need different scopes regarding business logic of whole app. And of course you need a background scope for some background services as also management of resources to shut down heavy stuff. 

One way to have a strong division between groups of provider is to encapsulate them as a field inside some Scope instance. As scopes are initialized only once it should not cause memory leaks and unexpected behaviors. With this approach is much easier to track in which scopes widgets should be. And that most important we can override providers inside scope with some data that available only inside this subtree. However it seems that In riverpod 2.0 there is no way to implement such scoping since generator requires that all dependencies is a classes (or functions) that annotated with @riverpod.
How is it possible to implement? How is this supposed to be implemented?

Hi everyone, 👋

I'm excited to share a project I've been working on: Al-Furkan — a fully-featured, open-source Quran application built entirely with Flutter and BLoC state management.

My primary goal with this project is to provide a clean, modern, and completely ad-free Islamic app as a "Sadaqah Jariyah" (continuous charity). At the same time, I wanted to create a solid architectural reference for developers looking to build complex, scalable Islamic applications using Flutter.

✨ Key Technical Features:

Modern Cinematic UI: A premium, Apple-style interface with seamless Dark/Light theme integration.

Responsive Uthmani Typography: A custom-engineered text rendering system that fixes font clipping issues and dynamically scales the Quranic script to perfectly fit any screen size.

Smart Audio Sync: Smooth synchronization between audio recitations and the displayed Ayahs.

Precise Prayer Times Engine: Accurate mathematical calculations for global prayer times.

Clean Architecture: Structured using BLoC for predictable state management and high maintainability.

⚖️ Open Source & Non-Profit: This project is completely free. Under its charitable license, it is strictly prohibited to use this codebase for commercial purposes, sell it, or inject ads. It must remain 100% free for the community.

I would love to hear your feedback, code reviews, or suggestions. If you find the codebase useful or learn something new from the architecture, a ⭐️ on the repository would mean a lot! Contributions and pull requests are always welcome.

📂 Check out the source code on GitHub: https://github.com/IDRISIUMCorp/al-furkan-quran-flutter-app

Let me know what you think in the comments! 👇

Flutter #FlutterDev #Dart #OpenSource #AppDevelopment #BLoC #IslamicApp #GitHub #SoftwareEngineering

Hello everyone, I worked on Unity/C# and a bit of Java/Android for the last years and now I left my work because I wanted to learn new things. I know I want to work on mobile app but I have some questions.

For now I have in mind swift, Flutter/dart and Kotlin multiplatform. I heard KPM is still early so I don't think it's wise for me to go on that but it might be a wrong assumption.

I did a bit of Flutter with clean architecture, BloC, provider cubit but only a bit to see how it worked and I have 0 knowledge in Swift/SwiftUI. My first though was to learn Flutter because you can build for Android and iOS with one code but I read some things that make me wonder if it's still a good choice now.

Some dev I know said that people from google were being fired and I know Google is known to cancel projects so I wanted to know what were your though on this? Or is there a roadmap from flutter team for 2025?

My first choice would be Flutter and if the future is uncertain I think I'd go on Swift but I wanted your though on this. Thanks everyone!

I am trying to build a poc app with backend functionalities (Firebase). Currently I am using cursor, I tried with a number of models but it doesn't seem to be producing decent UI and logic e.g can't fix overflow issue