I would suggest making a list of questions or template to ask yourself for any problem you decide to solve. Find out what you can do (given your constraints) and what you can't. For example, I prefer apps that don't require full-time support. Being in Non-US timezone, it will be hard to provide support.
I documented my questions here: https://amols.blog/product-led-growth/17-questions-to-ask-be...
These apply to side project as well. Do add your own or create a similar doc to guide you further.
Good luck!
If you can come up with a good solution to an existing problem, perhaps an app of some sort, create a landing page for it using some mock-ups (e.g. using Sketch, another thing I haven't used!) along with a mailing list subscription to indicate their interest... if it picks up, you know it's worth dedicating resources to the problem. Then when you're ready to release the software you know you have some potential users/customers - they could even have a trial of early versions and give valuable feedback.
There are downsides, of course, e.g. giving away your idea to people who may be able to implement it quicker than you do - but they won't have your mailing list!