After a few years, several iterations of payment structures, roadmaps etc I have to ask the developers, "Is Vuo ok?" I've ended up relying on Vuo in a professional environment and I have to ask what is going on here with the lengthy development times. While I truly do understand the limitations that small companies face, as well as the downsides of a roadmap/voting system as the initial one(community's fault imo, not kosada) vuo now appears vastly different to the initial estimations and looks more like a 10 year endeavour. There are quite high-level features being implemented and voted on before groundwork is even in sight(more opinion, i know, but see things like fluid resizing while macros and universal multiport is missing for example ). As it happens, VDMX shares a user base with Vuo and their development has also gone very quiet in the last few years. Two amazing platforms that work really nicely together have slowed to a point where it spooks the people who rely on them for their businesses. I definitely fell victim to the roadmap as I made the continuum of choices to invest the time and money into Vuo. Money well spent and great value IMO. Happy to spend more. But now I'm just getting frustrated at the dangling carrot of features chosen to be implemented, no idea when or to what extent, with the looming possibility of it being abandoned by its creators(inferred from the dev times and pricing polls etc). I'd love to be wrong but it seems pretty clear. At the start there seemed to be so much effort going into being transparent about the development. This obviously backfired, fair enough, no promises etc. But what is going on? If there has been substantial engineering challenges or something then let us know. The roadmap may have caused as many problems as it solved but it certainly gave us an indication of the level of commitment to the development. Users have roadmaps of their own, which is why kosada's was so appealing, what's the plan?