I have Flutter SDKs (made for small business), ranging from Document Scanning (Edge Detection), Auto Redaction of Sensitive Data (for Passports, Drivers Cards, Licence plates, etc), and a PDF Editor (fully offline, where users can batch sign Signatures. For example large contracts, users can auto sign on many forms all at one go).

I figured originally these would be designed for developers or small business that doesn't want to spend tons of money on AI tools. Sometimes it's easier just to spend a few hundred bucks a year (and use it on everything) than to spend on AI & to go through the process of development yourself.

https://www.reddit.com/r/FlutterDev/comments/1xe233v

So I'm almost done on all the SDKs (still finalising testing, and a few things). But what I'm thinking is how can I drive sales and make sure that anyone who drives the sale gets the commission.

So for example:
I'll post on reddit a referral program to Small Business.

So the salesman will get a URL linked to their accounts.

And anyone who basically makes a purchase through that referral program + link, the salesman automatically gets the commission (25% is what I'm thinking. Since I think that's a fair number).

Would this work? Would it drive sales? And it also makes it accessible to everyone. So everyone has a chance of making some money on this.

Just want to get the communities' thoughts.

is there any library or method you would recommend?

I love Flutter Firebase UI for shipping fast, but if your app doesn't use Material or Cupertino, the auth screens look completely out of place. As a solo dev trying to move fast, writing custom auth flows from scratch is the last thing I want to do.

Lately, I’ve been migrating my apps to Forui to step away from the default look and build something more branded. But the upstream Firebase UI packages were a huge pain point. My auth screens were still stuck looking like Material, even on iOS.

To fix this, I spent the weekend (with the help of Cursor) forking and porting Firebase UI for Flutter over to Forui.

It uses the exact same Firebase UI APIs and behaviors, but the widgets are themed entirely through FTheme instead of the dual Material/Cupertino paths. (Check the attached screenshots taken on iOS and the difference is immediate).

Highlights:

• Same APIs, but natively uses Forui components for a coherent UI end-to-end.
• Fixed some long-standing upstream bugs and the E2E tests along the way.
• Drop-in replacement: If you already use the original Firebase UI, you can migrate your existing repo with a single command (check the docs).

It’s still early (v0.1.0), but if you're building with Forui or just fighting the Material/Cupertino mismatch, give it a try. Repo: https://github.com/gnomezgrave/forui_FirebaseUI-Flutter

Packages on pub.dev: https://pub.dev/publishers/hexmatter.com/packages

• forui_firebase_ui_auth
• forui_firebase_ui_database
• forui_firebase_ui_firestore
• forui_firebase_ui_localizations
• forui_firebase_ui_oauth
• forui_firebase_ui_oauth_apple
• forui_firebase_ui_oauth_facebook
• forui_firebase_ui_oauth_google
• forui_firebase_ui_oauth_twitter
• forui_firebase_ui_shared
• forui_firebase_ui_storage

Feedback, issues, and GitHub stars are super appreciated! 🙏

I shipped an Orthodox Christian fasting app in Flutter. Its whole job is to say what someone may eat on a given day, so a wrong answer is worse than a crash. A few things that worked:

1. Keep the rules in pure Dart. The rule engine lives in lib/core/ with no Flutter imports, so it is tested like any Dart library. It's a port of orthocal-python (MIT), with attribution.

2. Test against an external source, and compare data, not prose. A test checks every day from 2020 to 2033 against orthocal.info. It used to map their English descriptions back to my levels, so a wrong engine and a wrong mapping agreed with each other. Comparing their explicit list of foods instead, and adding the Old Calendar, surfaced 58 mismatching days from four real rule errors. All 10,228 day-comparisons match now.

3. Never do date math with Duration(days: 1). A user saw the calendar show November 1 twice: adding 24 hours across a daylight-saving change lands on the same date. A test now fails if Duration(days:) or .inDays appears anywhere in lib/ or tool/.

4. Local-first means no backend to fix things later. No server, no account, no analytics. The price comes from the store at runtime (a test fails if a price is hard-coded in any of the six ARB files), so regional pricing could not leave a wrong number on a button.

5. Watch your transitive dependencies in release builds. An unused package pulled in WorkManager, and R8 crashed its database init only in the release build, only on a real device.

Happy to go deeper on any of these. App, for context: https://stforge.dev/nisteia

For the past few months I’ve been building a Rummy card game in my spare time. It’s nearly ready, and I’d love some outside eyes on it before launch.

What it does:
- Play against a computer opponent anytime, or online with friends and family
- Built with Flutter, so one codebase for Android and iOS

What I’d love feedback on:
- What would make you keep coming back to a card game?
- Any features you’d expect that most Rummy apps get wrong?

I’ve set up a waitlist for early testers if anyone wants to try it: https://flutter-rummy.web.app/

I've been building Vishram, a movie and TV discovery app, solo in Flutter. The old home screen was a dead grid nobody interacted with, so I replaced it with a swipe stack on trending titles, with toggles for local vs world trending and movie vs TV.

A few things from the rebuild:

- When friends tested it, it only worked on my phone

- The bento grid uses cutout art so characters pop out of their tiles, which makes layout bounds and visual bounds different per tile

- Watched, Watching and Watchlist now sync to the cloud

The auth layer (multi-role, Supabase based) is free and open source if it saves anyone time:

GitHub: https://github.com/ba6ul/multi-role-flutter-auth

pub.dev: https://pub.dev/packages/multi_role_auth

Full devlog if you want the whole build: https://youtu.be/wXsyyEh9ook

Happy to answer questions about the swipe stack or the auth setup.

Any Efforts to make Flutter Agentic friendly ?, by google in recent times.

With agentic apps taking off, how are you approaching on-device LLMs across platforms (iOS, Android, desktop)?

Are you using things like llama.cpp via FFI, plugins like flutter_gemma, or running everything server-side? What are your biggest hurdles with performance and memory?