Show HN: An open-source, local-first Webflow for your own app
11–20 of 53 posts
Re: Show HN: An open-source, local-first Webflow for your own app
#12I love the idea. I'm working on something in the same general category, but a very different approach and I love seeing how others are tackling this problem. Over time I suspect we'll see more tools that attempt to bridge design tools with dev tools - every time I crack open Chrome's inspector, all I can think about is how amazing it could be if it was intended to be used by design teams.
Chrome inspector does so much more like clip support and media queries that I didn't even know about. It also writes directly to inline styles so propagating those changes as code is definitely possible. I was thinking if there's a way we can leverage the great work the Chrome devtool have already put in.
Re: Show HN: An open-source, local-first Webflow for your own app
#13exciting stuff
Re: Show HN: An open-source, local-first Webflow for your own app
#14Re: Show HN: An open-source, local-first Webflow for your own app
#15Re: Show HN: An open-source, local-first Webflow for your own app
#16so cool - always feel a little pain when i have to suggest webflow nowadays. Glad to see other options cropping up - love the vision :)
Re: Show HN: An open-source, local-first Webflow for your own app
#17Re: Show HN: An open-source, local-first Webflow for your own app
#18Exciting update, Kiet and Daniel! Even as a non-technical person, I can see how Onlook could really bridge the gap between design and development. The ability to visually edit a React app and see those changes in the code in real-time is a game-changer. I’m looking forward to seeing how you bring those A/B testing and component creation features to life. Keep up the great work!
Re: Show HN: An open-source, local-first Webflow for your own app
#19Happy to contribute to this amazing product...
Re: Show HN: An open-source, local-first Webflow for your own app
#20 {"component":"Dashboard","endTag":{"end":{"column":10,"line":620},"start":{"column":5,"line":620}},"path":"/Users/kietho/workplace/onlook/studio/demos/next/components/dashboard.tsx","startTag":{"end":{"column":67,"line":69},"start":{"column":5,"line":69}}}
Up to you, but you'll save a ton of space in that b64, and arguably some user privacy, by trying to use workspace relative paths. I also thought JS had access to gzip (or zlib) which would similarly help, doubly so if the gzip dictionary were externalized (e.g. ) since it seems the object keys repeat a lot