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 demo gives me an idea. But let us take the example of header and navbar. What happens in responsive case. will it give me the hamburger icons or a placeholder for that along with the menu for mobile screens? If we are able to generate generic place holder text along with alignment and font sizes built in will be great.
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.
Some logic to rename variables and perhaps wrap on-screen text with an instruction to rephrase, coupled with watermarking images so they have to be replaced, might effectively render copyright objections void/unenforceable ... it's not like you can copyright the general techniques.
This would make it a far more viable commercial tool.
If this could be combined with tooling to facilitate the use of generated code to more easily produce React Native compliant versions, giving you a quicker path to iOS and Android equivalents, you would be halfway to auto-generating what 90% of non-technical people want when they say "just build me something like X site/app".
In literature no, but in code, where once you take those parts out what's left is often industry standards on function structure, used so often that you would struggle to identify which example your copy is based on (a good defense in itself) ... there you should be ok.
It's really just a specialized Copilot at that point.
