I was looking for a short, cute animal-inspired name — something in the spirit of "Flipper".
+I turned my head and saw my golden retriever, Flocon, smiling to me... and that was it.
+That was all the inspiration I needed.
No brainstorming, no hesitation — just the perfect name at the perfect time.
+Flocon shows a real-time stream of analytics events emitted by your application. Whether you’re using Firebase Analytics, Segment, or a custom solution, the Flocon SDK can be plugged and forward these events to the desktop UI.
+Each event includes: +- The event name +- Parameters and metadata (key-value pairs) +- Timestamps
+This is especially useful for QA teams and product analysts to validate that the right events are triggered at the right time with the correct payloads.
+You can log events by identifying the source (e.g., "firebase", "segment", or any custom ID). Flocon Desktop will group events by these IDs.
floconAnalytics("firebase").logEvents(
+ AnalyticsEvent(
+ eventName = "clicked_user",
+ "userId" analyticsProperty "1024",
+ "username" analyticsProperty "florent",
+ "index" analyticsProperty "3",
+ ),
+ AnalyticsEvent(
+ eventName = "opened_profile",
+ "userId" analyticsProperty "2048",
+ "username" analyticsProperty "kevin",
+ "age" analyticsProperty "34",
+ )
+)
+Often, you want to forward all your app's analytics to Flocon. You can easily do this in your analytics tracking implementation:
+fun trackEvent(name: String, params: Map<String, Any>) {
+ // Forward to Flocon
+ floconAnalytics("app_events").logEvents(
+ AnalyticsEvent(
+ eventName = name,
+ params.map { it.key analyticsProperty it.value.toString() }
+ )
+ )
+
+ // Original tracking (e.g., Firebase)
+ firebaseAnalytics.logEvent(name, bundleOf(...))
+}
+