In this post I outline the pipeline I built for automating UI design. It's an ongoing project but it's already replacing for me a lot of the drudgery of design exploration, which current tools noticeably don't do well.
In this post I outline the pipeline I built for automating UI design. It's an ongoing project but it's already replacing for me a lot of the drudgery of design exploration, which current tools noticeably don't do well.
Orthogonal is simple RAG with file and conversation coverage. I notice that a single context is too messy to keep track of what I'm working on, so I added projects so you can switch context for your files and chats. Inspired by Claude Projects.
This is a good point. In general, you get redundancy by splitting samples over multiple locations and storing cells at -196 liquid nitrogen or slightly warmer vapor phase.
I also think sequencing is another form of insurance that applies to cell storage for aging, because sequencing as much of your cells as possible now is basically a digital save state of your youngest cells. A rubric for age-reversal, at least for your cells.
I made this as a quick, focused way to generate responsive code for my projects. It focuses on generating responsive element layout, which tends to be the most annoying part of creating UI. With GPT4 being released I'll be able to generate more sophisticated code soon. Posting here to see if it's useful for anyone else.
The react export option exports inline jsx for now. You should be able to directly paste that into a react file, as opposed to the html export. I purposely don't wrap the jsx in a named component since I can see all kinds of use cases where a person wants to inject jsx into a part of an existing component.
At the time of posting, the extension actually allows you to export either jsx (which you can directly place in a react file) or html. That detail just isn't shown in the video, which shows an earlier version of the feature. Will update video.
Thanks! Since Aspect aims to solve the design-to-engineering handoff problem, I think we monetize on a per-seat basis for enterprise customers. Similar to Figma's pricing model actually.
I made this because it felt like a missing feature in Figma. Engineers shouldn't spend time rounding corners and changing button colors when designers have already done it. Hope it's useful!
Yeah I can learn a lot from React Studio—I think a lot about keeping the learning curve down for growth, so I'm glad you pointed that out. I'm focusing on enterprise sales next and actively looking for people to help with that, so again I think you're right. Thanks for the feedback!
Been thinking about this a lot the past few days. The main reason this isn’t yet integrated into vscode is to allow designers to edit, like in webflow.
Right now we export class components, but the option to export functional components is coming soon. Will likely default to functional component export.
I set up super minimal preset styling, and yeah I think basic css import makes sense as a next feature. Hoping to avoid overly complex style inheritance.
I 100% agree, getting layout css right is the most annoying part of styling. I’m inspired by Apple’s stack views and Figma’s auto layout which make it a lot more intuitive so I think those can be the first “Aspect components” that will come out on next release.