Onlook sounds interesting as someone who had lined up using https://webflow.com/devlink as a solution for allowing our web dev to continue doing static content development in our new web app. If I were to ask: why use Onlook over Devlink what would your answer be?
I think DevLink is great and it's a step in the right direction. However, you're still locking into a WebFlow project. You can export a DevLink component out and then migrate it back in. You also have to instrument the weblink component. With Onlook, there's no new environment. Your code is just running in localhost in your project. No import export and no extra code just to develop a new component.
Show HN: An open-source, local-first Webflow for your own app
51–53 of 53 posts
Re: Show HN: An open-source, local-first Webflow for your own app
#52very cool!
Re: Show HN: An open-source, local-first Webflow for your own app
#53I'm a product designer turned web dev, and I work extensively with Nextjs, Tailwind, and Shadcn/ui.
I love the idea of being able to visually edit my webapp and port them back to code seamlessly. I was hoping you could help me understand the following
- How does Onlook compare with Webflow's devlink and Webstudio? Honestly Devlink seems dead to me, Webstudio seems promising but doesn't look like they prioritize react nor tailwind
- Can I use onlook in a Nextjs project with Tailwind? Will the visual edit reflects in Tailwind classes' updates?
- Will there be issues with "use client" or "use server" components as I read there were with Devlink?
- I'm building out of a turbo monorepo, how will this work? Do I just cd apps/my-nextjs-app and run npx onlook?
- How does this work with Shadcn/ui? If I update a component in the visual editor, I'm assuming it will change the tailwind className from app/components/ui?