> Kagi didn't need to beat Google for everyone; they just needed to serve that specific slice of users perfectly. They focused on being the ideal 20% for people whose 20% Google was ignoring. Yes, this is actually a critical insight into how to find product-market fit
When it comes to Kagi, it just needs to be the old Google. Something that new Google abandoned.
Users only care about 20% of your application
131–140 of 199 posts
Re: Users only care about 20% of your application
#132create issue, edit issue, move issue, update issue status, close sprint, repeat
Re: Users only care about 20% of your application
#133Re: Users only care about 20% of your application
#134Earlier quoted context omitted.
As best I can tell we've never sold the same product twice. Product roadmap is "whatever the last person I spoke to asked for." And tech debt maintaining a grab bag of 5,000 almost-but-not-quite-entirely-production-grade "must have" features that the customers rarely if ever use despite claiming that not having it was a deal breaker, is, well, debty.
The best decision I ever made was moving from a company that acted on the whims of whomever the sales team spoke to last, to a company that had a strong product vision and was happy to say no to their customers on occasion. It's a lot less exhausting when you're not changing priorities every quarter. You also avoid the soul crushing experience of working really hard, crunching to get a feature out, only to realise yo…
The reality is I only get paid because of those deals, and the post deal tech-debt sprint never happens.
So the work has to get done and if sales doesn’t give time for it to be done properly then in 3-6 months velocity will drop and the sales pipeline will dry up.
Any company that can’t understand that is not a long term company I want to work at.
Re: Users only care about 20% of your application
#135The entire premise of an "application" is, in my opinion, a huge mistake. Each application, by virtue of being just that, is designed to be a silo of functionality and usability. An application monopolizes the functionality for the use case it was designed to apply to. Not only does an application hold its functionality hostage, it insulates itself from the functionality of other applications. This creates a brittle system with incredible overhead.
There's a reason many of us prefer to use a terminal emulator and shell utilities: they are designed with the opposite goal, to collaborate with each other as much as possible. That's often worth dealing with the ~40 years of cruft that the shell comes with, but accessibility could definitely be improved.
Re: Users only care about 20% of your application
#136Re: Users only care about 20% of your application
#137Re: Users only care about 20% of your application
#138And the first reason I don't is because I'm not interested in promoting it, and it's pretty pointless to release to no one.
But the much bigger reason is because I'm not interested in implementing the remaining 80% that I don't use myself.
Re: Users only care about 20% of your application
#139I kinda miss the unix philosophy... one tool for one job. A PDF reader should read PDFs, there's no need for it to have its own (possibly paid) cloud service and an AI chat bot. I do get why some integrations are beneficial (eg. office software with text editing, spreadsheets and a database, so you can generate eg. letters with data from a database, etc... but every service needing its own cloud and adding a useless…
Once you have a pdf viewer users want rotating pages, then bookmarks, then highlights, then form filling, etc.
That “just a pdf reader” is strictly worse than every pdf editor (which have to meet the minimum requirement of a pdf reader).
Apple’s Automator and Preview combo for me are indispensible and perfectly follow the Unix ideal. Automator composes well, and Preview does all the pdf editing well, and together they’re excellent software.
The version of Preview Apple just released on iPad is however basically just a reader, and do it hasn’t made itself relevant to any of my workflows or needs.
Full featured plus composable. That’s the sweet spot for the best apps.
Side note: I’m surprised there’s no ffmeg or imagemagik for pdfs (maybe there is?). Someone should build that.
Re: Users only care about 20% of your application
#140Very true. But then you start selling to Enterprise and everything changes. Because one missing "hygiene feature"* can tank the the whole deal. And every Enterprise has a different one. *like a toilet. It needs to be there. You use it 3 minutes per day. If it is not there, the house is uninhabitable.
Damn you must get a lot of fiber.