Hey HN, excited to share our open source tool with the community. We wanted to build an open source omnichannel tool where you can design customer journeys with a drag and drop editor.
You can use our tool for example to design an onboarding flow so that users who sign up to your site can receive a series of predetermined emails and sms. Give it a spin and let us know how we can improve it. We also made it so you can self host.
Ex adobe eng here worked on our similar project - looks great always thought there should be an open source alternative as marketing tech becomes more complex.
The hard thing here is making something that scales with millions of messages, have you thought through how you may handle that?
Hello GitHub. I'm willing to pay for a service that deploys a demo instance of the repo. You can craft a nice little button named "Demo" and when I click it, you'd send me back an URL and credentials to the app itself. Last, but not least, please share a cut of the deployment fee with the repo core maintainers. Thanks
Ex adobe eng here worked on our similar project - looks great always thought there should be an open source alternative as marketing tech becomes more complex. The hard thing here is making something that scales with millions of messages, have you thought through how you may handle that?
Hey, cofounder of Laudspeaker here. At a high level, there are two main problems to solve for when it comes to scaling this type of system. One is the ability of your infrastructure to handle resource intensive customer requests (sending 10 million emails) that are instantiated at arbitrary unpredictable times—this sort of work is usually best handled using job queues and job processing threads that are horizontally scalable. The second is the channel specific failure modes that are common at higher message sending volumes, for example IP blacklisting by spam filters for email, or sending the same notifications repeatedly when dealing with mobile push. We’ve set up our architecture to tackle the first problem and are currently performing stress testing to find and fix any bottlenecks there; with respect to the second type of problem, we are actively experimenting with ways to mitigate these failure modes as our product matures.
Hello GitHub. I'm willing to pay for a service that deploys a demo instance of the repo. You can craft a nice little button named "Demo" and when I click it, you'd send me back an URL and credentials to the app itself. Last, but not least, please share a cut of the deployment fee with the repo core maintainers. Thanks
Hello GitHub. I'm willing to pay for a service that deploys a demo instance of the repo. You can craft a nice little button named "Demo" and when I click it, you'd send me back an URL and credentials to the app itself. Last, but not least, please share a cut of the deployment fee with the repo core maintainers. Thanks