I want to kill this thread because the title may be confusing to new developers coming to this forum for the first time. I'm going to attempt to rename it "Improving the developer.roku.com site".
You have a good point there, "dead
" in the name might be scary, although "alive and well
" the developer.roku.com ain't.
Can we settle on a middle ground, like "The troubled^ developer.roku.com
In truth, i think me and many (most?) other developers will be happy if "the new" site gets killed altogether because it is nothing more than mascara on top of the web services that https://owner.roku.com/Developer/
provides - but unlike the "old" site, the "new" one actually has serious
problems. In private conversations top Roku developers (plural) have told me they avoid developer.roku.com as much as possible. Nobody has said a good word, that's for sure.
Surely back-pedaling won't be popular with management but if the issues have not been fixed for a 12 months, when will that happen? Looking at the photo above, it's obvious no QA has not spent even 5 minutes reviewing the screen. It has not been tested, plain and simple.
Alternative proposal, how about this - instead of killing "new" site, how about when outside developers waste hours fighting with the "new" portal, we get to bill RokuCo for the squandered time? Internally the Co. is can to cost-share/endorse such bills to the web team. Something tells me the issues will get fixed "presto change-o"
(^) short form for "The Mysterious Yearning Secretive Sad Lonely Troubled Confused Loving Musical Gifted Intelligent Beautiful Tender Sensitive Haunted Passionate Talented Mr. Ripley