That may have been the case with the initial Android build, but with the death of this and the migration to the CE code, and with the changes with Cisco Spark and consistency of the endpoint look and feel across multiple platforms, those things that may have previously been on the old Roadmap are likely not on the current one.
Cisco being Cisco[1] doesn't change the fact that Cisco billed the product to do X at launch, and told us it would do Y shortly after launch. I was simply trying to defend those in this thread who are being told that feature $x or $y was "never on the roadmap", because that is clearly not the way the story actually unfolded. Cisco is a business and has every right to change their chosen direction on a product/solution, but by no means do we the consumers of said products/solutions have to agree with them.
So, in short, never purchase a product for what it may do in the future, as roadmaps and feature sets change, and those things may never come to fruition.
Congratulations, this is the most condescending thing some rando on the Internet has come out of the woodwork to say to me since the days of Usenet.
At no point do I infer that I purchased the product FOR the two promised features I was discussing, I simply make the statement that the features WERE promised. Your condescending statement infers that these two things are one in the same, when in reality you can obviously have one without the other -- as in this case.
-jd
[1]: "Cisco being Cisco" is heretofore defined as follows: When Cisco takes their previously-chosen product/solution which has been developed to the point that it could be objectively considered to be "80% of the way there", casts it off to maintenance mode and ceases further meaningful development on it in favor of their newly-selected product/solution which at initial release could only be objectively considered to be "20% of the way there".
