The only downside from my point of view is the large installer size for Electron apps, but it hasn't been a big issue for our users (because they will need to download quite a bit of other stuff like npm packages to actually build apps with dyad)
Your message wasn't delivered to support@relace.ai because the address couldn't be found, or is unable to receive mail.
btw, I'm interested in trying out relace for my AI app generator tool: http://dyad.sh/
But it does local models via ollama, supports multiple chats, and can get an app stood up just the same as Bolt, v0, Lovable, et al.
Stoked this is being built, looking forward to seeing what it becomes!
Regarding the localness, are you optimizing or targeting users that prefer only local inference? The part about API keys at the end makes me wonder if there's any practical difference outside of lower local resource requirements and access to private models on the clound.
Do you recommend or force that people use any specific languages or frameworks that dyad is optimized to render or iterate on locally?
I definitely want to support users who want to use cloud inference or local inference because you do need a pretty beefy machine to run the top open source models.
Right now Dyad supports React (vite), but i'm working on supporting more frameworks in the future! (other languages is probably further off)
I think practically, the nice part with Dyad is that all the code is on your computer, so if you want to switch back and forth with Cursor/VS Code, it's seamless.
Using Cursor, I felt like it was too easy to modify too many things in one go.
I keep my prompts scoped to drafting / refining specific components. If I feel stuck, I’ll use the chat as a rubber duck to bounce ideas off of and rebuild momentum. Asking the model to follow a specific pattern you’ve already established helps with consistency.
Recently been impressed with Gemini 2.5, it’s able to provide more substantive responses when I ask for criticism whereas the other models will act more like sycophants.
Basically it's running a chat UI locally on a Git repo and you can reference files like "#foo.py" and then if you want to edit a file, you hit "Apply code" for a markdown code block and then it shows you a code diff so you can review the changes before actually updating the files. I've found this makes it much easier to curb stray edits and keep the LLM edits focused on what you actually care about.
You can also check out the GitHub repo at: https://github.com/dyad-sh/dyad
(disclosure: I created Dyad)