Also something that irks me is that all these platforms design DAGs as journeys. Journeys are fine but they're inherently value capped. A user is only supposed to go through an onboarding journey once or a memorial day sale journey once.
What I really want as a mobile app dev is loops. I want to be able to say "Run this every day, send a user a push or email at 10am. wait until 6pm. if the user hasnt opened the app yet, send another push based on a different template".
Currently we have a whole ass subproject dedicated to defining these flows. whats worse is that its hard to ab test flow and impossible for anyone non technical to set up a loop. Please build this, we'll pay you sweet sweet MRR if you do.
Our plan is to model loops by having journeys define re-entry conditions, allowing users to run through journeys multiple times on a schedule. Would love to talk, to learn more about y'all are doing.
My email is: max@dittofeed.com, or feel free to ping me on our community slack!
Also something that irks me is that all these platforms design DAGs as journeys. Journeys are fine but they're inherently value capped. A user is only supposed to go through an onboarding journey once or a memorial day sale journey once.
What I really want as a mobile app dev is loops. I want to be able to say "Run this every day, send a user a push or email at 10am. wait until 6pm. if the user hasnt opened the app yet, send another push based on a different template".
Currently we have a whole ass subproject dedicated to defining these flows. whats worse is that its hard to ab test flow and impossible for anyone non technical to set up a loop. Please build this, we'll pay you sweet sweet MRR if you do.