I think the Apple II is one example of this.
It's also easier to run a feedback loop. If you implement Y, but Amy doesn't give you $5 a month, what are you going to do? Knock on her door? Users have no idea what they want half the time, anyway.
If you build a product and no one cares, it bruises the ego a bit more, sure, but if you self reflect, you can eek out your own bad assumptions, or bad implementation, or maybe a way to pivot that keeps your product ethos.
First let’s look at B2B, there the “user is not the buyer”. The buyer doesn’t care about “good taste” they care about a lot of other things.
(“Where is my SSO support for multiple users, I’m not going to have my IT department worry about tracking down usernames when Bob leaves)
https://news.ycombinator.com/item?id=46919794
Second, if you have the feature that people need or a service or network effect, they will suffer through a bad app - see every Electron app ever.
That “smaller team” may not be around in a year and if you are lucky, you’ll get an “Our Amazing Journey” blog post. Does this product export to a format that my design team can import into Figma if this product goes tits up?
Especially when, who the heck has time for trying out a dozen products? That's at least a full day of work, which probably costs more than the software itself.
No, you just read a few reviews to find the best full price option and best budget option and figure out if the budget does what you need or not. And often go for full price just because you don't even know what features you'll need in 6 months which you don't need now, so safer to just learn the option that is the most future-proof.
Anecdotally I haven't tried Codex and use Claude Code. The day I try Codex will be when I hear from my friends/communities that it's much better. Same for IDEs, STT tools, etc
Let's be real, unless some soul somehow had the same 20% as yours and left a review somewhere, you won't know if the features you need, or their implemention, fit your need until you try.
Then again, I do this in my free time. At work, I rarely deviate from what is provided and the handful of things that I explicitly added.
Are your customers selecting one of five features in your product, or choosing any twenty from among a hundred?
Games are closer to that than any other type of software even if they tend to cluster around popular genres and styles a bit much.
I don't know anyone that doesn't use a combination of at least one simple, one feature laden, text editor. Most of us via notes apps, etc., routinely move between a range of text complexity, suitable to a range of things we want to write.
Having the simplest to the most powerful apps be consistent between each other, wherever they have feature commonality, would be really nice.
Which is where the bulk of the other 80% of features come from. It’s a cycle.
You start as you describe, you expand, you end up with this enterprise monstrosity, everyone using a different 20%. New tool comes along, you start as you describe…
Hopefully you can afford to say "No" a lot.
[1] https://www.joelonsoftware.com/2001/03/23/strategy-letter-iv...
What you’re saying is basically a majority of SaaS shouldn’t exist because it could just be an excel spreadsheet. Why would anyone pay for a subscription or something when they already pay for excel right? Problem is spreadsheets are a blank canvas and can be difficult for people to build. Just like a design software like adobes and figma. This product is trying to focus on one particular use case of design software and simplify it. It’s not a horrible idea and can exist in the market. I’m not sure it will succeed but conceptually it’s not destined to fail for the this reason. I think you need to also define what success means. For a single dev, could just be a thousand paying users. He’s not necessarily trying to be figma.
My most successful company was a tool that focused on 10% of a ERP feature. One that I had used and implemented at corporates but knew ERP vendors were selling hard for having 100s of features of which I only cared about 20%. Not everyone cared about those same 20% but I found enough people that did and liked my opinionated take on the software. It would have never worked if I had this mindset.
Vecti looks like a Figma clone if its landing page is anything to go by. You're not going to have an easy time convincing people to migrate from Figma to a clone.
I’m not saying anything good or bad against this product just that it has a right to exist and could work (whether it will or not is not what I’m arguing).
I am not even sure it was still true by the time her wrote it. It think that there is a set of core features (laying out stuff in a table, simple formulae) and some very commonly used features (e.g. graphs, data filtering) and a long tail of less commonly used advanced features (pivot tables, database like formulae like VLOOKUP).
Its more like 80% of users only use the same subset. Less commonly used stiff is important to the people who do use them, so you need it to sustain the network effects and enterprise sales.
To me this is an argument for more apps that do less extremely well instead of a handful of apps that do everything poorly. There's nothing wrong with a tool that's honed for very specific user. They'll never hyperscale, but that's also fine.
Or then again maybe they can. Google Docs is plenty popular despite being closer to WordPad or TextEdit in terms of functionality than it is to MS Word.
Then Steve Jobs gives one of his most memorable statements about building good products while ignoring the taunt.[0]
I got your reference. Cyberdog!
for reference if anyone is interested in poor old cyberdog (and the meme reference): https://oldvcr.blogspot.com/2023/10/teaching-apple-cyberdog-...
In my experience, what people use is very malleable to how easy/good the flows are they are presented with. Given 100 equal options, they might use 20, and nobody picks the same 20, but given 25 options, 20 of which present a very good experience, almost 90% will go with those 20 without complaints.
On the other hand, I'm afraid that if this did happen that FFMPEG frontend would look like a GNOME app and I would hate using it.
Want to generate a video, it's just a few lines of code. Want to connect the user's camera (with permission), it's just a few lines of code. Websockets? About 4 lines of code.
There could be 1000s of options for each of those but they mostly distilled it down to what most people need, and they're cross platform.
My favorite frontend is MPV, because I can generally forgo a GUI and just use single keystrokes to do everything.
I don't think that's really true, unless the behavior of each toggle is tightly coupled to the behavior each other toggle.
Case in point - most mature apps nowadays do have hundreds of toggles for various settings and features.
https://developer.mozilla.org/en-US/docs/Glossary/blink_elem...
And Gopher support…
It's wild - I'm a big gamer but I strongly doubt I could even list 1500 games across all systems and time. And that many games make $50k+ each year.
[1] - https://gameworldobserver.com/2023/10/06/steam-stats-41k-gam...
I'm really just describing the long tail at this point. Gives me hope that maybe I can find that product before getting to retirement age.
Like lots of people prefer Trader Joes (limited selection) to a bigger super market
The current system of a near-monoculture of garbage sucks.
I think this is a weird question. Sure he can't be the only soul in the world to need only those features. Those 20% people need gotta overlap. So I think a more generous way to read your question would be "what makes you think that the features that are personally important to you are the same features that the mass audience need?". If that's what you meant then I'd ask why appealing to the mass audience so important? Why maximize sales and risk making your product worse if the core of your product is to make things you care about?
This is a phrase that gets repeated and it sounds clever. But it's completely at odds with statistics, specifically the normal distribution.
We should say, people use 80-90% the same features, and then there's a tail of less common features that only some people use but are very important to them.
This is why plugin systems for apps are so important. You can build an app that supports the 80% with a tightly designed set of core features, and if someone needs to go outside of those they can use/build a plugin.
Good question, what's the pitch:
“Vecti is a browser-based UI design tool built from the ground up with one core belief, that creators deserve tools built specifically for them. Better performance, better privacy, and better alignment with their actual needs. A tool that just works, built by someone who genuinely cares about the people using it.”
Hmm. Did founders of Balsamiq or Figma not care about the people using it? And who if not creators were they built for?
“Share & Present - Set viewer and editor permissions at the team or project level. When it's time to present … let your work shine.”
Oh, right, for the people who pay the creator.
This is a provocative joke, isn't it?
Could you elaborate a little bit more, how a sole developer should do these things in a meaningful way, if even larger companies and start-ups fail with this?
The most basic way is to do a 30 min interview with 20 designers that cover a few each of freelance, small company, med company, large company. Find out which features they use and don't, and what their pain points are, and whether a tool with less features is something that would be majorly helpful or not very important.
Then do a round of validation with AdWords, can you get designers to click on the ad for something advertised as simpler and bloat-free, go to a landing page that explains what it has and doesn't have, and then put it their email to find out when it launches.
To me, that is the absolute bare minimum to make sure you're developing something that can be a business, rather than just a hobby for yourself.
And these are not my ideas or anything. They're pretty standard stuff, and there's a lot more you can and should do as well.
I remember reading something like this while talking about developing in C++.
If you agree however that functionality profiles will repeat among users given a large enough user base then it implies a particular limited feature set can still be totally adequate to support program development.
And that is with assumptions stacked against you succeeding, if indeed, as would seem likely, that some user profiles are more widely distributed than others it would follow that a successful product can just focus on those.
Joel Spolsky said (I'm paraphrasing) that everybody only uses 20% of a given program's features, but the problem is that everyone is using a different 20%, so you can't ship an "unbloated" version and expect it to still work for most people.
So it looks like you've built something really cool, but I have to ask what makes you think that the features that are personally important to you are the same features that other potential users need? Since this clearly seems to be something you're trying to create a business out of rather than just a personal hobby project. I'm curious how you went about customer research and market validation for the specific subset of features that you chose to develop?