co-founder of Magic Patterns here, saw were were mentioned, figured I'd chime in:
We don't use Trigger for marketing at all and I actually never thought of it for that use case.
We're an AI design tool - prompt to create an interactive mockup - and we use Trigger to take screenshots of designs to provide a preview image. Taking a screenshot sounds easy, but it's not because Puppeteer constantly hits OOM errors. So you need a high-end machine, and so it can get expensive. We originally were using a homegrown solution, a microservice, but it would constantly crash (even though were paying $$$$$ for it).
Trigger spinning up jobs was perfect and we migrated in a day and now I never think about it.
Can you expand a bit on this use case? Why would Puppeteer constantly crash on your own high end machine, but not on Trigger's infra? Puppeteer doesn't care where it runs, so it would be nice to understand how Trigger's infra works around this problem.
As someone who currently "bricks" his phone and has gamified it a bit by sharing my stats with my brother-in-law who also does that, this is cool. I do think "not spending time on your phone" needs to be celebrated more.
P.S. "bricks" meaning a very strict screentime set up, only basically phone + text is available M-F
We always iterating and definitely need to improve! Anything you can point to explicitly that makes the canvas feel clunky/half finished? We're using a simple div under the hood!
To add some color: while we do generate code, we don't view ourselves as a code generator because our customers don't get value out of our tool from the raw code. They instead receive value from the interactive prototype, and for that reason it's lot of PMs, designers, founders using us versus developers.
I just had a cool experience with it doing some simple design. It prompted back to me usefully as well.
I can imagine also uploading a component library that this thing then uses the components from, to add styling for higher-fidelity designs, and allow app designers/builders to just use the components built by an internal team (who might also use magic patterns, I suppose).
oof! this is a bad bug that seemed to tick up overnight! Fixing this, thanks for flagging. If you create a support chat via "Get Support" or DM me happy to throw you some credits and regenerate it for you.
I mention this in another comment: v0 has been around as long as we have (October 2023), so it's very cool seeing how we have both iterated on the same problems, especially given Vercel is a $3B company and we are a team of two :-)
We have both evolved a lot and now have some major differences, given we focus on product teams more than developers:
- Magic Patterns has an infinite canvas
- Password protection on designs
- Feedback collection on prototypes
- Reusable components, so you can create a component library with us and then reference those components in your design
- We are only focused on frontend
A few customers actually use both us and v0! For example, they'll design in Magic Patterns and then copy paste the code into v0 to add a database.
I wouldn't be scared because in practice we don't see this! Instead we see 1. devs appreciating getting an interactive mockup and 2. the PM having a better sense of what it's like to build technically. (It's pretty cool seeing how AI tools like Magic Patterns help non-technical software professionals naturally learn more about web dev concepts because the best prompts reference code.)
At big companies, Magic Patterns designs are used created & used at the beginning of the product lifecycle for brainstorming and iteration. And there's still a human in the loop in the process: the PM prompting Magic Patterns. The value we create is not the actual raw code, and so we are not seeing teams telling their devs to simply "polish" it. The handoff still is very similar to most dev/design handoffs today, except it's a Magic Patterns design versus a Figma design.
We don't use Trigger for marketing at all and I actually never thought of it for that use case.
We're an AI design tool - prompt to create an interactive mockup - and we use Trigger to take screenshots of designs to provide a preview image. Taking a screenshot sounds easy, but it's not because Puppeteer constantly hits OOM errors. So you need a high-end machine, and so it can get expensive. We originally were using a homegrown solution, a microservice, but it would constantly crash (even though were paying $$$$$ for it).
Trigger spinning up jobs was perfect and we migrated in a day and now I never think about it.