9 ms·
Why isn’t someone using my software product or open source tool?
- DC-3 8y ago> And if the tool is meant to be used by devs, still describe your tool in a way a non-developer can understand Why?
- wastedhours 8y agoDevs are often not (although sometimes are) the ones that hold the company credit card or are the gatekeepers of organisation power.
- deleted 8y ago[deleted]
- deugtniet 8y agoMaybe to explain the decision to a non-dev colleague?
- DC-3 8y agoWhy should they have to do this? Is a carpenter required to explain to an interior designer why they have a preference for a particular type of chisel?
- corobo 8y agoIf they're asking the interior designer to buy it over some other chisel, probably
- personjerry 8y agoYes, of course. This chisel damages my designs on the table, can we use a softer one? No, we can’t because the material the table is made of won’t be malleable to any softer chisel.
- DC-3 8y agoThat's not a problem with the chisel, that's a problem with the carpenter. The chisel should be wholly abstracted away from the designer's perspective.
- matte_black 8y agoThat requires a higher level of trust in the carpenter to simply do the right thing. In the absence of sufficient trust, a definitive explanation is always required for a party to be at ease.
- thecatspaw 8y agoI did have to explain jrebel (java class reloading while running) to a manager lately, so it definitely happens
- emodendroket 8y agoHe does need to justify his choice of materials and his approach -- certainly by the time he is bringing in heavy machinery. This metaphor is too muddled to tell us much.
- pjc50 8y agoThis entire subtree of discussion has convinced me that developers should not be trusted with metaphors, let alone chisels.
- DC-3 8y agoIf it gets me into webshit weekly it'll all have been worth it.
- deleted 8y ago[deleted]
- corobo 8y agoOff the top of my head - different skill levels, different language barriers, different purchasing power, different management layers to sign off on a product
- deleted 8y ago[deleted]
- KineticLensman 8y agoThe description could include features, advantages and benefits: - Features - what the tool does; - Advantages - how are the features better than the competitors'; - Benefits - why are the advantages useful to my business. Users (devs) are typically interested in features but the people who make usage/purchasing decisions (often non-devs) are more interested in benefits.
- pjc50 8y agoThe dev-specific explanation will often be dull and hyper-specific, narrowing your target market even among developers.
- matte_black 8y agoAnd at the same time, don't make the explanation sound too patronizing or infantile, or litter your landing page and docs with stupid little memes. Strike a professional tone.
- emodendroket 8y agoEven if your audience is a developer they'll probably more easily grasp a plain-language explanation than a technical one as they skim search results.
- DC-3 8y agoThis isn't true though. Here's the description for, to take an example, Rust: > Rust is a systems programming language that runs blazingly fast, prevents segfaults, and guarantees thread safety. Succinct and understandable, and exactly what a developer chancing upon the project wants to see. Were this to be made accessible to non-developers it would need to read something like this: > Rust is a programming language for developing computer systems and applications that runs blazingly fast and prevents errors when programs try to access the wrong memory, or attempt to work with that memory in two different places at once. It would be less readable and less appropriate for the primary audience of the product.
- emodendroket 8y agoWell, to use a hoary old saw, things should be explained as simply as possible, but no simpler.
- DC-3 8y agoIn broad terms, I'd agree with this adage - and to bring us back to my original point, I'd argue that 'as simply as possible' is in some circumstances not understandable to non-developers and that's ok.
- pdonis 8y ago> Were this to be made accessible to non-developers it would need to read something like this: No, it could read: "Rust is a systems programming language that runs blazingly fast and is more reliable and secure."
- DC-3 8y agoWhich is an even worse description because 'reliable' and 'secure' are just adjectives that can mean almost anything you want them to mean and thus tell the intelligent reader almost nothing about the product at all.
- krageon 8y agoAny extra effort I have to expend to understand your thing within the first five minutes of seeing your webpage means I get closer to closing the tab and never looking at it again. I'm capable of following extremely dense developer-oriented information, but I won't do so without an extremely good reason. I'd much rather speedread through a paragraph of information that had some effort put into making it legible.
- deleted 8y ago[deleted]
- danesparza 8y agoAlso: Have you built something people actually want to use? (There is a good chance the answer to this is 'no')
- ElectronShak 8y agoThis checklist misses the most important question; Are you using the tool yourself?
- aaron-lebo 8y agoIs it too much to ask for evidence for any of these claims? More than "trust me"?
- carlmr 8y ago>If you know of good resources for the folks interested in learning more about marketing or sales, reply with links and I’ll happily RT. She's crowdsourcing it, very efficient from her perspective.
- DogLover_ 8y agoMy pet peeve: Not providing screenshot, gif or video. Some developers even do that with themes. Yeah, I am not going to DL a theme file only to find out I don't like.
- geff82 8y agoThis is one of the most common errors that open source projects make: not providing screenshots, not providing info for the beginner. There is almost always some "help us" or "documentation" corner on the web pages, but the screenshots, even if it is just a CLI tools, are too often missing.
- __david__ 8y agoWhat's the point of screenshotting CLI tools? I'd much rather have an example command line that I can copy/paste than some image of a terminal...
- moepstar 8y agoI, for one, have been helped much by some project providing screenshots or even animated gifs of input and possible output by a tool...
- pvorb 8y agohttps://asciinema.org https://asciinema.org is a great alternative to providing animated gifs.
- romwell 8y agoAnd, for everyone's benefit, LICEcap[1] is a FOSS tool to make just that (animated GIFs showcasing your software) from the guy responsible for Winamp and Reaper DAW (the GIF's on the Reaper page are made using this tool). [1]https://www.cockos.com/licecap/ https://www.cockos.com/licecap/
- DogLover_ 8y agoFor me it is about seeing how a tool can be used and if it is worth installing. I am not going to bother install a tool and then try a command to see if it is worthwhile to have on my computer. I try to keep my computer junk-free so I only install something if I believe if its any worth for me.
- mattlondon 8y agoMissing: marketing? Just being able to find the product even exists is crucial in my experience. They wont even get to reading the description or trying out the product/demo if they don't know it exists. Point #7 is getting at this, but I personally feel like this should be Point #1 and probably also have a load of sub-points about it :-) A single post on a forum or a handful of blog/twitter posts probably isn't going to cut it. You need relentless self-promotion via appropriate communities (which might be twitter, but possibly IRC, forums, mailing lists, hell even youtube) in a genuine & non-spammy way that is appropriate, interesting/useful, and (crucially) relevant to the people in that community/discussion. Once your product becomes more widely used and well-known enough in those communities, then it starts to become a bit more scalable since your happy users will suggest people use your tool for you, and you dont have to be the one to pounce on every opportunity to suggest people use your tool to solve their problem X. Marketing is tough and its a really crowded space.
- grosjona 8y agoThis checklist is a petty distraction from the most pertinent truth; it's all about trust. Reputable people and companies don't trust your project because neither you nor your project have connections to famous people or companies. Big companies don't trust projects that aren't used by other big companies. Especially open source projects; this is because companies don't trust someone who works for free and has no skin in the game (nothing to lose). Small companies and individual developers also tend not to trust projects that aren't already used by big companies so it's a catch 22 from any angle. Trust in open source is about money; you need connections to big capital. Everyone follows capital like moths to a flame. You can have the worst product in the world, but if you have connections to big corporate capital, you will succeed. That's what I learned from my own open source work; without meaningful social connections, it took me about 10 years working nights and weekends to get one of my projects to reach 200K+ downloads per month. I have about 4 full years of 'failed' projects behind me; even though they were actually successful from a technical perspective.
- maze-le 8y ago>> neither you nor your project have connections to famous companies or people It may come across like this, but most often, a decision is made against a solution by an individual, because the risk of a project like this not being maintained after a while is quite high.
- grosjona 8y agoIf you're talking about a small/trivial/low-complexity open source library then that is probably the whole story but if you're talking about something more ambitious and opinionated (like a framework or platform) then the element of trust becomes very significant.
- adim86 8y agoI think the first points are the most salient. Developers undervalue the skill of marketing and sales frequently. It is one of the most powerful secondary skillsets a creator needs. If you are unable to inspire, trust and expertise you will forever have a hard time selling your product. I wrote a post on this area just a couple hours ago and what mindset can help fix that: http://blog.adimofunne.com/no-one-gives-a-shit/ http://blog.adimofunne.com/no-one-gives-a-shit/
- _31 8y agoI enjoyed your blog post, it touches on an important point that I find myself getting caught in. Explaining what I'm building in a technical manner or with a logical description that doesn't address what people really care about, "how will this product help me (save me time/money)?"
- adim86 8y agoHahaha, glad you liked it
- ransom1538 8y agoFunny story. On my last 2 day hack project [1] I was really concerned about "no-one-gives-a-shit". So the last project I created something everyone wants: You trade Github stars. Even though the users loved it, it will not spread because on any forum/twitter/channel it is down voted almost immediately. Even though people do give a shit - the group that hates the project drowns it out. https://www.gitstarred.com https://www.gitstarred.com
- Timpy 8y agoI'm not trying to be inflammatory but I think the first issue that comes to mind is that giving stars at random kind of circumvents the meaning of stars.
- pnloyd 8y agoThe the reason this is disliked is pretty obvious IMO. It's undermining the value of stars as an indicator of a projects health / usefullness. People explore tools and libraries on GitHub to incorporate into the work they do at their jobs. If this were to take off it could potentially make everyones job harder, yikes!
- blensor 8y agoMy most important takeaway from my past projects is. No matter how cool/sophisticated your product is, people are interested in solving their specific problem and won't discover most of what your product can do. They are coming to your site/product because they tried to solve a specific problem. So focus on a very narrow use case and make that as simply and frictionless as possible to solve (installers for all platforms, bundled libraries, simple tutorial for the main use cases people are downloading your software for, ...). Your product may still support all the cool stuff you put into it, but accept the fact that most people wont use those features. Once your user is invested in your software he might try to expand his use further which is what might keep your users invested, but to get there you need those specialized narrow key use cases that are your hook to get them.
- aequitas 8y ago"4. Do you compare your tool to other similar tools so people feel educated about pros/cons of yours?" This I find is an important one most developers forget. I want to know why you consider your tool/library different from the solutions already out there. It might be better in some respect, it might sacrifice some functionality for the benefit of simplicity, usability, etc. Or you might have created a 'yet-another-X' in which case I probably won't bother as I might already have a solution I'm fine with.
- mbrumlow 8y agoIs this the new trend? Somebody relatively new to the tech industry who seems to have time to write tons of "expert opinions"? I have seen more and more of these sorts of articles coming on HN, and other tech orentend places on the internet. I am starting to question if coding is the right path for anybody doing tech, and simply skip stratit to being a expert in field that takes decades to master even a small segment. It's not every single post. The ones I am talking about are ones where they have worked a hand full of a jobs -- about a year each and yet find themself speaking at conferences and writing grand articles as if they are somehow a proven expert in the topic they are talking/writing on, but lack the actual experience to justify their stance. To me, the real experts who have something valuable to say are probably too busy writing code and solving problems. It is not until much later in their career can they even begin to connect the dots of their mistakes and success to be able to talk about them. I think people should be leery of advice given by those with no real track record to support their views and positions. Yes, I know this is a bit of rant, but it seems to me that the industry is starting to look a lot like other industries where a class of people who actually can DO things are getting left at the sidelines while those who only talk about things are being trumpited as superstars and leaders of the industry -- without ever writing any significant amount of code or being a valued team member. Please feel free to correct my thought process on this, I am open to other interpretations of what is going on.
- Isamu 8y ago>as if they are somehow a proven expert This article isn't that, though. It's some common sense recommendations from a person consuming software. Almost anybody can write that, and if it's actionable advice, so much the better. Shallow topics can afford to have new people come in and give their opinion. I've got to say though, I'm not reading lots of those articles. I'm reading the articles that have technical depth. Just my preference.
- hasperdi 8y agoI agree with you. Conferences these days for example, they are more focused on passing their inclusivity quotas than making sure speakers are expert in their subjects. That is disappointing.
- WhitneyLand 8y agoRelated: If you’re trying to decide between two projects you want to start is there any methodical but simple way to determine which might be more useful or gain more traction? I don’t mean methodical as in heavy or complex. Example, there’s a short book on designing good usability into a UX with some really simple and quick methods (https://www.amazon.com/Rocket-Surgery-Made-Easy-Yourself-ebook/dp/B002UXRGNO https://www.amazon.com/Rocket-Surgery-Made-Easy-Yourself-ebo...). Isn’t choosing which open source project to invest in a bit like market research, as is UI/UX design? Maybe that’s stethching an analogy. The point is I always have strong intuitions and opinions about what project to invest time in, independent of interest/passion. However, it seems even one or two more methodical decisions processes could be provide useful data points to factor in. If you feel roughly as passionate about two projects, why not try to maximize your chances all the work will go somewhere?
- sevensor 8y agoThere's nothing wrong with this advice, but you could do everything on the checklist and still attract no users. However, I'd like to question the premise that that's a good way to measure the success of a project. Having written a very successful open-source library with one user (me), I'm quite satisfied with how it turned out. Some of my other stuff has more users, but I can't say I'm happier with it.
- objectivetruth 8y agoMaybe somebody can correct me if I'm wrong, but I think that there's an implied and generally understood "...that I want other people to use," at the end of that headline.
- sevensor 8y agoThere is. It's what I'm responding to here; I want to contest the idea that attracting users is a measure of success. I wrote a library to do something that nobody else really wants to do. But I wanted to have it, I think it was well-executed (one design flaw notwithstanding), and I'm glad I wrote it. So it's a success, and it has exactly one user.
- dredmorbius 8y agoGood advice. "Please forward to marketing" is based on one of my highest-rated HN comments. It starts: Tell me what your product is. What it does, where it works, how it does it, what it requires. Is it a physical product (or is it shipped in one), an interactive application, a Web service, a programming language / tool? As a reader notes, don't make me use Wikipedia to figure out WTF your company does. https://old.reddit.com/r/dredmorbius/comments/27d5xr/please_forward_to_marketing_how_to_present_your/ https://old.reddit.com/r/dredmorbius/comments/27d5xr/please_...
- keredson 8y agoYou have to get it linked on HN for some shameless self promotion. For instance, check out my project https://github.com/keredson/gnomecast https://github.com/keredson/gnomecast, a linux native Chromecast broadcaster for local files, which supports MKV files, subtitles and 4K! I'm only a few stars shy of 1000! Help me out here guys! =P