Collection · updated 2026-06
Telephony & Product Analytics at Runo
Everything on this site about the hybrid telephony model and the analytics layer built around it, in the order it makes sense to read.
- 01
Runo Hybrid Telephony — Cloud & GSM Calling
Contributed to hybrid telephony support at Runo — letting users call via cloud or GSM, with call-medium selection, virtual number assignment, and consistent reporting across logs, exports, and analytics.
#telephony#flutter#call-medium→Start here — the hybrid telephony feature itself.
- 02
- 03
Runo Product Analytics & Amplitude Instrumentation
Worked on a product analytics layer at Runo — Amplitude provider abstraction, event taxonomy, user/company traits, deduplication, and platform-aware tracking across auth, billing, CRM, and call workflows.
#amplitude#event-taxonomy#flutter→The analytics layer that needed to report correctly across both calling modes.
- 04
Designing an Event Taxonomy for Amplitude
How to name events and properties so analytics stays usable as the product grows, instead of becoming hundreds of one-off strings.
#amplitude#product-analytics#event-taxonomy→The general taxonomy approach this analytics work was built on.
- 05
Keeping sandbox traffic out of production analytics
Why analytics initialization should check environment/host before sending any events, not just before reporting them.
#analytics#amplitude#patterns→A specific gotcha encountered while building the analytics layer.
- 06
Sizing an event deduplication window
A short note on why a fixed time window for analytics event deduplication needs tuning, not just existing.
#analytics#amplitude#patterns→The dedup heuristic referenced in the analytics work.