It doesn't surprise me when a code base is retired. There are strategic considerations here so that M/S can use the same code base to support web based and smart phone and tablet markets. What this does is allow a higher user predictability of what they will see when using this app on the different platforms. It also allows a smaller support footprint and a coherent upgrade cycle.
Very interesting, Sonora. So in other words, Portfolio Manger is being dumbed down to the level that will fit on a smartphone screen?
Essentially, yes, because a common code base is easier and cheaper to maintain. Unfortunately, using standards that all platforms subscribe to doesn't usually lead to the best user experience, and in this case, it was exacerbated by what appears to be woeful project management.
You learn from your failures much better than you learn from your successes....Comforting?