I don't think I've created enough individual projects to give good advice, but it goes something like this. Find the sweet spot of something you love and something that would be helpful to other people.
Then search online for similar applications. If you do find an application that does what you're thinking, ask yourself why you haven't heard of this application before. Is it because it's expensive? Hard to use? Outdated? Lacks certain functionality? Requires users to use the terminal or set up their own server?
Try tackling one of those problems in your own project. Some people like to learn a new framework or language while they are making their own project. That is cool, but in my opinion only learn if you need to. If you can make a prototype with tech you're familiar with, that just makes it faster to publish the app.
Then get feedback as soon as possible. Dev websites like DEV obviously, but also users on forums and message boards that would appreciate your app. It is possible that your app might pivot to other features and uses that you might not have thought of before and requires a complete revamp of your tech stack/design.
You mentioned you're thinking about developing a photo blog. Are you developing your own blog? Or is it a platform for others to blog their photos as well? Social media platforms like Insta, Flickr, and Pinterest come to mind. What do you like about these platforms and what will you do differently? Those questions should set in motion answers that will determine your design, your stack, the amount of time you need to commit to etc.
Thanks, I realised that I ve never thought in a kind of that way when I ve got a idea. I am more like at the moment, thinking about what can I do "for me" to improve my skills. But you also giving a way to think differently and further more about the future project :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't think I've created enough individual projects to give good advice, but it goes something like this. Find the sweet spot of something you love and something that would be helpful to other people.
Then search online for similar applications. If you do find an application that does what you're thinking, ask yourself why you haven't heard of this application before. Is it because it's expensive? Hard to use? Outdated? Lacks certain functionality? Requires users to use the terminal or set up their own server?
Try tackling one of those problems in your own project. Some people like to learn a new framework or language while they are making their own project. That is cool, but in my opinion only learn if you need to. If you can make a prototype with tech you're familiar with, that just makes it faster to publish the app.
Then get feedback as soon as possible. Dev websites like DEV obviously, but also users on forums and message boards that would appreciate your app. It is possible that your app might pivot to other features and uses that you might not have thought of before and requires a complete revamp of your tech stack/design.
You mentioned you're thinking about developing a photo blog. Are you developing your own blog? Or is it a platform for others to blog their photos as well? Social media platforms like Insta, Flickr, and Pinterest come to mind. What do you like about these platforms and what will you do differently? Those questions should set in motion answers that will determine your design, your stack, the amount of time you need to commit to etc.
Your Venn diagram made me think of ikigai. I love how the Japanese have a single word that pretty much sums up this concept.
I thought it two when I was the diagram 👍
Thanks, I realised that I ve never thought in a kind of that way when I ve got a idea. I am more like at the moment, thinking about what can I do "for me" to improve my skills. But you also giving a way to think differently and further more about the future project :)