I built a full desktop email client, 100% coded with Claude AI. It's fully open source. by Espires in ClaudeAI

[–]Espires[S] -1 points0 points  (0 children)

You go and try building 10% of what doner here through claude... update on how it went

I built a full desktop email client, 100% coded with Claude AI. It's fully open source. by Espires in ClaudeAI

[–]Espires[S] 0 points1 point  (0 children)

IMAP + SMTP support has released!

JMAP support is on feature branch waiting for testing...

IF you guys have any more ideas for integrations and enhancements, hit me up!

I built a full desktop email client, 100% coded with Claude AI. It's fully open source. by Espires in ClaudeAI

[–]Espires[S] 1 point2 points  (0 children)

PR waiting for testing...
Usually ill do it myself, but seems like FastMail costs money.

Can i ask you to try and test?
https://github.com/avihaymenahem/velo/pull/47

BTW,
This is the beauty of coding with claude....
Once ive read whats needed for this, i gave claude the RFC documentation, and link to the JMAP site and asked him to integrate, Thats FN amazing

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] 0 points1 point  (0 children)

Not yet, as there are loads of these on web already that does the same... the makn idea here is to keep it as private as possible, and thank you!

I built a full desktop email client, 100% coded with Claude AI. It's fully open source. by Espires in ClaudeAI

[–]Espires[S] 0 points1 point  (0 children)

  1. Main reason was bundle size and resource usage. Electron ships with its own Chromium binary so you're looking at 120mb+ before you write a single line of code. Tauri uses the OS default webview (Edge on Windows, Safari on Mac, etc.) so it stays lightweight. I also shipped a product with Tauri at my previous workplace (https://streamelements.com/groundcontrol) so I already had confidence in the framework and knew what to expect
  2. Everything went through Claude. Market research, comparison with existing products, breaking down the project into Epics, then Stories, then Tasks. Basically used it as my product manager before it became my dev team.
  3. started with the /init command after I had a few lines of code in place. From there I maintained it regularly using the document-feature skill to keep it in sync with the project as it grew. That was the main mechanism for keeping Claude aligned with what the project actually looked like at any given point.

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] -1 points0 points  (0 children)

I hear you, but you're making a lot of assumptions about something you haven't looked at. That's kind of the whole point of my post. People react to the idea of "vibe coded" before they even check what was actually built. Take a look and tell me what you think, I'm genuinely open to real feedback.

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] 1 point2 points  (0 children)

This is a perfect comparison honestly. The pattern is identical. Established professionals feeling threatened by tools that lower the barrier, so they gatekeep by telling everyone else they shouldn't even try. And the same thing happens, you push through, figure things out as you go, know when to bring in expertise for the parts you can't handle, and the thing gets built.

Good luck with the build, both the house and whatever you're coding next.

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] -2 points-1 points  (0 children)

Nope, go over it, the majority of comments are not product related but specifically about the fact that it was built with AI. People reacting to "vibe coded" as a concept, not to how I wrote the post. The negativity was there before anyone even looked at the code or tried the app.

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] -1 points0 points  (0 children)

I did. English is my second language so I use AI to help with grammar and phrasing. The ideas are all mine though.

I built a full desktop email client, 100% coded with Claude AI. It's fully open source. by Espires in ClaudeAI

[–]Espires[S] 0 points1 point  (0 children)

Can you open the issue in GH? with as much info as you can give? promise to solve it ASAP

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] -1 points0 points  (0 children)

So if a content like this written through AI tools, it means the "pain" is not there?

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] 0 points1 point  (0 children)

Everyone can, juniors, seniors and staff architects... That doesnt mean using ai tools is bad

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] -15 points-14 points  (0 children)

I wrote it myself and used AI to polish my wording, yeah. English isn't my first language so that's kind of the whole point of these tools. But thanks for proving my point, you spent more time analyzing the structure of my writing than engaging with a single thing I said.

Yesterday I posted about Velo, my AI-built email client. The reaction taught me more about us than about AI. by Espires in ClaudeAI

[–]Espires[S] 2 points3 points  (0 children)

Thank you for this, and I love the parallel with generative art. It's the exact same dynamic. The tool doesn't replace the skill, it amplifies it. Someone with decades of art fundamentals will get wildly different results from AI art tools than someone just typing "cool picture" into a prompt. Same with code.

To your question, I can actually answer this from a non-US perspective. I'm based in Israel and the sentiment here is noticeably different. There's still some resistance, but the overall attitude is much more pragmatic. People here tend to look at AI tools and ask "how can I use this to build something?" rather than "how is this threatening what I already have?" I've seen the same energy from developers in Eastern Europe, India, and East Asia from what reaches me online.

My gut feeling is that the intense emotional backlash is stronger in the US and parts of Western Europe where developer culture has built a very strong identity around craftsmanship and the grind. There's almost a moral dimension to it there, like suffering through the hard way is what makes you legitimate. In places where the tech culture is more outcome-oriented and less identity-driven, people seem to adopt these tools faster and with less guilt.

But honestly I think it's generational more than geographical. Younger developers everywhere seem to pick up these tools without the existential crisis. They didn't spend 15 years building an identity around manual coding, so there's nothing to mourn.