No-where did I say otherwise, did I? Of course Zune should be developed forward. What I objected to was the idea of having a more or less incomplete MUI3.8 (or less) "Zune" ported to MorphOS and other OS's, expecting this limited (and perhaps somewhat different and perhaps not always 100% MUI compatible) API to become some kind of standard.
It's not very interesting before it's 3.8 compatible, that's true. But when it is, having a port makes a very big difference:
Anyone wishing to target MOS, AROS and AmigaOS at the same time will need their software to work with Zune to have it work on AROS.
If Zune is available on all three platforms, then they get a choice: They can target Zune on all of them, as the lowest common denominator, without worrying about incompatibilities, or they can target three different libraries with varying capabilities.
As long as the capability gap between Zune and MUI3.8 / MUI4 is big, I'm sure a lot of developers will choose the latter option because restricting themselves to Zune means either extra work or fewer capabilities, but as the gap closes I'm not so sure you won't start seeing some app developers preferring to target Zune instead.
The only standard is MUI, it's still evolving AFAIK, and Zune has to walk carefully in its footsteps until it catches up, carefully avoiding "branching out".
The only standard in a fragmented market is what application developers choose to support. Zune has the advantage that it is the only one that has any hope at all of becoming available on all the platforms.
As it stands *there is no standard* - app developers have 3 different targets.
In other words: We'll see.