News for hackers. Stuff that matters.
Re:Our experience launching a paid, proprietary product on L... by brightball on Monday July 23, 2018 @10:30AM (#17593008)
Yep, totally agree with you there.

After reading the article that was my first thought when he mentioned adding support for Google IMAP.

Full stop. Don't do it. You have a product that is doing well as the solution for something with a clear business case that's not well addressed elsewhere. Own that market and focus your development attention on that Exchange ecosystem.

As soon as you branch to IMAP/Gmail/General purpose you're going to be in the sea of tons of other email clients, most of which are free. It's going to dilute the value proposition for Hiri because Hiri is going to become "another email client" that also supports exchange. The taste for email clients that add exchange support is not generally a good experience. It also means that you have to ensure all of your UI elements work equally with both, bringing you to more of a lowest-common-denominator experience.

When I see Linux Exchange Email Client and that's all you do, I see specialty software that I can rely on to solve that problem correctly. When I worked at a company that used Exchange, I would have bought it IMMEDIATELY and convinced my boss to reimburse me later.

As soon as you become a general purpose email client, everything about what you offer to solve that problem starts getting lost in the shuffle.

Re:Our experience launching a paid, proprietary product on L... by bovermyer on Monday July 23, 2018 @10:42AM (#17593087)
This would sound like wisdom, except that all of the other email clients for Linux are garbage.

I bought Mailbird because it looked amazing and had the feature set I wanted. It has done its job extremely well, and I'm very happy with it. But it doesn't have a Linux client; it's only for Windows.

I have six active email addresses spread across multiple providers - Office365, Exchange, Gmail, GSuite, and Zoho. I need a central place to read it all.

I've seen Hiri mentioned before, but dismissed it because it doesn't support Google/IMAP. Once it adds that support, it has my attention, and potentially my dollars.

Re:Our experience launching a paid, proprietary product on L... by kevkav on Monday July 23, 2018 @10:46AM (#17593103)
That is exactly the reason for Gmail support.

It's not moving focus away from Linux/Office365 but it accommodates people that want to have their Gmail accounts in the same client as their Office 365 / Exchange accounts.

Re:Our experience launching a paid, proprietary product on L... by caymanjim on Monday July 23, 2018 @11:40AM (#17593473)
I'm a consultant. My clients often use Outlook/Exchange. My consulting company uses Google Apps. I also tend to create a per-client GMail persona, so that I can work around issues with corporate Exchange servers (aggressive content filtering, misguided attachment quarantines, or just to keep work-related-but-social stuff out of the corporate inbox), and have a convenient OAuth login option. I would welcome anything that allows me to use a single client.

Another reason for wanting a client that works with Exchange and Google is simply wanting to use the same app both at work and at home, even if you never cross the streams and access them both from the same instance.

And as others have mentioned, Linux email clients suck. I'm a huge proponent of open-source software, and prefer free clients wherever possible. No one has made a free email client that I can tolerate. They're so bad that I tend to stick to web clients. Hiri's client reminds me of Polymail on MacOS, which is the only non-game, non-cloud application I've paid for in the past decade.

Re:Our experience launching a paid, proprietary product on L... by bunderbunder on Monday July 23, 2018 @11:22AM (#17593340)
The prime use case there would seem to be intermingling your work and personal email.

That doesn't seem like a great idea, on many levels.

Re:Our experience launching a paid, proprietary product on L... by kevkav on Monday July 23, 2018 @11:36AM (#17593442)
Yup, from a personal perspective I agree. I don't like to cross the streams either but a lot of people do.
Re:Our experience launching a paid, proprietary product on L... by jtchang on Monday July 23, 2018 @10:33AM (#17593022)
Keep in mind that Google IMAP could mean Google Apps compatibility. And a good number of orgs use Google Apps.
Re:Our experience launching a paid, proprietary product on L... by brightball on Monday July 23, 2018 @10:36AM (#17593041)
Oh I know, there's just so many existing IMAP clients that I can't imagine paying for a desktop email/calendar client to work with Google Apps. Not to mention all the web based bits like Google Inbox, etc.

The value proposition just isn't there with all of the free options already out there.

Re:Our experience launching a paid, proprietary product on L... by drb91 on Tuesday July 24, 2018 @11:14AM (#17601735)
....not on linux there aren’t.
Re:Our experience launching a paid, proprietary product on L... by __sr__ on Monday July 23, 2018 @11:51AM (#17593566)
Doesn’t Google Apps support MS Exchange on the server? The paid one, that is? I remember there was a lot of hue and cry over Google dropping MS Exchange option for free Gmail around the same time when Windows Phone 8 launched. But at the same time, Google said they would continue to offer Exchange for paid accounts. Has that changed?
Re:Our experience launching a paid, proprietary product on L... by compuguy on Monday July 23, 2018 @03:00PM (#17594970)
It supports ActiveSync, to my knowledge.
Re:Our experience launching a paid, proprietary product on L... by Fnoord on Monday July 23, 2018 @03:32PM (#17595265)
Isn't that also a matter of how you word / market it? If its marketed as an Exchange client also able to do IMAP/Gmail that's something different than an email client with IMAP/Gmail support oh and it has an Exchange plugin.

There's only a handful of Exchange clients for *NIX though, that I agree with.

Re:Our experience launching a paid, proprietary product on L... by pkphilip on Monday July 23, 2018 @12:20PM (#17593733)
An email client without IMAP support is not going to get much traction. No one wants to have multiple email clients open at the same time.
Re:Our experience launching a paid, proprietary product on L... by hk__2 on Monday July 23, 2018 @03:02PM (#17594993)
> An email client without IMAP support is not going to get much traction. No one wants to have multiple email clients open at the same time.

I don’t understand the link between your second sentence and the first one. How not having IMAP support forces you to have multiple email clients open at the same time?

Re:Our experience launching a paid, proprietary product on L... by sabas_ge on Tuesday July 24, 2018 @01:51AM (#17598434)
At work I switched from Outlook 2013 to Thunderbird, we only have linux mail servers although we run Windows on clients, but I needed to access an Exchange email. I solved it by installing Davmail locally, which translates exchange commands in IMAP commands. Otherwise I would have been forced to use Outlook only for that exchange mailbox.