Sequences design document

[Yopi]

The idea and proposal behind groups of events and sequences.

[pieterbeulque]

True, but I'm having trouble thinking of a reasonable reason to do this.

Why would you want to compare e.g. a single sequence "workout_tracking" with "nutrition_tracking" in a fitness app? I could see how globally you want to know the average cost of tracking a workout and tracking food intake but you'd never compare an instance of each side by side.

In other words you want to compare apples to apples, oranges to oranges, and additionally are interested in both the average apple and average orange.

[Yopi]

I was thinking about when you want to track e.g.

• nutrition_tracking (outcome: ate balanced)
• nutrition_tracking (outcome: ate too much candy)

How often does users eat balanced vs too much candy. If you have multiple sequences that are tracking the same events you might want to start to compare the outcomes of those sequences.

When it comes to fully disparate sequences, then I fully agree that it does not make sense to want to compare them

[pieterbeulque]

• Nutrition Tracked (no success)
• Nutrition Tracked: Balanced (success: ate_balanced)
• Nutrition Tracked: Cheat Day (success: too_much_candy)

But yes, I get what you're after, eventually you'll want to run numbers balanced <> cheat day, maybe.

But that's solvable outside of the scope of this design, no, it's more dashboarding than anything else.