Analytics Developer (Smart Router)

Analytics event routing standardizes how events flow to the Anytype iOS analytics system by enforcing typed route enums in AnalyticsConstants.swift and centralized event methods. This ensures consistent event definitions and property keys across screens, coordinators, and data models throughout your codebase.

Route tracking captures user navigation by defining route enums, applying them through AnytypeAnalytics+Events.swift methods, and passing route context into screen and button analytics. This preserves navigation flow context using .compactMapValues to handle optional properties cleanly.

Define a route enum in AnalyticsConstants.swift, create a method in AnytypeAnalytics+Events.swift for your event, then call AnytypeAnalytics.instance().logYourEvent(...) from your ViewModel or Coordinator, passing route context as a typed parameter instead of string literals.

String literals for routes create inconsistency, typos, and make refactoring difficult. Typed route enums in AnalyticsConstants.swift provide compile-time safety, enable IDE autocomplete, and ensure all route tracking uses the same definitions across screens and data models.

Yes. The Skill applies to multi-space events by using AnalyticsEventsPropertiesKey for event keys and route context across spaces. Define space-specific route enums and apply them through the same centralized AnytypeAnalytics+Events.swift pattern.

Route context combines screen identifiers, coordinator names, and user navigation state. Use AnalyticsEventsPropertiesKey for typed property keys, apply .compactMapValues { $0 } to optional properties, and pass route enums instead of raw strings to preserve the full navigation context in each event.