While this definitely seems like a step in the right direction, it still seems like you're too caught up in your own world as a maker rather than looking at things from a customer's perspective.
Sharing your development process is interesting to other makers and helps you build your network within our community, but it won't do you much good in terms of attracting customers unless those happen to makers too. Are they?
As for getting featured on Product Hunt, Hacker News, etc those are hard to predict, unsustainable long-term traffic sources, and not necessarily where your customers are. Again, it depends on who your customers are.
Rather than starting with the idea, I'd start with the problem you're trying to solve and the audience you're trying to reach. Building the product is probably the easy part. Do people really have this problem though? And can you reach these people at scale?
I'd try and answer these questions first. Just go and talk to them to understand their problem, how they currently solve it, etc.
I also suggest listening to the recent Indie Hackers interview with Julian Shapiro. Towards the end they talk about choosing the right idea to work on.
While this definitely seems like a step in the right direction, it still seems like you're too caught up in your own world as a maker
Likely true... making my first steps and I think this is how you start. You slowly have to get out of your comfort zone.Sharing your development process is interesting to other makers and helps you build your network within our community, but it won't do you much good in terms of attracting customers
Makes sense. For me personally, when I have someone to talk to (a bit) about a project, I easier stay involved with it. Maybe this is a personal "hack" then :DRather than starting with the idea, I'd start with the problem you're trying to solve and the audience you're trying to reach.
Like boiling down the problem and possible solution to 1-2 sentences and approach potential future customers and ask if they agree to have this problem at all?
I continued to think about this a bit..
Do people really have this problem though? And can you reach these people at scale?
So (cold) emailing, asking people at meetups/Twitter/..., reaching out to old employers maybe etc. to figure out if "they" have a similar idea about the "problem" as I do and would be interested in a service to solve that problem right?
I would think this is easier when I have a simple MVP to demonstrate what I have in mind. Am I wrong with this or should I prepare to give a quick demo?
Yep. wip.chat/api for more info.
I'm not 100% sure yet it was the right decision. Like I said, it more flexible than REST, but not as straight forward for developers unfamiliar with it. This might hold back more people from creating simple integrations.
Very cool. But does the Rails app (frontend) driving WIP use the GraphQL API or direct db calls in controllers?
It's usually something where I see someone else work (IRL or screencast) and be like "hey that's an interesting technique!"
what about reading stuff for inspiration (apart from wipchat obviously!)?
- Getting Things Done: The concept of "next available action" was eye opening. Always knowing what the next task is you can work on for any given project. Also the requirement of a task starting with a verb. So instead of just "laundry" I'd say something like "select clothes to put in washing machine". Even though I know what "laundry" means, having it be more concrete helps actually doing it.
- Thinking Fast & Slow: Helps you become more aware of all the common mistakes our brain make.
- The Creative Habit and The War of Art: Both taught me you don't need "inspiration" to do creative work. With good habits and discipline you should be able to do creative work anytime.
- The Effective Executive: No-nonsense advice on how to be a more productive executive.
I read these books quite a while ago. Many of them I wouldn't enjoy today, but they worked for me in the moment. I recommend just getting the free chapter on iTunes/Amazon and if you don't enjoy it try again in a few years.
Nope. I'm not sure how a tool would know how to best market a product?
For screenshots I tend to set a nice background wallpaper, and then take screenshots using macOS' built-in screenshotting tool. You could also use @lukaszmtw's CleanShot which makes this process a little easier.
For the icon I tend to use Photoshop to make a simple animated GIF. There are some tools that make this easier (e.g. I remember there being a tool to easily create a GIF of different emoji), but typically it's up to you to create something that best communicates your concept.