Here's a couple of examples of the groundwork laid by sketching the flow and some significant project points ahead.
An initial sketch that examines the student-user flow
Getting a grasp on how the stream may look and behave for the student.
These illustrate working through how will the lesson content and feedback share the same space.
I wanted to figure out the conversation between the feedback view and the native interface.
Lesson content occupies the very center of the screen under everyday product use.
The content will move to the left to create room for the feedback and lesson to share the same space.
Notice how busy and overly complex this is.
With each iteration, the interaction became more streamlined...
and closer to this exercise's goal; an excellent baseline experience.
With this version, the messages appear in a time based list with links to the corresponding classwork view.
Feedback on the platform would be in one direction, from teacher to student, to avoid all conversations happening only on screen.
Again, further simplification of the interface towards a baseline.
Here, I explored what canned or clipped responses could look like when moving through a more significant roster of students.
I enjoy rapidly creating multiple versions of the UI's important components to make sure I've landed on the best possible option.
These were a direction that we examined for each potential state for a single message.
The work my team put into designing and building this feature met the goal of creating a fantastic, baseline feedback experience upon which we could build.
The student is able to view the instructor's feedback next to the work to facilitate acting upon their feedback.
The teacher is able to view the feedback entry window next to the student's work