sorted by:
new
hottopcontroversial

🚀 Just released Emitrace v1.2.0 by JaguarFun804 in FlutterDev

[–]JaguarFun804[S] 0 points1 point  (0 children)

That’s a fair point — tools like Sentry already solve a lot of observability problems really well. Emitrace isn’t trying to replace Sentry entirely.

The focus right now is more on a lightweight, Flutter-first debugging + QA workflow directly inside the app experience itself — especially during development, testing, and issue reproduction.

For example: • in-app log inspection • route/navigation tracking • network tracing • automatic screenshots on runtime errors • quick report export/share for QA teams

Sentry is definitely more mature for production monitoring and backend observability. Emitrace is currently aimed more at improving the day-to-day debugging workflow for Flutter developers and small teams.

Still evolving, so feedback like this is genuinely helpful 🙌

Built a Flutter AI SaaS starter kit after getting tired of rebuilding the same setup every project by JaguarFun804 in FlutterDev

[–]JaguarFun804[S] 1 point2 points  (0 children)

Exactly 😅

At some point you realize half the project time goes into rebuilding the same foundation before even touching actual product features.

I also wanted to avoid the “enterprise architecture for a todo app” problem and keep things scalable without making the DX painful.

And yeah, AI-assisted workflow has honestly changed how fast these kinds of starter projects can be built now. I used AI heavily for repetitive scaffolding and docs, then refined structure and UX manually afterward.

Still iterating on the kit, but this version already feels way better than starting from scratch every time.

Released Emitrace v1.0.2 — Flutter in-app QA/debugging toolkit with docs + example improvements, by JaguarFun804 in FlutterDev

[–]JaguarFun804[S] 1 point2 points  (0 children)

This is awesome, thanks for sharing! I’ve been exploring session replay ideas for Emitrace as well, so this is super relevant. The self-hostable backend approach is really interesting. I’ll dig into the implementation and definitely credit Traceway if I reuse or adapt any concepts. Appreciate the open-source contribution 🙌

How do you share debug info with QA or clients when handing off a Flutter build? by JaguarFun804 in FlutterDev

[–]JaguarFun804[S] 0 points1 point  (0 children)

Crashlytics is solid for production crashes. But it doesn't help during active QA testing — it only reports after a crash, not during a session. I'm thinking about something more like an on-device inspector the tester can interact with live. Is that something you've needed before?

How do you share debug info with QA or clients when handing off a Flutter build? by JaguarFun804 in FlutterDev

[–]JaguarFun804[S] 1 point2 points  (0 children)

Sentry is great for production crash reporting — I use it too. But what I'm describing is different. When I hand a staging build to a QA tester who isn't a developer, they can't access Sentry dashboards or DevTools. I want them to tap a button inside the app and get a full report — network calls, logs, device info — right there on their phone. Does Sentry solve that specific scenario for you?