@dansup i am not familiar with the code base, true, and devil is usually in the details I know, but I am familiar with long term compatibility of evolving products.
A stable versioned api is good. I think most of the work should be on client apps, right? Client apps can test for new versions of APIs and gracefully fall back on previous versions? This sounds like a valid design pattern even if I'm not actually familiar with the implementation details...