Live data from Hacker News

Our experience launching a paid, proprietary product on Linux

blog.hiri.com

151–160 of 395 posts

Re: Our experience launching a paid, proprietary product on Linux

#151
Step 1: excited. An email client I've never heard of?

Step 2: interested: read article, read webpage

Step 3: meh. They call it email client, but it's only for Exchange/Office365

Some additional notes on the website: it's nice that there's a 50% discount, it usually helps to show the before/after prices ;)

Re: Our experience launching a paid, proprietary product on Linux

#152
post #97

I am trying to make a living with a software product, a database in particular. RediSQL, SQL steroids for Redis: http://redbeardlab.tech/rediSQL/ So let me share a different point of view. I find it extremely, extremely difficult. As far as I know, if you need a solution for in memory SQL as cache layer or also as main persistent layer it is the only available solution, on top of that it works on top of existing, wid…

A small amount of hopefully useful feedback from someone who purchases business software:

1/ Your website gives a 'open source hobby app' vibe over 'professional, dependable software business'. Selling support contracts in particular requires some expectation that there's a solid business standing behind it that won't just be gone tomorrow.

2/ The 'redirect to an external store to download / purchase' will probably be making any sales funnel leak like a sieve. There's a complete discontinuity between the design of the two sites, and along with trusting you with their information / card details, they now have to trust a random third party.

3/ For a ~€1000 piece of software, I'd expect at least some period of eg. email support, rather than just supporting through Github issues.

4/ I'd remove the option of having the open source edition available through sign-up and just link clearly to the latest release. If you're struggling to even get any interest on the commercial side, getting it out in front of as many people as possible would be my priority. A clear and unambiguous 'Get started' section that doesn't worry about open vs. Pro is probably a good idea too. Worry about converting those to paid users later.

Re: Our experience launching a paid, proprietary product on Linux

#153
post #18

Earlier quoted context omitted.

> I don't think I've ever seen someone claim to use Linux because it's free (no cost). It's almost always because it's an open platform or because it has the best tools for the job they're doing (e.g. development work). Then those people are lying. Free is absolutely a factor for many.

I'd wager that over 90% of desktop Linux users are running it on a machine that came with a Windows license and Windows preinstalled, and went to the effort of wiping it despite the fact that they paid for it and legally own it.

The cost of Windows is assumed to be part of buying the laptop (and it's the OEM version anyway).

I never myself cared for the sub-$100 Windows license attached, given that I bought a $1500+ laptop. Since there were always few (and usually subpar) selection of Linux-first machines (especially here), having a Windows license was just the normal across all laptop brands -- so it was not a deciding factor in comparing prices. It was either paying that, or being constrained to pick from 1/50 the machine selection.

This doesn't extend to buying software in general.

Re: Our experience launching a paid, proprietary product on Linux

#154

"First stop, reddit" Dont go to reddit for market research. You will only find extreem views on reddit. They are the younger crowd. Try the ubuntu or mint forums if you want to talk to average linux users. I myself would pay for such an email client because no good foss one exists atm. But i find it very odd that such basic software isnt yet free. I dont like the idea of having my email handled by propietary software…

> I dont like the idea of having my email handled by propietary software. Fair point, although I'll point out that you're commenting on a story about a client specifically designed for Microsoft Exchange.

I'm a bit extreme when it comes to my email. Work insists on outlook so I use it there, but for private email I forgo dedicated software. I use webmail on my phone (husmail.com). It is slower, but when the airport security guy asks me to "unlock my phone" I can do so without revealing my email conversations. I don't trust my Andriod phone in the same way I do my ubuntu/mint/kali linux machines.

Re: Our experience launching a paid, proprietary product on Linux

#155
post #93

Earlier quoted context omitted.

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 pu…

Keep in mind that Google IMAP could mean Google Apps compatibility. And a good number of orgs use Google Apps.

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 Linux

#156
post #6

I am increasingly happy to pay for software and services as long as the organization producing the software has no relationship with advertisers. I would rather pay money than use something for free that includes advertising. If there are good open-source alternatives I will always prefer those, but there are definitely some things that open-source will never be able to really make work effectively (notably anything…

What happens when the product becomes unsupported, or the company goes under? I'd like to see more software sold with a code escrow clause -- if development stops or the company no longer offers support, the source is released by a third party. Maybe even under an open license.

Re: Our experience launching a paid, proprietary product on Linux

#157
post #33

Earlier quoted context omitted.

How many people are actually free to use this product? My work uses outlook+office but, due to 101 different things, we are locked into windows and ie. How many people use outlook+office for email but are also free enough from other restrictions to be allowed linux? Our office is so locked imto win7 that the ongoing upgrade to win10 is killing things. People are migrating to the few win7 machines to complete essentia…

A lot of people can use Hiri because runs on Windows and Mac too.

Then again, so does Outlook.

Re: Our experience launching a paid, proprietary product on Linux

#158
post #112

Earlier quoted context omitted.

Having the blog post outside Medium doesn't guarantee them all looking better. On the other side, it is easier to fix one site using custom CSS than it is to fix a bunch. An on the other other side Firefox's reading mode makes this whole discussion irrelevant.

> An on the other other side Firefox's reading mode makes this whole discussion irrelevant. It really doesn't. It doesn't fix it for non-firefox and non-power users.

Chrome is the only mainstream browser without a decent reading mode these days — because doesn’t want people hiding advertisements. One of the reasons I prefer not to use it.

And enabling reader mode doesn’t need any power user skills, does it?

Re: Our experience launching a paid, proprietary product on Linux

#159
post #5

Completely unrelated to the contents: Please, publishers, I beg you: walk away from medium. It's terrible for us, your readers. Set up a static blog, with a domain, go WordPress, Grav, Typo3, anything, but without stupidly large sticky header/footer and without heavy javascript . EDIT: apparently 121KB javascript is not heavy. I still believe it's an overkill for 30KB content.

I barely see the problem. Sure, the header and footer aren't perfect, but stupidly large? I also don't feel any "cpu melting javascripts" and my PC is barely usable when I compile anything. For me, Medium provides a very readable experience that is much better than the average static blog. And I don't have to fear a malware ridden page like an old Wordpress installation.

its a problem whenever I visit my rural family.

Re: Our experience launching a paid, proprietary product on Linux

#160
I believe having more proprietary software available on all platforms (including Mac) improves the situation - especially something "basic" like a mail client.

Yes, FOSS and Linux are "a more natural" match than proprietary and Linux, but the truth is: You can't get everything you might want/need for free at an acceptable quality .

Working for a company which sells niche-software for both Windows (most customers) and Linux (some big $$$ customers), I am happy to see more mainstream developers doing the same. If you're a making consumer software: Please try to follow suit!

Internally, we develop on and for Linux, but our code is cross platform enough (thanks Qt) to easily build on Linux and Windows. The biggest issue for me is remembering which C++ constructs work with GCC/clang but not with the MS compiler (which improved a lot in the last years - and which our CI usually notifies me about).

Post reply on HN