Nate,Here's the list of already dones:
These are all done. They were picked first primarily because they were either low hanging fruit or (in the case of Discover) the old way was just that bad. Most of them were done or partially done before I even started.
- New means of browsing discover more efficiently
- redone padding
- a settings page that's easily accessible
- easier access to search on slice
- we added a clock (no one was asking for this, but we had some extra space and it took like 3 seconds)
Right now we have a list of user-requested features for the future, but at present we aren't spending a lot of time focusing on them, because everyone involved is handling bug fixes. But what I have done is created a private github repo and pulled everything from that thread you made, neil, and created individual tickets for every feature. I then went to several related threads and pulled tickets there too. I think total, after adjusting and combining some features and requests where it made sense to, we've got 33 open tickets. A few of those are bugs or regressions, but most are user requests and features.
Once we've gotten to the point where all platforms work equally well on the current feature set, we'll begin ranking requests. For example, the thing you ranked first on your list is first on mine as well, but could take more time to develop and code. I've already begin wire-framing and visualizing that particular request though, because I think it's that important. If there is any more low hanging and important fruit, we may attack that first or at the same time, but if all of this development is really focused around giving more control to the user, your first item is the obvious no-brainer to really start focusing on asap.
I'd love to give you more info, but frankly there's not much more to give. At the moment, it's all hands on deck for bug fixing.
edit: And I should probably say we've not thrown any ideas out. When we can, we'll re-examine a guide. We've already spent some time talking about it and how it could theoretically work into the flow of the app. This is absolutely not a promise that it'll happen, but we're at least talking about it.
Excellent, I think these are excellent things to get out of the way first. Would they be my choices? Probably not, but they are worthy choices made logically.
The fact that you are talking about guide options internally and not just trying to convince users that they are ignorant (my feelings based on the existing posts, not yours) for wanting a guide is also very important.
Hopefully, we can get SD to consider handling more than one workflow or use case.
For example, we never watch live TV and don't ever intend to using SD products. We are OTA only, no cable. All of our TVs have antennas, so why watch live through the SD hardware. We would disable the Live tab if possible.
As for Guide flow, just make a new tab called Guide. Again if possible we would completely disable the Discover view and use the Guide view.
Thank you for communicating these facts.
Hopefully, you will find more facts to communicate in the future.