That's more or less what FogCreek did with Trello and CoPilot. While FogBugz was "good enough" to more or less run on rails, they made other bets to expand or productize some of their internal toolkit. It worked so well that these side-bets eventually got much bigger than FogBugz.
I wish more people tried that, instead of messing with their cash-cows. Yes, sometimes you have to keep up with competition or "innovate" in your own space, but if you got big already, chances are that you've done your best work already - leave it as it is and move on.
[0] https://www.cgg.com/industry-applications/energy-transition/...
For example Shell Ventures [0] funds companies like d.light (solar home energy) and Husk (off grid renewable energy)
[0] https://www.shell.com/energy-and-innovation/new-energies/she...
So now you're Exxon, and you see that Shell has significant investments into oil AND Green energy (specifically Wind right now for Shell). How do you plan to beat Shell at their dual-strategy game?
Exxon double-down on oil. You can't just do the same strategy as someone else and expect to get ahead. You gotta place your bets on a different strategy.
No, you don't. Betting all on black is just a different gamble, and in my opinion a more risky one. But investors are ok with it because many prefer pure play gambles.
There's no law of nature saying that you have to zig when others zag. A big opportunity like clean energy has room for many winners.
Not to mention the reputation of the organization might make it difficult to attract and retain the types of innovators and professionals it needs to succeed.
Whereas with FogBugz, they were investing in complementary products, not destroying their own market.
Only problem is we don't have any good UI toolkits anymore, all are second rate compared to the browser. Qt might be the best, but their licensing scares solo devs.
With that, if the only thing that's going to happen is my ideas get taken and used in an open-source project, why not just keep my tools to myself and continue to work for a big corporation?
I live in a small town in Minnesota so I don’t need to make much money to be comfortable, raising a family. I’m in my late 30s and have done mostly iOS and Node IIOT consulting the last 10 years. That’s what was paying the bills until my electron app started making “real” money.
On the technical side. I get emails every day saying how much a user loves my app. It’s really rewarding. Every year I get one angry email or App Store review saying that there are much better design/desktop-publishing apps out there. These reviews are usually written by technically savvy people that don’t quite get how stupid-complicated label printing can get. Like, don’t expect to design your company logo in my app. But surely, you can drag in your company logo and my app will dither your image for a 200 DPI zebra printer.
My app is basically a no-code image processing pipeline that effortlessly hooks up spreadsheet data, generates barcodes, resizes and fences text, dithers images, dynamically changes colors, and then talks directly to a thermal printer without using a driver.
And you can use it for free for 14 days to see if it works. It’s a single download. Yeah, it’s electron, yeah it uses some memory. But you can share the design files between Mac and windows and it doesn’t require internet for use.
I don’t know. I think it’s a pretty good solution.
Read more at https://label.live
Btw, what do you mean "without a driver". Do you bundle code that talks to thermal printers in you app? Is there a standardized communication protocol in this space or do you maintain a breadth of custom implementations?
Oh, don't worry about that. Trading money for things is an ages-old thing and will remain for centuries no matter what. Just make something useful and put the right price on it. People will buy it if it solves their problem. If someone won't use it because it's not free - they don't really have the need that your product solves. Just ignore them.
Anyway if a few devs can quickly slap together a functional open-source clone of your apps you might want to ask yourself if your app really provides enough worth to your users to pay for it.
My target audience is businesses, not HN users so I haven't ran into these open source zealots.
Some businesses do ask for open source (politely declined)
Some have also asked to place the source code into escrow for continuity in case the business folds (also politely declined but for some companies this a reasonable ask)
The thing is that people will ask for literally anything and the requests are asinine:
* Rewrite in java\python\ruby\c++\whatever language the IT guy read about last week (nah)
* We need a mac version for the one guy who somehow uses a mac (nope)
* Support oracle (fuck no)
* Support novel networking (lol)
* Make a webapp (lmao)
I'm also not afraid the "hacker" who is going to re-write my app. If theirs is truly better, I will just fork it and crush them :)
Don't let the bobble heads dissuade you. If you want to make a desktop app and if you think the desktop is the correct medium, do it.
Loved VB6. I have a friend who is still writing and maintaining software he wrote in VB6 for an industrial plant to this day.
Anyway, you'd be surprised. Once you venture outside the HN echo chamber there are large numbers of people who really prefer that their data stay on their own PC. Also, many are concerned about the same problem that this topic is about: having interfaces change without warning is a huge problem for most people.
Convincing them is largely about providing an upgrade path if they need it and not having forced upgrades.
AFAICT, that's backward: people with that preference are over-, not under-, represented on HN.
[0] anyone who just uses a web browser arguably doesn't even count as a 'desktop computer user'.
My understanding right now is that if you have a software that people need to install and your competitors have an in browser offering, your customers overwhelmingly choose the in browser offering.
This has been my experience even though I hate the subscription model as much as everybody else in this thread
Speaking for myself, I have replaced Adobe CC with Affinity Publisher, Designer and Photo. A one-time fee for software I can use forever, as opposed to paying forever regardless of whether I use it or not.
I also have Dreamweaver and Flash-type animation tools (Bootstrap Studio and Tumult Hype) that are also one-time fee apps.
Yes, this.
Investing all your energy into features none of your users want for an existing app is a waste of energy for you and an annoyance for the users.
And maintaining the backend of a SaaS can mean more operations busywork for you, compared to a standalone application.
Build something new people actually want.
I feel like general computer skills have decayed quite a bit in the general public, especially with people who don't work with computers 8 hours/day. See this recent article: https://www.theverge.com/22684730/students-file-folder-direc... The advent of the smartphone/tablet overtaking PC use for general/casual use, e.g. emails, photos, social media, online banking/billpay has really reduced the general public's skill level with desktop operating systems. Probably similar overlap with the subset of people who always dumped every file to the desktop directory instead of organizing files in specific directories.
Even for IDE I have XCode, Webstorm, Sublime …
In general, native apps are still far superior for most tasks I do.
I believe you’re right in that there are money to be made in developing desktop app, but I also believe that the customer base expect thing to be native, so don’t try to do Windows application using GTK or macOS applications using wxWidgets.
Which is why everyone and their dog is going Electron. Linux compatibility is one thing (which no one really cares about, except for software in the public services sector), but users generally expect that their software is available on a Mac - not to mention that people using a Mac tend to be on the better-earning/willing to pay actual money for software side.
I think everyone is moving to electron because web developers are a dime a dozen.
Companies want their application on two platform, use Electron and now their product suck on both.
Electron is actually a reasonable solution for internal and bespoke software. It just not at a level where I can see it being something I’d want to pay for as a consumer. Again VS Code is pretty good, but it’s still clearly not a mac app.
And that happens occasionally with Discord, without running make -j42.
As a non-web developer I'm genuinely curious, what is a good UI toolkit targeting web browsers/Electron that rivals Qt?
If it's a simple SaaS by all means go for it. I really like the idea of being able to toggle things I like/don't like. But most of the times I become a "second-rate" citizen in the eyes of devs when I'm on a lesser-used subset of features.
Example is this service I'm using to manage my small company's finance; because I refuse to toggle on a feature that makes life easier for most people (but not mine), getting support for bugs has been very difficult.
Finding the combinations that result in something broken (through some unexpected interaction of features) would be impossible via QA. I guess you could keep a list of the more popular combination of settings and test those. More likely it means you'll let the customers do the QA for you. The customers will not like that.
If you've ever maintained a system that uses developer feature flagging, the cost is large and typically this is for feature flags that should only exist for a matter of weeks or less.
The nice thing about installing your own software is you controlled the updates. If there was no compelling reason to upgrade and you were stable, you didn't. Most people today could probably break out a copy of Office 97 and be totally fine with it.
I don't think that is the case (depending of course on how we define "the entire software world") I've been a developer for 20 years and never worked for a VC funded company.
There is a tonne of software development outside the realm of VC's.
For a lot of software, like social networks, getting new users and new downloads is the main goal.
When a company is not charging [most] users money, the second best thing is publicity or grabbing and selling user's data. Both options require user churn. Keeping users happy for a long time is not their concern.
Unfortunately this is happening in the FOSS world as well. Constant churn of software products, features and bugfixes to keep users addicted.
I suspect there's so much churn in FOSS, because developers love rewrites and starting from scratch. In the world of commercial software, written by companies, the bosses/owners reign them in. FOSS, on the other hand, does not have bosses or owners...
Among other reasons, they use churn as a way to control the userbase and prevent successful fork.
> FOSS, on the other hand, does not have bosses or owners...
Corporate-driven OSS has plenty.
You know it's bad if there's multiple XKCD's about it.
#1) Software used to live on a disk you buy. That software doesn't change, until buy a new disk. Then it lived in apps, where you can update or not. Now often, it lives in the mythical cloud where changes can happen all the time.
Now, even on the disk front, things were always changing. Often for the better, sometimes for the worse. In the OS world Dos->Windows->Windows 95 were big changes, and the OS9->OSX change also huge! But now the changes are always.
#2) The entire software world is built on VC money. VC money is not looking for slow and sustainable growth. Or a happy userbase of 10k people. The VC world doesn't mind if 99 companies crash and burn trying to harvest the wind while building their sails if one takes off.
#3) Out of the VC/startup world, large companies must justify their existence and every team and every programmer on that team must justify theirs. No one ever stuck around by saying "everything is good, we literally don't need to do anything or acquire another customer, let's all cut out hours to 2 days a week, keep patching bugs and making security updates, be happy with our current level of subscriptions, and spend a bit of time in R&D to make sure we have other bait in the water too if for some reason our users stop liking this.