Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

news.ycombinator.com

Post reply on HN
Print view View original

101–110 of 118 posts

Re: Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

#101

Post by alexdanilowicz »

sizzle wrote: post #93
alexdanilowicz wrote: post #68

Earlier quoted context omitted.

1. We're using Sonnet 3.7 for the first prompt. I've noticed with some prompts that require lots of files it can be PAINFULLY slow. Our servers also might be getting slammed from the HN traffic. We have a "fast" mode that uses 3.5 that you can toggle and that's the default for editing, however, it won't be as visually rich. We need to improve the loading experience for sure. One big UX/UI difference between our produ…

Don’t change your pricing model based off n=1 go do some market research first. Don’t kill your adoption rates in the critical early days of growth.

We have been around for 2 years and at one point had "contact us for pricing", so don't worry not changing anything on n=1!

Re: Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

#102

Post by alexdanilowicz »

mattfrommars wrote: post #99

What does this look so similar to v0 from Vercel?

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.

Re: Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

#103

Post by alexdanilowicz »

arcanelegender wrote: post #97

I uploaded a screenshot twice but it keeps saying "Sorry, I don't see a screenshot!"

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.

Re: Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

#104

Post by alexdanilowicz »

robertlagrant wrote: post #98

This is a very good idea. I see a lot of friction (and lack of process) with product -> UX -> dev than with product and dev able to iterate on things like screen flows very quickly, and UX feeding in more from the user research angle. Currently a lot of UX work is "translate what you said into Figma and wait for comments" which is very automatable, and I think frustrating for UX people as much as anyone.

100%. This is what we hear and see from our customers, many now skipping Figma entirely.

I shared this post before below, but to share it again: https://www.linkedin.com/posts/stephenwitmer_you-gotta-love-...

Re: Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

#106

Post by alexdanilowicz »

_betty_ wrote: post #96

Canvas is an interesting idea - although the implementation feels very clunky and half finished. rest of the tool doesn't feel that special - eg there's tonnes of code generators out there. would have to play more to understand but it wasn't immediately apparent

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.

Re: Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

#108

Post by leerob »

alexdanilowicz wrote: post #102
mattfrommars wrote: post #99

What does this look so similar to v0 from Vercel?

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 desig…

Y'all are doing amazing. Keep it up!

Re: Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

#109

Post by _betty_ »

alexdanilowicz wrote: post #106
_betty_ wrote: post #96

Canvas is an interesting idea - although the implementation feels very clunky and half finished. rest of the tool doesn't feel that special - eg there's tonnes of code generators out there. would have to play more to understand but it wasn't immediately apparent

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…

Lack of tools (shapes, cards etc)

Also felt very laggy/buggy when selecting, dragging etc. may be my underpowered rig

Re: Launch HN: Magic Patterns (YC W23) – AI Design and Prototyping for Product Teams

#110

Post by _betty_ »

_betty_ wrote: post #109
alexdanilowicz wrote: post #106

Earlier quoted context omitted.

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…

Lack of tools (shapes, cards etc) Also felt very laggy/buggy when selecting, dragging etc. may be my underpowered rig

Also just how separate the tool was - it was the primary reason I checked out the product but felt I had to go searching to find it.

Maybe a add to canvas/project button in the code gen area.

Post reply on HN