TBH I've created so many things over the years I've learnt my lesson. Now, I always start with a marketing plan: * Who's your target market, and how big is it and what are they likely to pay? * What do they want? * How will you create value you can capture? * How will you reach them? * What's the competition? If you can't answer these or don't get decent answers, bin it and move on. It's easy as an engineer to build…
Ask HN: How do you generally build a product?
51–60 of 73 posts
Re: Ask HN: How do you generally build a product?
#52> how do you find the time to build that idea out Based on this, I'm assuming you want to build an idea that makes money first. You need to solve a problem that's worth paying for. Easily said, of course. The Mom Test[0] is a book about how to ask questions that are worth pursuing as a business. > do some of the good ideas get left out? That's the question really to focus on. Don't worry about developers or building…
You made a valid point about building in vacuum, that's exactly what I was doing with one of my projects last year and was wondering why I couldn't get any users who were sticking around. Sometimes, it can be the painfully bad UI but when that's not an issue either, you know, it's probably the problem you picked to work on itself. So I'm assuming, before working on anything that you think might make some money or be…
> What do they do to get the word out for developers to start working with them, after all?
A very different problem, but this co-founder dating.
It's hard because for people who don't have extensive networks, you're basically asking people to... build a network.
But if you can take an idea far enough with an MVP, get some sales, customers, it's significantly easier to convince a potential co founder.
Chicken egg problem made only worse, I know - but sadly, no easy answers here.
Re: Ask HN: How do you generally build a product?
#531) First start with trying to sketch out (write out) the solution on paper. Writing out your solution forces you to think the problem through. Psychologically, you don't see it as being stressful or as tasking as writing code which means you're more likely to stick with it for some days. 2) Try to work on your idea at least 4 or 5 days of the week, no matter how small the time. You don't have to write code. Sometimes…
Re: Ask HN: How do you generally build a product?
#54I’m a full time indie hacker, building my own products (several in the pipeline) and doing my own design and marketing as well. Regarding the product idea, it varies from an itch I have, to a neat idea but I’m not the target audience, so I ask around (esp. on Reddit), to someone asking me to make them something and I ask if instead of billing my hourly rate, I can sell them a productized service. I jot down my “itch…
Re: Ask HN: How do you generally build a product?
#55Earlier quoted context omitted.
You made a valid point about building in vacuum, that's exactly what I was doing with one of my projects last year and was wondering why I couldn't get any users who were sticking around. Sometimes, it can be the painfully bad UI but when that's not an issue either, you know, it's probably the problem you picked to work on itself. So I'm assuming, before working on anything that you think might make some money or be…
Glad you realized and moved on. It's easy to continue and stay stuck in the vacuum with the tunnel vision and all. Just one more feature. > What do they do to get the word out for developers to start working with them, after all? A very different problem, but this co-founder dating. It's hard because for people who don't have extensive networks, you're basically asking people to... build a network. But if you can tak…
Re: Ask HN: How do you generally build a product?
#56My 2 cents... generally a product is something that has value to others... so, think about that first. Why is your product valuable to others? Explain your product to at least one person who is not invested in the process that would buy your product if it existed. Ask them lots of questions about why they would buy your product. Would their friends buy your product? Why? Can you pre-sell your product before you even…
Re: Ask HN: How do you generally build a product?
#57Think of a product name. Buy the domain name. Launch a cloud linux server, install web server, database, application server. Configure it all up to talk to each other. Build the user creation and auth system. Implement email system for user emails. Start building the hardest bits of the application first, try to get a minimal end to end implementation of the system, iterate over the minimal version improving stuff un…
Re: Ask HN: How do you generally build a product?
#58TBH I've created so many things over the years I've learnt my lesson. Now, I always start with a marketing plan: * Who's your target market, and how big is it and what are they likely to pay? * What do they want? * How will you create value you can capture? * How will you reach them? * What's the competition? If you can't answer these or don't get decent answers, bin it and move on. It's easy as an engineer to build…
What your target market wants is not that easy to determine. I've heard the book "The Mom Test" is a good read to help with this. I've started reading it recently.
Now, I'm thinking of a way to help others (users on my platform) do the same with their products without those surveys, people don't usually fill out surveys and are more receptive to conversations from my experience. Guess, I'll figure something out eventually.
Re: Ask HN: How do you generally build a product?
#59For me, the first thing when starting a project is to figure out who you're building it for and what problem you're solving for them. Try to talk to them and ask lots of questions about the problem domain and about their problem. Allow yourself to be surprised by the answers. This may involve learning to ask open questions and not coming into it with too many preconceptions. Try not to ask questions that assume what you already _think_ you know.
Secondly, try to build something (minimal) as quickly as you can and try to get someone using it. If you are lucky enough to have customers then great, either observe them using it or ask them how well it works for them.
Thirdly, try to iterate as quickly as possible. Whatever you build in the first place probably won't be the right thing anyway so try to learn, as quickly as possible, what is wrong with it, and then change it. Again, allow yourself to be surprised by what you learn and try to be aware of any initial assumptions that you might have, so that they don't lead you in the wrong direction if they turn out to be wrong.
All of the above assumes that you're lucky enough to have customers. If you don't have any then either abandon what you're working on or be content to work on something that scratches your own itch (in which case, you're the customer and you're the one who decides what works and what doesn't).
Finally, I'm still really curious about this TODO list with ideas that you might have. For me, nothing crushes my sense of intrinsic motivation more than feeling forced to pick up items from a TODO list. How does your TODO list work for you? What benefits does your TODO list give you? And are you aware of any negatives that spring from it?
Re: Ask HN: How do you generally build a product?
#60It would be helpful to give some ideas of the sorts of projects that you're thinking of. It sounds like you have a very specific idea in mind. What sort of things do you have on your TODO list and what are you assuming that folks here have on their TODO lists? For me, the first thing when starting a project is to figure out who you're building it for and what problem you're solving for them. Try to talk to them and a…
For example, right now, I'm working on something full-time on what I thought would be really cool to build in January but along the way, I thought of other things as well, some of those require more time than just a weekend. I tend to write those ideas down instead of passing on them or getting involved in them and abandoning my current projects.
Keep doing this for long enough and you'll end up with a long list of ideas over a period of time so that's what I was referring to with the TODO list of ideas, ideas that really intrigue me, stuff I want to build but currently don't have the time for. I'm assuming this happens to other developers as well, at least, some of my friends do this. We even have a shared list of what we want to build together.