If a tool looks really cool (paradigm shift for the industry) I check it out. If it's a competitor - or hopes to be. AND when I think it could be valuable for me and or my team.
If a product is relevant for you, then supporting it would make sense. Supporting isn't only being part of the launch, but also testing it and providing feedback to the makers.
Feedback is the life and blood of any startup, so it is one of the most valuable things you can do.
@hansvangent I give you credits for this. You're absolutely right. Support is great, but feedback is better to get better results for your beloved products and tools you're using.
As a user of a software, I would appreciate when that tool improves step by step and unlocks more possibilities.
If an idea seems interesting to me, I test the product. If the product is an iPhone app and I like it, I write a 5-star review on the App Store (which I believe is important). Using this opportunity, I would like to suggest that fellow developers be more test-friendly. If an app requires registration, subscription, or payment information before demonstrating any functionality or value, it discourages testing.
I test apps almost daily, or at least sign up/register and take a look around. If it's something relevant to me I try to give it a good bit of time, if it has nothing to do with my work or interests, I will still support, maybe look around the launch page or product homepage, but not always test.
I frequently test apps that are relevant to me, giving them a try and providing genuine reviews of the products on the Product Hunt or any other review platform. This can be especially helpful for others who are seeking similar tools.
It depends if a software is useful for me as a developer to schedule my work-life routine or how much it benefits my personal interests.
I see no point testing software that doesn't fit to my personal routines or interests.
Replies
Sprout SEO Extension 🌱
PixelFree Studio
Flipner AI
PixelFree Studio