teddarific

Definitely — we've seen some pretty crazy high fidelity mock ups from our customers who spend hours and hours prompting away, and they genuinely blow my mind. it's honestly why we spend so much time working on the application layer (e.g. making it easier to feed context into your prompt, referencing other designs, etc) since we know that the LLM is capable of these things, it just takes much more time than most people are willing to put in.

would love to hear what you think when you give it another try!

Awesome to hear — our goal is to get to a point where you can copy/paste the design, but we totally recognize that it doesn't always get you to a full high fidelity mock up with the current limitations. So the main use case we've seen a lot of success with is ideating and validating different branches, quickly.

Oh that sounds very neat — definitely similar in nature! Documents and UI are both complex and can require a lot of iterations to get right

Other tools are AMAZING for spinning up actual fullstack apps and use cases that require persistent storage. But actual product teams aren’t asking for that.

Also, our customers tell us that anecdotally it feels like we error less compared to other tools because we are focused entirely on frontend (there’s less room for error). Of course, we still error a lot - not easy when natural language is your input set!! - but it helps to stay focused and theres less dependencies on a backend & database.

p.s. one of my personal favorite parts of Magic Patterns is that you can very easily revert to a previous version, which is possible because no backend or database!

other Magic Patterns co-founder here —

to add on to Alex's answer above, we also differ in that we have a lot of features focused around brainstorming / exploring ideas, versus just spinning up a fullstack app. For example, we have a "Commands" feature that lets you get four variations (that are guaranteed to be different!) of a prompt.

We also have a Chrome extension that lets you import designs from your existing product to ideate on top of existing content.

i hate working with DBs via command line, so this looks really cool. curious if your product resonates with a specific segment of developers, e.g. frontend vs backend? Hoping this can entirely replace me needing to do anything DB related in the comamnd line...

The entire disappearance of semantic HTML tags has been sad to see. It's just all <divs> inside of <divs> inside of <divs> these days.

Am curious on the O(n) calculation as well haha — I get what OP is saying, but would love to know if there's some deeper technical details here.

hey! other co-founder here — yeah, it does go through our backend systems for processing. We also store it in our db so people can iterate on it further in our web app. At the moment, no designs created via our extension are actually featured in our public catalog, but we do also support a private option for those folks who need private designs!

I originally thought that too but learned yesterday they have their own model. Definitely explains how its so fast and accurate!

This is neat. I worked on something similar to college where we built an app to track how long the line was at a popular cafe. We set up a camera + raspberry pi in the cafe and tried to the number of people. There was a lot of noise from overlapping people, random people walking in and out of line, etc. Cool seeing all the techniques and approaches you tried!

Wow, this was a lot of fun.

3 was a lot harder than expected — a great exercise for anyone honestly. I'm a math nerd so this was cool visualized!

Oh amazing, no idea how I missed that green button LOL. Was too excited about the details.

This is really neat. Have always wondered how these work under the hood / the algorithm behind them.

Would love a web version that's easily usable though; as much as I live in the terminal, just too much of a mental burden installing a new package.

I agree with the overall sentiment of the article, but find it a bit harsh.

I honestly find the real debate to be inline styles vs stylesheets.

Tailwind is just fancy inline styles. Personally, every single time I've used stylesheets in a large production-grade project it's an absolute mess. Every project I start now I use inline styles. I'm pretty indifferent on Tailwind though, it's sometimes nice to get opinionated defaults.