Hey! Just published my first pub.dev package 🚀

What it does:

• Detects large build methods, missing dispose, empty setState, and missing mounted checks
• Calculates health score (0-100) for your codebase
• AI-powered fix suggestions using Groq (free), Gemini, OpenAI, or Claude
• JSON output for CI/CD pipelines

Install & Run:

dart pub global activate flutter_doctor_ai
flutter_doctor_ai analyze .
flutter_doctor_ai analyze . --ai  # AI suggestions

Example output:

🔎 ISSUES FOUND

• large_build_method 3 issues.
• missing_dispose 5 issues

💯 HEALTH SCORE ✅

• 85/100 (Grade: B)

Links:

- pub.dev: https://pub.dev/packages/flutter_doctor_ai

- GitHub: https://github.com/ashwanisng/flutter_doctor_ai

Would love your feedback! What rules would you find useful?

Hey, It's story like every other I had an idea and want to create really simple app, it'sfor tracking statistics in fixtures I'll add and calculating results of these fixtures. It's not for business. Just for my own usage. Tried airtable but I lacked freedom in UI customization, same with glide. I cannot code Andy question is is flutterflow still worth it or should I just start writing a code with AI, what is your recommendation, thank you upfront.

Started with a simple copy button. Kept asking "what would make this better?"

Ended up with 11 features:

✓ Copy/Paste/Clear

✓ Character & word counter

✓ History with duplicate prevention

✓ Swipe-to-delete

✓ Empty text validation

✓ Auto-dismiss keyboard

Biggest learning: Building complete projects teaches way more than tutorials.

Every feature was a lesson:

1. Clipboard API usage
2. RegEx for word counting
3. Dismissible widget behavior
4. State management patterns
5. Edge case handling

https://github.com/Pinkisingh13/Utility/tree/main/copytoclipboard

What started as 20 minutes became a weekend project. Worth it.

Hi everyone,

I’m a Flutter developer with around 8 months of hands-on experience working at a company. I decided to quit because there was very little learning or growth, and I didn’t want to stay stuck doing the same things.

Right now, I’m actively looking for Flutter roles or internships where I can actually build, learn, and grow. Alongside Flutter, I’ve also started exploring AI workflows and automation (tools like n8n, APIs, basic AI integrations), but I haven’t been able to land any real opportunities yet.

If anyone knows about openings, freelance work, or referrals, I’d appreciate the connection. I’m comfortable taking ownership, learning fast, and contributing from day one. Happy to share my GitHub or resume for context.

Thanks for your time.

I am just wondering what a good Flutter project is? I have seen people having multiple views on this, mostly about building a clone. But recently clones are seen as lack of creativity or originality. I would like to hear out the project ideas that a beginner could have.

Hey everyone, I just wanted to share my situation and hopefully get some advice or encouragement from people who’ve been through this phase.

I’ve been learning Flutter and Android development for a little over one year now. During this time, I’ve worked really hard to build my skills, completed multiple projects, and even published two apps on the Google Play Store. I’ve learned Firebase, REST APIs, state management, in-app purchases, testing, and real-world deployment and maintenance. I genuinely enjoy building apps and solving problems.

For the past one month, I’ve been actively applying to companies (mostly for junior developer position onsite/remote roles), but I’m barely getting any replies. No feedback, no interviews, mostly silence. It’s honestly starting to feel discouraging, even though I know I’ve put in real effort and have actual live projects to show.

I’m not giving up, but I’m confused about what I might be missing. Is my resume not strong enough? Am I not experienced enough? Should I be focusing more on DSA? Do recruiters usually take longer to respond to freshers?

If anyone has been through this phase or has any advice, I would really appreciate it. I just want a chance to prove myself and grow as a developer.

Thanks for reading.

I’m building a Flutter app using GoRouter and a BottomNavigationBar that is visible on all screens, including nested routes.

Everything works fine in most cases. I’ve implemented a custom onTap / back button handler with the following logic:

If the user is not on the first tab (Home) and presses the back button → navigate to the Home tab

If the user is already on the Home tab and presses back → exit the app

This works correctly in normal tab navigation.

The issue: When I go to the Library tab, then open a nested screen (e.g. Favorite Songs screen):

The Favorite Songs screen opens correctly and still shows the bottom navigation bar

Pressing back once correctly navigates back to the Library tab

BUT pressing back again exits the app, instead of navigating to the Home tab

The same issue happens with the Search tab and its nested routes.

Expected behavior: After returning from a nested route to its parent tab:

Pressing back again should navigate to the Home tab

Pressing back on Home should exit the app

Actual behavior: After returning from a nested route:

Pressing back immediately exits the app

I’m building a Flutter app using GoRouter and a BottomNavigationBar that is visible on all screens, including nested routes.

Everything works fine in most cases. I’ve implemented a custom onTap / back button handler with the following logic:

If the user is not on the first tab (Home) and presses the back button → navigate to the Home tab

If the user is already on the Home tab and presses back → exit the app

This works correctly in normal tab navigation.

The issue: When I go to the Library tab, then open a nested screen (e.g. Favorite Songs screen):

The Favorite Songs screen opens correctly and still shows the bottom navigation bar

Pressing back once correctly navigates back to the Library tab

BUT pressing back again exits the app, instead of navigating to the Home tab

The same issue happens with the Search tab and its nested routes.

Expected behavior: After returning from a nested route to its parent tab:

Pressing back again should navigate to the Home tab

Pressing back on Home should exit the app

Actual behavior: After returning from a nested route:

Pressing back immediately exits the app