@ Nearly-Right
I think you're right on about the lack of news being problematic.
It's a weird dynamic we have in the Amiga market. We have a long history of vaporware announcments, culminating, I think, with Amiga, Inc.'s Executetive Updates in the 2000-2001 period. Eventually even they said that they wouldn't announce anything until it was ready to ship. They've been essentially silent ever since (apart from additional vapor announcements), and I think that others, consciously or not, don't want to be perceived as another Amiga, Inc. (or similar non-delivering entity).
The pendulum's gone too far in the opposite direction, though. We've gone from vapor to nothing and I think that's hurting the "market" just as badly. With no news, it looks like there's no activity and users are ready to throw in the towel, whether that be leaving the platform (as seems to have happened with a lot of Pegasos/MOS users), or declaring a product dead and asking for keyfiles. If I may suggest, no perceptible news leads to no perceptible user interest leads to no developer interest, maybe?
But there is interest, as the occasional, yet lively, IBrowse (and MorphOS2, etc.) threads show.
I think everyone is (or should be) aware that Amiga development isn't sustainable as a primary business and that coding is done on one's own time and therefore takes longer. No problem. I was too harsh with my comments on IBrowse development being slow. Amiga users are patient. They wait. But if it looks like there's nothing to be waiting for, then that's the problem.
Not asking for release dates. Maybe just a semi-annual check-in. What's been worked on, what's still to be done, a screengrab or two (WinUAE is great with these sorts of updates). That's all. And I'm not just talking about IBrowse. Visible activity on any product would help sustain the market (maybe even expand it if some hardware turns up), benefiting users and developers alike.
EDIT: Bottom line: Take pride in your products and let people know they exist! :-)