Question for both player developers and plug-in developers:
Looking into the future beyond OSMF 1.0, what are your expectations for backward compatibility with the APIs from one version of OSMF to the next?
As development progresses from version 0.1 up to 1.0, the customer feedback we've been getting has been great, and it's directly influenced some our choices on features and design, and consequently the APIs.?We plan to use the moniker ''version 1.0'' to signal that the APIs are set and that we'll support them for some period of time.?How long after 1.0 do you need those APIs to keep working??Can the 1.0 APIs change for 2.0, or do they need to continue to work in 2.0??How about 3.0?
Given how fast things move with online video and related services, it would make development of future versions of the framework much easier if we can place less of an emphasis on enduring backward compatibility.?The challenge is finding the right balance between a blank slate and permanent backwards compatibility.
Any thoughts are appreciated!
Sumner Paine, product manager
No comments:
Post a Comment