u/JaguarFun804

Most bug reports from QA/users are still basically:
“app crashed” 😅

…without enough context to reproduce issues quickly.

So I started building a lightweight in-app debugging workflow around:

• route tracking
• logs
• network calls
• screenshots
• event timeline
• report generation

Latest update added:

• route observer support
• manual APIs for events/actions/errors
• better timeline tracking
• improved report export

One thing I’m trying hard to avoid is turning it into over-engineered “enterprise architecture” too early.

Current goal is mainly:

• better debugging workflow
• easier issue reproduction
• lightweight integration for Flutter apps

Curious what other Flutter devs are currently using for:

• production debugging
• QA workflows
• user issue reproduction
• session tracking

And what’s the most annoying part of debugging Flutter issues for you right now?

🔗 GitHub: https://github.com/RITIKKUMAWAT009/emitrace
🔗 pub.dev: https://pub.dev/packages/emitrace

Over the last couple of years working with Flutter, I noticed I kept rebuilding:

• auth
• routing
• architecture
• reusable widgets
• API setup
• onboarding flows

So I decided to create a reusable production-style starter foundation for my own projects.

Current stack:

• Riverpod
• GoRouter
• Dio
• Firebase Auth
• Gemini API

Features included:

• onboarding flow
• demo auth mode
• Firebase-ready auth
• AI chat screen
• dark/light theme
• reusable widgets
• loading/error states

One thing I tried focusing on was keeping the architecture scalable without over-engineering it.

Would genuinely love feedback from other Flutter devs on:

• folder structure
• DX
• architecture decisions
• things you’d improve in a starter project like this

Demo:
https://youtube.com/shorts/o01aq8faMLY?feature=share

It’s an in-app debugging / QA toolkit for Flutter apps that helps capture:

• Logs / breadcrumbs
• Network requests
• Runtime errors with screenshots
• Debug reports
• Slack summaries

Built it after facing repeated QA/debugging pain in production apps.

Would genuinely appreciate feedback from Flutter devs on:

• Missing features
• API design
• DX improvements
• Real-world use cases

Pub.dev: https://pub.dev/packages/emitrace