On the flip side, you'll probably be able to better break a
chicken-and-egg issue if you implement your ideas in a private copy of
Android, and use this to demonstrate the feature and how it works
against existing MMSCs and interoperates with devices that don't have
your feature implemented. Seeing a feature in action always makes a
better impression than a simple theoretical description.
Looking much further in the future, if your improvements get
incorporated in the standard, you'll already have them implemented as
a prototype, so you'll have done the first step toward a
production-quality implementation (and you'll have an implementation
that other vendors can use to bootstrap interoperability testing).
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.