Greetings all.
Conversations in the community unthread after 100 comments, making the conversation difficult to follow, and official comments hard to find. For this reason we're posting our most recent update here:
We know this is an important topic to many. We appreciate all of the use cases (pros/cons) that have been presented and the ideas for solutions. We are working toward a longer range strategy that we envision solving many of the struggles you've expressed here. We do not have an immediate solution. Stay plugged into Canvas Studio to watch this strategy unfold (beginning with Assignments 2.0)
This idea was considered when developing our product plan for Q1 2019 and is not expected to influence development within Canvas at this time.
- This idea will remain open for vote.
- If this idea is in the top 10% by vote next cycle it will be reconsidered.
Read more about the feature idea process:
I share your impression, Ron Marx! I'm honestly not sure how this whole process really works in terms of actual implementation. I still feel very let down about the lack of any progress on search; when I attended Project Khaki, search was the only idea among the Khaki array that I had any interest in at all personally. So, when search was one of the features "postponed" without any progress I was disappointed. I was even more disappointed when there was no detailed explanation provided about partial progress, roadblocks, etc. That's when I started to suspect that the ultimate design decisions at Instructure are pretty far removed from the issues as I see them and which drive the decisions I make about which tools to use.
As a result, Canvas is a tool with only very limited value for me, exactly because my priorities are simply not the Instructure priorities. I suspect that will remain the case even after they finally get done with the mammoth amount of resources being devoted to quizzes, grades, and analytics, none of which have any value for me personally in terms of my course design.