11–20 of 41 posts
I don't understand, what exactly are you sunsetting? N1? Or the service that synced mailboxes?
The mail cient was originally called N1 (later Nylas Mail), and is the product being sunsetted so they can focus on the API.
As a user, I've been loving Nylas Mail/N1. I hope the project lives on in some usable form - the blog post mentioned Nylas Mail Lives and Mailspring, which I'll have to take a close look at. (I came to Nylas after Dropbox finally killed off Mailbox. I seem to have a good track record of falling in love with desktop email clients which then die...)
Hey thanks! I used to work on Nylas Mail at Nylas and I'm the author of the Mailspring fork. It's definitely sad to see this post, but Nylas has remained committed to open source and I think they've done this right. Relicensing everything under MIT ensures the product will have a bright future, even though Nylas has better opportunities it needs to pursue for it's employees and investors. Would love for you to check…
> Relicensing everything under MIT ensures the product will have a bright future
Absolutely. Very impressive move.
I don't understand, what exactly are you sunsetting? N1? Or the service that synced mailboxes?
My understanding is Nylas has two products: An email API you could use to build applications on, and a mail client they built on top of that API. The mail cient was originally called N1 (later Nylas Mail), and is the product being sunsetted so they can focus on the API.
Interesting. I used N1 for a while a really enjoyed it, but the Electron apps were killing my laptop so I ditched it. Super interested in the Mailspring fork :)
[0]: https://github.com/MailCore/mailcore2
[1]: https://github.com/Foundry376/Mailspring#high-level-goals
Earlier quoted context omitted.
My understanding is Nylas has two products: An email API you could use to build applications on, and a mail client they built on top of that API. The mail cient was originally called N1 (later Nylas Mail), and is the product being sunsetted so they can focus on the API.
This is correct. The APIs have extended to include calendar and contacts in addition to the original email API, and that's where we've chosen to focus going forward.
Their API sync-engine [0] either hasn't been updated since March, or hasn't been kept open source--neither of which is a great sign. We're currently using the open source Nylas sync engine in production as we were uncomfortable trusting an important feature of our product in a company that doesn't seem to have a firm idea of what they want to do. But with the seemingly abandoned open source project, we are now working on building out our own syncing applications to ditch it altogether.
I would strongly caution anyone considering using the sync APIs to think about what they are getting into and the switching costs.
Glad the Nylas team is focusing. I really wanted to like the frontend client, but I stopped using it about a year ago due to reliability issues. Mining organization data from email seems like a great opportunity. Context.io wasn't able to make it work, but Nylas looks a lot more capable.
(disclaimer: I'm the business guy at Nylas) Unlike Context.io, the Nylas APIs don't mine email organization data at all! We're not owned by a marketing parent company, and all our customer MSAs make it very clear that we have no rights to any of the email data passing through us. Nylas is an infrastructure company, like Stripe or AWS, and we make money by building tools and making our customer's lives and products be…
We originally piloted using Nylas's APIs in our product about a year and a half ago. In that timespan, their pricing has changed significantly about 4 times and they do not seem like they have a particularly good grasp on their business model. They also, despite advertising 10 free test accounts, arbitrarily delete said accounts and then when you ask to get them reactivated you get connected with a sales rep. Their A…
1. Company invests heavily in engineering and builds a sync engine. Progress is visible on GitHub and rapid.
2. Company launches and repeatedly adjusts pricing and business models. Drives everybody crazy BUT:
3. Company finds it's value prop and customer base and the changes stop. Entire company shifts to building a sales team and keeping the wheels on the bus while they make their first customers happy.
4. Engineers switch from working on the core sync codebase to surrounding services, infrastructure, and scale.*
* Last week's developer dashboard announcement: https://www.nylas.com/blog/announcing-the-nylas-dashboard-2....
And somewhere along the road: Company realizes customers that are willing to go through the hassle of provisioning, deploying, and maintaining their own version of the open source sync engine are not the customers to focus on. ;-)