It looks really great! Which frameworks/libraries and languages did you use? What were the main challenges you came across?
I've spent the last two years building a new email client
111–120 of 608 posts
Re: I've spent the last two years building a new email client
#112Re: I've spent the last two years building a new email client
#113Re: I've spent the last two years building a new email client
#114Earlier quoted context omitted.
This is an "all my friends voted for..." argument. Electron applications such as Slack, Discord, and VS Code have ballooned in popularity over the last year or two. Hacker News comments are not representative of the whole.
It is not about popularity, it is about the resources Electron apps use vs native. The apps that you mentioned do not have good native alternatives. I cannot see anyone preferring a native app over Electron app if both offer the same features.
Re: I've spent the last two years building a new email client
#115Earlier quoted context omitted.
1. It's an Electron app, but it is built to use as little RAM as possible, when I run it on my old Macbook Air, it consumes only around 300mb of RAM maximum, which is less than what Finder consumes, and I consider everything over this limit to be a bug. 2. Currently not supporting Mbox/Maildir but downloading emails directly from the server, however an import of this is on the todo list 3. Re: turn off conversation v…
I think SyneRyder means what format are you storing emails on disk? If a user uses your email client to download all their pop3 email, is it available in a nice format on disk for whatever reason (backups/file recovery/migration to another client)? Or is it locked up in a custom file format.
Re: I've spent the last two years building a new email client
#116Well, I am curious. Seems so hard to get an email client right. I would not mind paying (GPG integration is a must). If you don't go the mutt/alpine route, there aren't much options. Basically Thunderbird and Evolution. Never really got Clawsemail and iscribe to work with my IMAP server settings. To make things worse, people do understand email less and less. Often, all ports except 80 and 443 are blocked and you can…
During development of this client, I fully understand why there aren't more email clients out there. GPG is coming!
Re: I've spent the last two years building a new email client
#117What is the reason to build it as a native software instead of a webapp? Seems like a lot of email clients are now webapps and I can see the arguments why.
What would be the reason to cram the mail client into the browser instead of making it a first-class application on the same level?
Re: I've spent the last two years building a new email client
#118Earlier quoted context omitted.
> Btw where are the electron haters?! Hi! I'm here! ;) I mentioned Electron in my comment, and Electron is a deal-breaker for me... but I would much rather encourage the work and effort that is going into this. If the product is successful and profitable, maybe it can be ported to native frameworks a few versions later. And considering the rumours about macOS, probably wise to avoid writing native Mac code just now.
> And considering the rumours about macOS, probably wise to avoid writing native Mac code just now. What rumors?
Re: I've spent the last two years building a new email client
#119Earlier quoted context omitted.
300MB of ram sounds like a lot to me. What are you storing in memory that is that large? If I dont use the app for 1 hour will it stop using the memory?
That's just the base cost of using electron (along with the associated CPU usage). It's terrifying but you get that much usage even if you're not storing anything in memory.