With the introduction of Apple Silicon at last week's Apple WWDC 2020, the Mac is ready for the most significant transition of all time! Will we see Canvas Mobile Apps on macOS for the first time? The truth lies below!
Well, you might think that it is Apple's version of Intel's x86 chip, right? Wrong. Apple Silicon is using ARM processors (the AXX processors found in many iOS devices, including the iPhone and iPad).
Chart showing the features of Apple Silicon
ADVANCED POWER MANAGEMENT With advanced power management, performance and battery life will improve, better than ever before.
SECURE ENCLAVE Secure Enclave will bring best-in-class security, and Apple's high-performance GPU is going to deliver better graphics performance to every Mac. This enhancement makes them even better for professional applications like Final Cut Pro (post-production video editing), Motion (motion graphics), Compressor (video encoding), and high-performance games.
NEURAL ENGINE AND MACHINE LEARNING Combined with Neural Engine Technology, Apple Silicon chips will make the Mac a fantastic platform for machine learning.
OTHER TECHNOLOGIES Apple is also bringing many other custom technologies, such as video-display and image-processing engines, that will help make the Mac better than ever before.
Why make the switch from Intel to Apple Silicon?
The transition will establish a universal architecture across all Apple products. It makes it far easier for app developers to create their apps for the entire Apple ecosystem (not just iOS products, but also Macs as well).
(Running mobile apps on the desktop has been made possible for Chromebooks when Android apps and Google Play were introduced.)
Until WWDC 2020, there have been a total of three significant transitions in Apple's history.
1994-1996: Transitioned from 68k processors to the PowerPC architecture
2001-2003: Transitioned from Mac OS 9.2 to Mac OS X (the latter now known as just macOS)
2006-2007: Transitioned from PowerPC to Intel processors (the computer that I am typing this post on is from an Intel-based Mac)
January 2006: Mac OS X 10.4.4 was released, supporting the Intel architecture for the first time
June 2006: First Macs with Intel processors started shipping
June 2007: Transition almost complete
August 2009: Mac OS X 10.6 Snow Leopard dropped support for PowerPC based Macs. Support for PowerPC-only applications still supported on this version, however.
With WWDC 2020, Apple has announced two more major milestones.
2020-2022: Transition from Intel processors to Apple Silicon is underway
2020-2021: macOS Big Sur (11.0.x) will be the first version to support these processors. After nearly 20 years, macOS finally moves from version 10 to 11.
Will there be any impact?
App developers can easily convert the apps they have created for iOS products to run on the new Apple silicon to take advantage of its latest technologies and performance. And for the first time, developers can make their iOS and iPadOS apps available on the Mac without having to modify the code. That would mean that the App Store could merge into one unified store in terms of Apple platforms (currently, there is one App Store for iOS, another one for the Mac). For Canvas Mobile developers, there won't be a huge impact; there is no need to rewrite the entire source code from scratch.
The Transition Process
Even though Apple will ship the first Mac with the new Apple silicon processors by the end of 2020 and complete the transition by 2021-2022, Apple will continue to support and release new versions of macOS for Intel-based Macs for years to come, at least until 2025-2026. Furthermore, Apple will continue to sell new Intel-based Macs in the future. The transition to Apple silicon processors represents one of the most significant milestones in the history of the Macintosh.
Universal App Quick Start Program
The Universal App Quick Start Program (UQSP) includes all the tools and resources developers need to build, test, and optimize their next-generation Universal apps for macOS Big Sur. For $500, in addition to developer resources and one-to-one technical support, Apple will send a Developer Transition Kit (DTK) for developing and testing Universal apps. The program will last no more than a full year.
(We don't know if the $500 fee is for an individual or an organization.)
Developer Transition Kit 2 (DTK-2)
(This is actually a Mac Mini, but with an Apple A12Z Bionic processor instead of an Intel Core processor.)
While some developers think of the DTK-2 as a gift from Apple and want to keep it as a token of appreciation, that isn't really true. According to the terms and conditions, the DTK-2 is the property of Apple. Developers must return the kits to Apple within 30 days following the conclusion of the program. The first time the UQSP program occurred was back to 2005. It cost $1,000 to join, and Apple gave developers a DTK-1, which is a Power Mac G5. As with the new DTK-2 devices, those Macs also had to be returned at the end of the program, although Apple did provide participants with a free first-generation Intel iMac in return.
Canvas and the UQSP
Now, back to Canvas. The main topic is: How can Instructure optimize the performance and layout for Canvas Mobile on macOS? We know that there is a Responsive Layout on the web version of Canvas, and resizing the width changes the view. We want to find out how the layout will look like for Canvas Mobile running on macOS.
Here is a look at Canvas Student on the iPhone in portrait orientation, showing the Assignments page of the Math 3 course. Below it lies the Course Navigation links. Even though it may look similar to the Responsive Layout for the mobile web version of Canvas, the title bar (Assignments - Math 3) is not clickable to get to the Course Navigation page with these same links.
Now, let's look at the iPad view of the History 101 course. It resembles more of the desktop web version of Canvas, with the Course Navigation links on the left side.
What that means is that there are currently some inconsistencies between Canvas Mobile and Canvas Desktop. It's not just the title bar that can open the Course Navigation menu on the iPhone, but also resizing and scaling for font size and accessibility.
What I want to see in Canvas 7 is the ability for Mac users to resize the app window, switching between the iPhone view to the iPad view, and vice versa.
Mobile View (Apple and Google platforms only)
There needs to be an option to open the course content in the Canvas Mobile Apps.
Mobile View is not available for Windows 10 since Windows 10 Mobile support ended back to January 2020.
The following items are supported in Mobile View:
Conversations & Notifications
Clicking the Mobile View button will pop up this dialog. If you are enrolled as a teacher, you can choose to open the content in the Canvas Teacher or Student app to see how the content will look like as a teacher or student, respectively.
(If you do not have the corresponding app downloaded, it will redirect you to the app store for the platform you are running (App Store for Apple platforms, Play Store for Google platforms).)
(This does not work correctly for Canvas Parent, as parents can only view assignments, course events, grades, and the front page for a student within that app, not other portions of Canvas.)
There are potential issues that need to be fixed as soon as possible to optimize the mobile experience for the Mac. Here are a few.
QR Code for Mobile Login does not work on the same device
This feature is designed to work on two devices at the same time: the desktop platform displaying the QR code, and the mobile platform scanning the code. In order to fix this issue, biometric technologies may need to be used (i.e., Touch ID and Face ID on the Mac; Pixel Imprint on the Chromebook).
(When enabling biometric login for a certain device, users must reenter their Canvas password for security reasons.)
FINGERPRINTS AND TOUCH ID Will the same fingerprint work for additional Canvas institutions added through the list when Change User is selected? We don't want 5 fingerprints each representing a different institution, making things more complicated! (Up to 5 fingerprints can be added on a single device with Touch ID.)
FACE ID Things may get complicated with Face ID on Apple products including the iPhone X series, iPad Pro 3, and later devices. One scenario is that if your parent's or sibling's face looks just like yours and breaks in (Scenario 1)! Another scenario is when you can successfully authenticate when you are really young, but not when you grow up (Scenario 2). According to Apple, the statistical probability is different for twins and siblings that look just like you, and among children younger than 13 years old because their distinct facial features may not have developed fully, making them unnoticeable until they grow up.
Scenario 1: Twin stuffed animals acting as siblings (younger one on the left). Assume that the registered face is that of the younger sibling. If they were real humans, will Face ID succeed on both of them, or will it only succeed on the younger sibling?
Scenario 2: Age progression of the same person (6th grade on the left, senior year on the right). Notice that her facial features are more noticeable as a young woman on the right.
Incompatibility with Intel-based Macs
As of right now, there are no Macs that run Apple Silicon processors. Doing a search for Canvas Instructure in the Mac App Store will not return any results. Apple Silicon is an ARM type of processor, and the first Apple Silicon Macs may arrive for consumers before the end of the Fall 2020 semester.
Seriously? No Instructure desktop apps for the Mac?
Lack of touch screen support
When there are iOS apps running on a Mac with Apple Silicon, not having a touch screen can be a problem. What if a teacher needs to make annotations on images using the Apple Pencil when he/she forgot to bring in his/her iPad? Not having a touch screen hampers the process.
In the MacBook Pro series, there is already a touchpad and a Touch Bar. A touch screen would be excellent, bringing all the multi-touch gestures from iOS to the Mac. An Apple Pencil puts the icing on the cake.
A teacher grades a random student with a caption and drawings from the iPhone.
Lack of augmented reality (AR) support
Even though AR support is available since Canvas 6.5, there is no rear-facing camera on MacBooks. There should be a MacBook Duo to resolve these issues. (MacBook Duo is a fictional name for a 2-in-1 Apple Silicon MacBook that looks similar to the iPad Pro with a detachable touch screen and keyboard, but runs macOS instead of iOS. This has not been officially announced by Apple yet, at least until Q1-Q2 2021.)
Augmented reality files use the USDZ file extension.
SpeedGrader annotations gone wrong
Another issue is the orientation of SpeedGrader annotations. In the example below, both the image on the Mac and on the iPad are both in portrait mode without any problems. A teacher performed his grading on the iPad with Apple Pencil, and it was OK. The graded annotations were on the picture in portrait mode, as you can see in the image below. When going to the Mac to check it out, the annotations that he did on his iPad shows up in landscape mode, which is different from the image from the Mac.
The orientation of annotations on an image can be annoying. With five questions wrong in Part I and 12 wrong in Part II, what did the student really miss?
"I can't read this. Can someone help out?"
When we tested Canvas Mobile with Chromebooks on displays with very high resolutions (Pixel Slate), we found out that the font size is too small and unreadable on the default accessibility settings. Canvas Mobile on Mac really needs to address this accessibility issue ASAP.
The font size is too hard to read when using default accessibility settings for Android apps.
One font for all platforms
I've been a fan of typography ever since I got used to the December 2016 facelift of Canvas (Canvas Production Release Notes (2016-12-10) > Other Updates > User Updates > Global Font Update). The Lato font needs to be included in not just the web interface, but the mobile apps and the new community (New Community Almost Here) as well. This makes the experience consistent across all Canvas services.
There are two Canvas Apps that haven't been updated for a long time. Here's why they need to stay and not be delisted.
Polls (last updated 9/7/2017)
The Canvas Polls app is an easy way for you to request students' opinions in the classroom and collect responses with ease. They only need to download the Polls for Canvas app on their smartphone devices. A teacher uses his/her Mac as a hosting device, while his/her students use their smartphones as responding devices.
Sample Polls screen showing a sample question from the hosting device. In this case, the correct life span of captive pandas is between 25-30 years (marked with a blue dot).
MagicMarker (last updated 5/19/2016)
The MagicMarker app is an efficient and effective way of recording the mastery of learning outcomes in the classroom. This syncs with the Learning Mastery Gradebook in Canvas (How does MagicMarker appear in the Learning Mastery Gradebook?). Tables created in MagicMarker are different than the groups you create in Canvas.
The MagicMarker app syncs with the Learning Mastery Gradebook. You can separate your students into groups and even export the data.
I hope that the Canvas Mobile team gets its hands on the UQSP and DTK-2 soon! Believe me, when the new students arrive for the Spring 2021 semester and beyond, Canvas users can set up mobile apps for grading notifications, due date reminders, and vice versa. When TestFlight for Canvas 7 comes out, educators can demonstrate how Canvas Mobile on Silicon really works and what really needs to be tweaked. Remember, we don't want students to leave out negative course evaluations in the Mobility section (if listed). (TestFlight invitations are limited up to 10,000 users, so be quick to join in once the TestFlight program starts!)
QR for Mobile Login (Available starting March 28 for students, April 4 for teachers and observers)
This feature appears in the Canvas Student 6.7 Release Notes and is now available in the Ready Release Notes (Ready Release Notes (2020-03-28) > Updated Features > User Navigation > Mobile App Login QR Code).
For teachers and observers, the QR code login will be available for the Teacher and Parent apps beginning April 4, 2020. Go to Ready Release Notes (2020-04-04) > User Navigation > Teacher/Observer Mobile App Login QR Code.
QR for Mobile Login. This is already available in the beta environment and will be available in the production environment in the first two Ready Releases on March 28 for students and April 4 for teachers and observers.
Once you click on it, to log in to your Canvas account when you're on the go, just simply scan the QR code from the Canvas Mobile app (Change User > QR Login (below Find My School)). The code expires after 10 minutes, after which you will need to start the process over.
Sample QR code. For security reasons, we had to wait 10 minutes before posting this so that the code is invalidated.
Native Conferences List
You can view any conferences made within Canvas from this section. Webviews are no longer used. Students can join in by tapping the green Join button.
WHAT ARE CANVAS CONFERENCES? Canvas Conferences is a free service provided by BigBlueButton. If your institution is likely to need more than 10 concurrent Conferences powered by BigBlueButton, we recommend upgrading to Premium BigBlueButton or exploring alternative conferencing solutions Canvas partners with, such as Zoom, Hangouts, Teams, and other video conferencing tools who are offering free or discounted services. Learn more. Not all of these services may be supported by your institution. Please contact your local admin for more information.
Sample conference. There is no Join button because the conference has not started.
There are some experimental features in the iOS version of Canvas. Unless stated otherwise, experimental features are available in both the Student and Teacher apps.
(Those are view-only, just ignore them. Only our production team can control these features remotely.)
conferences (TEACHER ONLY) Enable the native view for the Conferences in the Teacher app.
favorite_groups You can view your favorite groups in the Groups tab.
simple_discussion_renderer We don't know what this is, but it may render discussions faster in areas with low-bandwidth, hence the name Simple Discussion Renderer.
graphql_speed_grader Enables the GraphQL data query engine for the SpeedGrader. Learn more.
parent_calendar (TEACHER ONLY) This is useful if parents want to notify their child's teacher about certain events, such as a doctor's appointment. This can come handy for teachers to mark absences as excused.
student_calendar (STUDENT ONLY) It allows you to access your own calendar that is not part of any course.
qr_code_login_enabled (STUDENT ONLY) This refers to the QR for Mobile Login feature above, which will be enabled on March 28 for students and April 4 for teachers and observers.
There is a more responsive layout, though we haven't tested it yet.
Want to learn more?
Please stay tuned to the Canvas Mobile Release Notes space (Release Notes: Mobile) over the next few days to get a broader look at these features. We hope you continue to excel!
In providing support for faculty and courses, certain best practices have been validated repeatedly.
One of those is optimizing Canvas content pages to increase the likelihood your students will actually see and use them!
Unpack Course Documents to Become Canvas Pages
When new instructors are transitioning to Canvas, the process can be overwhelming. An unfortunate, frequent shortcut is to simply “link” documents like the Syllabus or assignment instructions. This may appear to be a quick solution—but only for one semester. When the complexity of updating increases, the missed opportunity to apply best practices becomes apparent through extra hassles and files housekeeping over time.
“A shortcut is the longest distance between two points”— Charles Issawi
Bad reasons to Link documents in the RCE or Modules:
Lower faculty skill-level or understanding of Canvas. Links to files are all the instructor knows how to do.
Instructor already has a big Masterfile with .pdfs and WordDocs that hasn’t been changed in years.
Imaginary threats, like the fear that students will change the Syllabus and argue some detail with the instructor.
Student UX hogwash! Courses have always been a big stack of papers to manage. Why suddenly make life easy for short attention spans?
Document was made on an old typewriter (or on MSWord) with lots of tabs and spaces to center the text. It will be a nightmare to learn the Word ribbon tool at this late date.
Signs that .pdf/.doc overuse is an issue
The course files area has 6 old versions of the Syllabus from which to choose.
Course content is not updated because the instructor can’t locate their original doc for editing.
Students don’t read the syllabus.
Instructors don’t understand why students don’t read the syllabus. See hint.
Hint: Students are looking on an iPhone and don’t want to clog up their memory by accidentally downloading that 10-page Syllabus yet again,plus the document opens in a tiny viewer in a 1 pt. font. Instead, use Canvas content pages to stream beautifully!
Instead of waiting for increased difficulty all around, consider unpacking your .docs into Canvas as a best practice.
Transitions are an ideal time to use Headings/Styles, alt text, descriptive links, ribbon tools, and correct tables in the pages rich content editor (RCE).
Encourage mobile streaming view for all content, versus documents to download and manage.
Increases the likelihood of students being able to see and use the content on any device.
Transitions are an ideal time to check copyright, record your Fair Use justifications, and/or update content into safe compliance.
Quicker updates each semester.
Compare updating a Syllabus in Canvas (Edit, type, save) with updating a linked document (Locate master doc, make changes, save, replace in Canvas, test to make sure you linked the correct doc, get rid of old doc, preserve link, etc.)
Remember, if you don’t do this every day, the workflow is forgettable. Once a semester, and you’ll forget what you’re doing.
No need to search for master copies on a former employee’s home computer. Everything related to the course lives in the Canvas course.
.Docs that are already Accessible easily become Canvas content pages that are accessible, with a simple copy and paste.
The transfer process reveals old-school tabs and spaces misuse. Oops. Those must be manually corrected once the content is in Canvas RCE.
.pdfs can be a nightmare. Depending on the complexity of content, you may need to open a .pdf in Adobe Acrobat Pro and export it as a WordDoc, then scan carefully for substitutions, misspellings, and other transcription errors.
Course builders work with what we have. Sometimes you just let one thing go—temporarily—to meet a deadline or inch toward progress.
*Good Reasons to link a document in RCE or modules
Students need to download and print an entire document intact. Example: APA or MLA formatted example research paper.
Information is not likely to change and is not available another way. Example: an archived out-of-print article.
Information that is already accessibility checked. Example: Government website downloads or official releases.
Ready or Not
Ready or not, increasing numbers of students view Canvas courses on mobile devices. (Numbers may vary by institutions, but the overall trend is upward for mobile use.)
Even if your course is designed for desktop/laptop, a quick check on iOS and Android devices will give you a more complete idea of what students see—and why they interact with the course the way they do.
We’re at nine million monthly active users of the Canvas mobile apps, which is many millions more than when I last posted about Instructure’s approach to mobile. If you’re new to Canvas, or if you’re curious about how and why we do the things we do, this post is for you!
We anchor mobile app development to a few principles:
Focus on experience. There’s a lot of ground to cover when it comes to making Canvas fit into your pocket. The mobile apps have to be secure and accessible and scalable. They have to be translated into 34 languages. The mobile apps have to evolve with regular changes to Canvas web and mobile operating systems. They have to handle courses with 10 students where every assignment is an LTI launch, and they have to handle courses with 200 students where every assignment is a discussion. The iOS and Android apps have to look and function the same way despite being on two different tech stacks produced by two different teams of people. But just as importantly, the mobile apps have to deliver worthwhile experiences. If regular operations take too long or make you miserable, or if the interface just looks like bad, you might as well be using any other LMS. Canvas has to be better.
Here's a subset of the 82 polish items to address before releasing Canvas Parent 3.1, for example:
These polish tickets are usually cosmetic, and they come when we compare iOS and Android side-by-side at the end of developing a feature.
Ship things. Product development exists on a spectrum. On one end, you plan every detail and you never take risks and as a result, you never ship things because you find that details change and risks can’t be avoided. On the other end of the spectrum, you don’t plan enough and you ship quickly and you break things. The outcomes at either end of the spectrum aren’t good. The Canvas mobile teams strive to be somewhere in the middle of that spectrum, always erring on the side of shipping. We can’t deliver the value that we don’t ship. We believe that when we mess up, we ought to listen and learn and ship again.
People over process. In my experience, this is the most overlooked value from the agile manifesto -- which is roughly the constitution of agile software development. Our teams do their best to reconcile what’s planned and what’s right when there’s a gap. We try to keep enough perspective to prevent process from lulling us into doing stupid things. There are scenarios where this principle doesn’t work, but we try to create situations where it does (small teams, smart people, taking on new challenges, limiting recurring meetings, encouraging communication, etc.).
Here's one of my favorite parts about working at Instructure:
This is the mobile support lead's way of saying something is on fire somewhere, check it out. I've worked for companies where people roll their eyes when they see this and say they'll get to it next sprint. That's the worst, and it's what you get with process over people. If there's a fire, we're going to stop regularly scheduled programming to go deal with it.
Prioritize real-life benefits. When you’re planning a project on a platform as versatile as Canvas, it’s tempting to miss the forest for the trees. What happens with our new feature if this course setting is on and this feature flag is off and this sub-account hides this button and this root account has this permission disabled for this role and this ticket hasn’t merged to beta? Concerns like these take up a huge amount of mental space, and to a large extent, it’s the job of product and engineering teams to make sure these cases are hashed out. At some point, it’s also true that 99.723% (see: made-up numbers) of users won’t experience the case you’re worried about, and you’re better off figuring out how to remove extra bits of friction for the average user. This is not a straightforward thing to balance, but in general, the mobile teams will prioritize delivering maximum value to maximum people over checking every last feature box.
Throw a little weird in there. Our software is designed and built by people as quirky as our users, and it ought to reflect that fact for the sake of everyone involved. If you like your software a little more dry and dusty, I’ve had good luck recently with printer utilities, insurance apps, and SimCity 2000 doesn’t hold up quite as well as I expected. Weirdness is especially vulnerable to atrophy over time, but it’s worth protecting. We want to flex those weird muscles.
When you mix those principles together, you get role-based apps which are updated regularly and rated best-in-class by users -- with spinning Canvas logos and panda avatar builders to top it off!
This definitely doesn't mean everything is awesome. Our approach involves tradeoffs. Let’s use peer reviews as an example. It’s a cool feature, and some people rely on peer reviews, and you can’t conduct peer reviews from our mobile apps today. We consider peer reviews every time we touch assignments in mobile. We have a design, and we know how it would work, and we know what it would take to support it. The problem is that peer reviewing is a relatively lesser used feature of assignments, and it would take a lot of effort to support natively. Instead of working on peer reviews last fall, we focused on things like improving load times on grade lists in student and teacher apps, and increasing the visibility of feedback on submissions, and reducing taps to submit assignments. But if you created those peer review assignments, this is still a bummer, and I get it!
I can think of a few escapes for this predicament, in no particular order:
If you’re on a tablet or Chromebook, Canvas web is fully supported in your native web browser
Some schools contract with our professional services team for custom development
Our mobile apps are open source, and some schools build their own mobile apps using our repositories as a model
You could build the feature yourself and submit a pull request for our mobile team to review
We can hop on a call and you can argue that we’re doing it wrong
You can submit a feature idea in our community and see how it resonates with other Canvas users
If you want to know more about web/mobile parity, our documentation team has created some guides for the student and teacher apps that you may find helpful. If you have feedback on making those documents better, send it on!
Working as an EdTech Specialist at a renowned Med School I come across various scenarios.
Major Users:Students, Instructors and Canvas Admins (Including Me!:smileygrin:)
How and Why:
Majority of our students use Canvas iOS app to take notes on their iPads. We have 50+ courses in MD Program and Canvas app is very helpful as it eases the stress of downloading a lot of paper or notes and bring it to the class. Instead use the canvas app on the iPads and write notes on PPTs or PDF's which are linked in their courses.
Other places where Mobile App comes in to picture is when our 3rd Year MD students are in clinics and have no time to login to Desktop. All that they do is use their apps and look at their schedules during their hectic Clerkship Courses. Students find the process of synching calendars easy and are happy about it.
Note taking is easy, stress free and students need not carry tons of paper or books to sessions or classes.
What they like: Announcements, Calendar Events, Grades, To-Do items, Assignments and Files
***I use the Canvas App on Various devices to troubleshoot and test out any new features which can be useful for our students and faculty***
Since the release of the New Quizzes platform in June 2018, there have been many advances. Here are some things that you should know about New Quizzes on Canvas Mobile.
CREATING A NEW QUIZ
In order to create a New Quiz, you must do so from the desktop. You cannot do it from the Canvas Teacher app since there is no Add Assignment button on the bottom right corner of the screen.
From Assignments, we will create a new assignment. We will not use the Add Quiz/Test button due to the lack of certain fields.
Now that we've got the Instructions and Content Selector Sidebars, we can go ahead and fill in some details.
For this assignment, please use the Quizzes 2 LTI External Tool.
Once we save and publish, it will be visible in the Mobile Apps. The pencil icon on the top right will be the only way for you to edit the quiz instructions from the Assignments page. To add/remove questions, select the External Tool under Submission Types.
Once the student finishes the test, the results will be displayed.
Wait a second! Something's not looking right when there are fractions.
Students can leave comments to request regrades. The teacher can then open the Mobile SpeedGrader and see the problematic question.
RULES FOR REGRADING
Regrading only applies to completed submissions. If all students are affected, please wait for all submissions before regrading.
Since the correct answer is a fraction, manual grading may be needed. To avoid any issues from occurring in the future, please recommend students to round decimals to the required precision, up to the thousandths.
And that's it! You can now master the power of New Quizzes in the Canvas Mobile Apps!
Hope summer is going well for you! After the second-rainiest spring on record, the atmosphere over Utah burned away and now we're all walking around in climate-controlled space suits and eating sand.
Here’s what the mobile teams are working on.
New assignment details and submission flows are coming in Canvas Student 6.6! We showed off this update at InstructureCon two weeks ago, but in case you missed it, here’s what that looks like:
The student app assignment detail view is the most-used detail view across all of our apps, and we’re really excited about this upgrade going into the new school year. We improved assignment details in a few ways:
Grade visibility. Most students access the assignment detail view to check a grade (surprise!), so we needed the design to reflect that pattern.
Feedback visibility. Grades are just the tip of the feedback iceberg. Almost all the value for the student -- and the bulk of time spent grading -- is in the comments. We wanted to beef up the visibility of teacher feedback (off the top of my head: annotations, annotation comments, submission comments, media comments, rubrics, and rubric comments). The student can now find all feedback in a single place while also viewing and interacting with their submission. And for the first time, students can navigate all rubric details -- all scores, definitions and descriptions -- both before and after submission.
Submission flow. If you’ve never submitted a file to Canvas from another app on a mobile device then you haven’t felt confusion. You may have heard about it, but you haven’t felt it in your bones. That’s a problem because students increasingly rely on the mobile app to submit assignments. Well, problem solved in 6.6. Here’s the new share extension in action -- submitting from the Files app on iOS to Canvas:
Submitting from within the app is also much better -- with the one exception of cloud assignments: those remain unchanged. To ship this update before fall start we had to save improvements to cloud assignments for another day. To play with new submissions yourself, see the TestFlight link below.
Lastly -- unrelated to assignment details -- hold onto your wigs and keys if you use Canvas Student on iPad because here’s the thing you’ve been waiting for:
That’s right, support for split view is coming in 6.6!
We’re in the process of testing 6.6 for both platforms right now. The iOS team is on track to begin rollout in the first week of August, and the Android update will happen a few days afterwards. If you want to help us test the 6.6 update by playing with it on iOS through TestFlight, here’s a link:
As usual, if you find any funny business, feel free to report it below. (...unless the 6.6 update is already released to stores when you're reading this. Once a release hits stores, you're better off reporting any issue you find to Canvas Support.)
Over the past few weeks we’ve worked on improving load times for submissions in the teacher app. If you work in large courses -- on the order of hundreds of enrollments -- stay tuned for the next teacher app release on iOS and Android. It should hit stores within the next few weeks. Everyone will see improved load times but it will be most noticeable for large courses.
Next up for the teacher app is adding support for post policies, which are the new gradebook’s equivalent of the old gradebook’s muting/unmuting grades.
We’ve already released two updates that should really help the observer self-registration process for teachers and parents this fall. If your school/system uses self-registration for parents, take note and help spread the word:
[INSERT LASER-LIKE FOCUS HERE]
Teachers can now create pairing codes for an entire class with a single click. Check out the documentation onexporting pairing codes to see how.
Parents can now add additional students to observe from the parent app. Android added this feature a little while ago, and iOS supports it as of this week. Canvas guides are being updated right now with directions for parents, and I'll update this post with the links when they're live. Update: Check out the iOS and Android guides for adding students to observe from the parent app.
I’m super excited to have these updates live before fall start, and I hope you are too! They should really smooth out the parent onboarding process.
Now for the fun part: improving the in-app experience for parents! Our goal is to help parents support their students on a daily basis by answering some simple questions: How’s my kid doing, and what’s due and when? We have three updates planned to answer those questions in a better way, divided as follows.
3.0: New grades list and updated syllabus. Today, parents can only view grades in the week view, which means there’s no way to see a summary of assignment grades in a particular course. In the 3.0 update, parents will have access to the same grades list that students have today (including grading period filter). In addition, we’ll make access to the course syllabus more obvious and add support for linking from rich content.
3.1: Messaging. The parent app is getting an inbox! Parents will be able to send and receive messages from the app, and message composition will be contextual. Parents will be able to compose a message from the assignment detail view, for example, and we’ll add the appropriate teacher(s) as recipients automatically. We’ll also include a link to the content being referenced in the text of the message so teachers have a little more context on the receiving end. (Yes, the parent app will use the existing Canvas Inbox to make this happen.)
3.2: New calendar. The parent app’s calendar isn’t awesome. We’re going to be redesigning it to include more course content like announcements and to-do items, which don’t show up in today's parent app. Parents should also be able to filter the calendar by course and content type, and see busy days upcoming for their students at a glance. (Then we plan to reuse the new calendar for the student app.)
These updates will be built and released throughout the fall. I’ll post progress updates, designs and links to beta builds in CMUG in the coming weeks.
Happy fall start to everyone! If you experience any issues, report them! We're here to help!
I've been pretty happy with the Canvas mobile app, but have noticed that there seems to be no real way of managing To Do notifications through the Canvas mobile app. I have the To Do notifications show up and can click on them, but they don't go away or mark as completed. I'm all about getting to a zero-inbox in terms of zero notification numbers on my app (which keeps throwing me when I see something on Canvas mobile as an instructor that I can only get rid of by logging in on a computer and marking them as complete). I guess I was wondering if anyone else has had this happen? This isn't dire or even really a big issue, but it's something I noticed and figured it was worth a small blog.
The improvements made to the Canvas Mobile app demonstrate that its development team is singing the same melody as the teacher-instructor promoters who run their courses on Canvas.
The drive to achieve near-complete transparency between the computer-web based Canvas experience and the mobile-based one is the most important feature to increase usage across a school and campus. Like original Apple GUI guidelines, creating parallel environments that work relatively the same promotes usage because a user skill set is interchangeable across platforms.
Here's some stuff that's worth writing home about!
We’ve been working for months on a new assignment details page and a new submission workflow for students in mobile. I outlined some of the features of that project in a post last fall. To minimize the risk of disruption, we don’t plan to release the update in stores until summer, but we will provide a link to a beta version of this update as it nears completion.
Cloud assignments have been harder to make good than we originally thought they would be, but we aren’t giving up yet. Everything else is going swimmingly. This is going to be an awesome update. Right now, it’s slated as Canvas Student 6.6 – more to come soon.
We will have a smaller feature release – Canvas Student 6.5 – likely before the end of the school year. That’s going to contain a syllabus update for both platforms. The old (current) syllabus works like this:
That’s...one way to present a syllabus. But probably not the best way. If you use the syllabus as your course homepage, you probably create attractive and/or important content to be featured on the syllabus, which today gets hidden behind a “Syllabus” button when the student has already tapped to view the syllabus. The old design is also inconsistent with the way the syllabus is presented on the web: rich content more prominent, and list of assignments less prominent.
The new syllabus looks like this:
So that’s better.
The 6.5 update will also include some cool iOS-specific features: support for viewing augmented reality files, checking grades via Siri Shortcuts, and updated Apple Pencil support.
We’re almost done with the most-requested feature for the teacher app, which is adding support for modules. Starting with Canvas Teacher 1.8, you’ll be able to navigate your course via modules list, like this:
Editing the module progression is significantly more complex because of features like mastery paths and module item prerequisites, and it also seems like a task more aligned with course creation rather than course facilitation, so that won’t be included in this release. Instead, if you like navigating your course via modules, you can do that!
This update also improves our use of temporary file storage so the teacher app stops eating all the goshdarn space on your iPad.
If you see anything wonky, wobbly or just straight up whack, please reply to this post so we can fix it.
I’m on a mission to make the parent mobile experience good. Less like Twinkies good, more like Plato’s Form of the Good. That means two things for the app most urgently:
Improve the process of connecting parents and students and teachers and Canvas. We started this last summer by unifying the parent user/Canvas user paradigm, which was 100% necessary and fundamental for kicking things up another notch, but now we need to actually kick things up another notch: allow teachers to mass produce pairing codes, allow students to create pairing/QR codes from mobile, allow parents to connect with multiple students from the parent app…that kind of thing.
Provide parents with more/better information. They access Canvas because they’re trying to help their kids. That could require viewing course announcements, school announcements, course content, calendar, assignment grades, communication with teachers, maybe even content recommendations to help them understand the topics their kids are learning.
We’re in a position to help parents support their students, and to reduce stress for admins and teachers in dealing with parents, and most importantly, to accomplish these things in a way that actually helps kids (instead of creating more noise or adding unnecessary burden). I’ll provide more specifics on upcoming parent app development soon, but if you feel passionately about this, I’d love to pick your brain and steal your ideas! The best way to arrange this is probably through your CSM.
I use apps for everything (doesn't everyone?) and I suppose when I first downloaded the Canvas app a few years ago, I was first learning how to use Canvas myself, and the app was not nearly as updated as it is today, so sadly I did not use it much. I recently watched the video and I highly recommend it to everyone. It pleasantly lead me through the newest features and how they can be used easily in our everyday life. (Picture yourself waiting on line at a grocery store and being able to publish/unpublish course content.) The fact that speedgrader can be used from my phone is especially exciting for me because I can now grade from anywhere. I look forward to using this latest version more often as a teacher and I will also recommend that my students use it. Special thanks to Ryan.Seilhamer@ucf.edu and firstname.lastname@example.org for the presentation. mobile-app
It’s about time we published an update from the Canvas mobile teams, don’t you think?
Here are some fall start highlights -- in descending order of how much they excited me:
Neighbor’s kid stopped me taking out the trash and said the student app’s gotten soooooo much better since he started using it last year!
Canvas Student hit 3 million daily active users a couple of weeks ago!
iOS 12 and Android Pie updates broke fewer things than usual!
Canvas Teacher became the highest-rated LMS teacher app on iOS and Android!
Canvas Student became the highest-rated LMS student app on iOS and Android!
Not everything went perfectly. Including both platforms, we closed 50 functional bugs in the month of September, and several more accessibility bugs. The self-registration pairing code rollout for parent app required a couple tweaks. But overall, it was a relatively smooth start for the mobile teams.
Both platforms are in the process of releasing Student 6.4 (adding support for custom help and searching files) and Teacher 1.7 (respecting document orientation set by DocViewer and adding an annotation eraser).
Now we’re on to Student 6.5, which will bring with it a new assignment details page and submission flow. The assignment details page is the most-visited details page in the student app. It’s also one of the oldest, and the current design doesn’t make much sense given how students use it.
For example, we know students look for their grade when they open an assignment after submission, but right now that information is hidden in a separate tab. We know students want information about submission status, but right now that doesn’t appear in the assignment details view. We know teachers want students to see comments and feedback, but right now there's no indication that feedback is available. We plan to fix all of that.
In addition, we think we can significantly improve the experience of submitting an assignment through mobile. Today’s submission flow feels awkward and laborious, and our analytics say that only about half the people that start submitting through mobile actually finish submitting through mobile. With an increasing number of students completing assignments solely from mobile devices, we have an opportunity to reduce some points of regular friction. That includes adding proper support for Canvas cloud assignments.
Today, opening a Google or Office assignment from the mobile app takes approximately 147 taps too many, and that’s because we launch the assignment as an LTI tool in a webview rather than attempting to open the Google or Office native apps. In the future, when a student taps “Launch External Tool” on a cloud assignment, we plan to redirect to the Google or Office apps directly. Combine that with a more streamlined process for submitting to Canvas from third-party apps, and submission flows in the student app all around should be much improved with the 6.5 release.
Let’s see some pictures!
New assignment details -- notice the submission status, the large grade cell, the “Feedback” pill indicating submission comments or annotations, and the large “Submit” or “Resubmit” button:
New submission details -- notice the student’s view of their submission is only a single tap away from the assignment details, the similarity to the teacher app SpeedGrader view, and the ability to view the submission, rubric and feedback in a single place:
New app extension -- students can submit a file directly to Canvas from a third-party app:
The iOS and Android teams are both working on new assignment details and submission flows now, and we hope to release it sometime in Q1 of 2019. We’re super excited about these upgrades.
If you’ve got a pet peeve with assignments in mobile that you feel like I haven’t addressed here, or if you want to give any other feedback, feel free to post a comment!
Instructure's mobile strategy usually ends up outlined in a couple of InstructureCon presentations, but if you’re new to Canvas, or if you haven’t made it to InstructureCon, or if you just want to know more about our mobile strategy, here’s a brief summary.
We build native mobile apps because native mobile offers a much better experience than mobile web from mobile devices. This means we minimize the number of web views in our mobile apps, and instead rely heavily on the Canvas API to present information from Canvas in a way that’s optimized for touchscreens, big and small. There are a few learning management systems that treat their mobile apps like web portals and their mobile experiences generally stink as a result, but many lean native nowadays for that reason. If you’ve ever annotated a paper from a mobile web browser and then done the same thing from a native app (say, Canvas Teacher), you can easily feel the difference in experience.
A few years ago we decided that we could further refine our mobile experience by focusing on how people approached Canvas from mobile devices. We noted a few truths up front:
In other words, Canvas is roughly bigger than the Pyramids of Giza combined, and even a gargantuan phone like the Samsung Galaxy Note is relatively small, and we have the opportunity to bridge that gap by giving people the experience they need from mobile -- tailored to their role -- because their expectations depend on their role.
A student approaches Canvas saying I want to see my grade on this assignment, or I want to see what’s due next week. A teacher approaches Canvas saying I want to post an announcement, or I want to grade this assignment. A parent approaches Canvas saying What’s Canvas? So let's deliver experiences that map to those realities.
This approach is working so far on a number of fronts:
The apps are easier to use because they provide the functions you need rather than the ones you don’t.
It streamlines messaging for us and for our clients. Parents don’t need to learn how to use Canvas, for example, they just need to learn how to use the parent app.
It forces us to decompose problems from the perspective of the user. Rather than let’s build an assignments page for a 4-inch screen, we say students need to submit assignments, or teachers need to grade assignments, and those needs inform how the assignments page needs to look and function from a variety of perspectives.
The apps are easier to maintain because we narrow the set of perspectives to consider for any function within a given app.
For an example that illustrates how roles inform the Canvas mobile experience, here’s the teacher app assignment details page beside the upcoming student app assignment details page:
Teachers see submission dials -- students see information about their own submissions. Teachers see publishing status -- students see submission status. Teachers can modify assignment details and grade submissions -- students can submit (or resubmit) assignments. Especially with limited screen real estate, we want to give people the experience they need to efficiently get things done no matter who or where they are.
We continue to release app updates geared towards boosting productivity and efficiency as quickly as we can build them, which is relatively quickly. Of course, Canvas offers support for tablet browsers, and new features -- like our new quizzes platform -- are built to be fully responsive if you're really jonesing for browser access from a mobile device. But we think if mobile is worth doing, it's worth doing right. With an ever-increasing number of daily active users in our native mobile apps, we're confident that we're on the right path.
Lastly, we make it a point to learn our way forward, so your feedback is incredibly important to the success and usefulness of our apps. If you're passionate about a idea related to mobile, we want to hear from you. Real bad. You can reach out to us through the community or email or client services. We'd love to chat.
I have been recently researching ways to reach the Modern Learner via mobile lessons, activities, projects, and plans. Yes, there are a lot of apps out there that are beneficial, but as email@example.com and Ryan.Seilhamer@ucf.edu stated "While the Canvas app is effective in translating your course to be responsive on a mobile device, it is the job of the teacher or instructional designer to effectively design assignments to address the on-the-go learner."
I conducted a workshop at the most recent Online Teaching Conference in Anaheim (2018) on Motivating Students with Cell Phone Activities. But as research has it and timing luck has it, I wish I would have read more about the Canvas Polls app. I think this Canvas Polls app and the upcoming Quizzes.Next features are going to be beneficial for increasing interaction while still being in the same overall environment. I applaud Canvas for seeing that need.
Anyway, I have some materials that are pinned to my twitter account from the conference, and I can share with you what I tried to convey should you have any questions. It seems like we are going to have a learning world soon that is community driven, individually contributed, location free, movable, right sized, goal oriented, success driven, failure learnable, and data large. A new way to learn, interact, earn badges, etc.
At UCF we have been using Canvas campus-wide since 2013. When we started using Canvas, there wasn't much mobile available. The SpeedGrader app had been out for a year or so, the iOS app was very limited, and the Android app just came out of beta. Over the past six years that mobile apps have grown to be an essential part of not only the online experience but the overall educational experience for students at UCF.
In 2014 we recognized the need to understand better how students were interacting with Canvas while on-the-go and we conducted our first Canvas Mobile App survey at UCF. The study is critical because it gives us a better understanding of how students are interacting with the most popular mobile app at UCF and help us better communicate needs directly to Instructure and the Canvas Mobile team. In 2018 we completed our fifth Canvas Mobile App survey which I want to share with the community to create discussion, inform your mobile strategy, and help improve the experience for students.
The survey was administered April 1-8 inside of Canvas as a global message to all users. We have found that this messaging feature is handy, but needs to be used sparingly to avoid overloading the user.
The survey this year included a record number of users (1688), and we suspect this might be to the addition of global messages being available on iOS for the first time. In the past, this was only available to web users and the smaller subset of Android users.
At UCF we are BIG and this includes a large diverse student population of over 66k. The following charts give a breakdown of the demographics behind the 1688 student responses.
App usage has been high at UCF since 2014 with very little change in usage, which is very high. In other studies, mobile app ownership is approximately 3:1 iPhone over Android devices. This survey was mostly in line with ownership. One interesting fact is that 3% of student reported both Android and iOS.
Outside of this survey, our Canvas Data shows approximately 20% of all Canvas traffic is through the Canvas Student app, which includes over 500 million page views and 40k unique users per month.
The following question is always interesting because the biggest reason why students didn't use the Canvas Student app was they didn't know it was available. This used to be a more significant issue, but when smart banners were added to Canvas in 2014, we noticed that adoption jumped up significantly.
This survey and our previous have proved that student who use the Canvas Student app, use it a lot. In fact, 96% use it at least once a week with the majority (87%) using it even more. It's the most used app at UCF just in front of the popular UCF Mobile app at 84%.
Since we started this survey in 2014, this hasn't changed much. Students generally want to know three things:
How am I doing in class?
What do I need to do?
How do I do it?
The survey shows that students are using the mobile app for light interaction and staying connected to their class while on-the-go.
In 2016 we added the following question to learn even more about how students use the Canvas apps, and this is in line with my statement above about what student generally want to know and how their interactions a light. There isn't a lot of interaction around assignments, discussions, or quizzes. These features are being used to get more information about a particular assignment, but not to submit one.
The favorite features have a lot of similarities to the most popular features like grades and assignments. Thought it's interesting to see how the app gives access and is convenient and easy. I am particularly interested in the word "check" which shows student value being able to stay connected with short interactions.
Which devices students own and how they access Canvas is essential as we continue to manage resources and support users on all platforms. One interesting point that has become common in recent surveys is laptop/desktop ownership is slightly less than smartphones. The 2018 survey is no different with 12 students reporting not owning a computer, with only four not owning a smartphone.
When I discuss these surveys I always say that usage doesn't equal importance, and it's no surprise that laptop/desktop is extremely important to students, with the smartphone in the middle, and tablet way behind at 11 percent.
If you take extremely important and very important to one data point, the smartphone is essential to almost 3/4th of the students in the survey with the tablet still well behind.
Communication through mobile technologies is often known as "non-traditional" but from our recent survey its obvious this is becoming less true as students reported push notifications (70%) to be more important than email (66%) with the more traditional SMS at 29%.
I hope to dive more into these numbers over the next few months but would love to know what you think. Also, if you are interested in running this survey at your school, please let me know as I'd be excited to compare numbers.
Version 6.0 of the student app has been in the wild for a few weeks, and I wanted to give an update on what you can expect from the Canvas mobile apps over the next few months.
We’ll continue releasing feature updates to Canvas Student through the rest of this school year, in roughly this order:
Version 6.1: New, shiny, and performant course announcements and discussions!
Announcements and discussions are two of the most-used course components in Canvas, and both our iOS and Android teams have been working for weeks to make them more usable and more scalable in mobile. One of the tricky things about discussion threads in mobile is that they can get really long, really quickly. They can also contain loads of images. And while your four-year-old laptop may have a paltry 8GB of RAM, your brand new iPhone X only contains 3GB of RAM. But you need both of those devices to load the same amount of information in about the same amount of time. So that was one of our goals. Here’s how an image-heavy discussion thread looks in the store version today compared to version 6.1:
To sum it up, replies load more quickly and the interface isn’t so cramped. The reply button in old discussions was also really easy to miss. See it in the top right? Well, a lot of people didn’t. So we added a big and loud “Reply” button at the bottom of the original post (and one less loud one at the top right of the original post).
Version 6.2: New, shiny, and performant grades and assignments lists!
The old grades and assignments lists took a long time to load. This update will make them better.
Version 6.3: New, shiny, and performant assignment details and submission flows!
Viewing and submitting assignments from the student app today isn’t easy. We want to improve three things:
Make grades and submission comments easy for students to access
Allow students to see their submission, submission comments, rubric and annotations in a single place
Make submitting assignments in mobile less of a pain in the butt
Here’s roughly what the new assignment details page will look like after a student receives a grade:
We also have plans to add support for peer reviews and improve support for cloud assignments - though I’m not sure yet if those two pieces will go into 6.3 or a subsequent version.
Version 1.5: Support for section-specific announcements, better discussions and faster context cards!
This should be released for both platforms within the next couple of weeks.
Other note: Teacher app doesn’t support modules today. We’re pretty close to being able to make this happen. Modules necessarily come last in development because almost every other kind of content in Canvas can be attached to a module (i.e., modules don’t do anything without assignments and pages and quizzes and links and files also being supported). Modules are also the way that many teachers interact with their course content, so getting to an assignment through the assignments list rather than through modules feels unnatural. Our first pass at modules will definitely not be adding support for building modules or modifyingthe structure of modules, as much as it will be viewing modules and module items. The basis for the teacher app’s success so far is its focus on course facilitation rather than course building or course structuring, and we’ll keep that theme going in however we incorporate modules. Version 1.5 is the last feature release for the teacher app we have planned on this side of InstructureCon, but we might be able to squeeze some other stuff in.
Version 2.0: Better authentication for e’rbody! Today, the first-time user experience in Canvas Parent is no good. The login process is convoluted, and once you log in, you still need to add a student before you can use the app -- even if you log in as an observer already connected to a student in the web. What’s worse, if your first-time experience in a mobile app stinks, you’re much more likely to delete the app than you are to keep using it. Generally, parents who get past that first-time experience use the app and it works well. But some parents want to see submission details, and some parents want messaging with teachers, and both of those things are technically impossible with the way authentication works today. We’ve found that virtually every K-12 institution either imports observers from their SIS or otherwise allows self-registration for observers. Either way, parents have an observer account in Canvas if the institution allows it. So we’re going to run with that and make everyone’s brains hurt less. In version 2.0, parents logging into the parent app will:
Find their school
Enter their observer credentials
Land in the app with their students already connected
If you can’t picture it, this is the difference we’re talking about between login pages:
And while simplifying that experience is awesome, this change will also make the app more stable and much more scalable for future development (like adding messaging or viewing submission details).
MOBILE PAGE VIEW REPORTING
Last but not least, we’re making page view reporting from mobile a real thing. Today, we report mobile activity through API calls made from the apps. Those API calls are really hard to use in tracking activity, because a single page in mobile may require four calls, or it may require none. Instead, we’re going to fit mobile into the web URL paradigm to make reporting easier. For example, if a student enters a course from the iOS student app, we’ll report that they went to “https://[account].instructure.com/courses/[courseid]” from "Canvas Student iOS" rather than showing all the calls we made loading that course’s homepage.
SpeedGrader is really the heart of this app. It gives teachers the ability to do so much on the go, and with the addition of an iPhone version, it’s even more convenient than before.
The parity between Android and iOS is very good with only a few subtle differences:
When annotating, the Android app doesn’t have a button for undo
Under comments, the Android app adds the text “Submitted Files” with the submission.
The Android version hides “Add Comments” or “View Long Description” in a Rubric if this hasn't been set on the web. iOS hides "Add Comments" if not set on the web, but shows "View Long Description" regardless.
The rubrics area on Android has a save button that needs to be tapped to save the grade. With iOS, the user can just swipe to the next user and the grade is saved
The Android version can export documents from SpeedGrader to the device, while iOS does not.
Rubrics display from smallest to largest, left to right - This is opposite on the web version (8/10 firstname.lastname@example.org)
On Android, users can add choose the option Set as Front Page when creating a new page
Refer to Attaching Media section for differences.
Android can filter people by section.
Android and iOS are fundamentally different, so it’s not reasonable to expect perfect parity with how features work on both platforms. For instance, Android generally leans towards drop downs, when iOS uses dropdown menus. Other difference(s) noticed:
Android version has limited support for web-based LTIs
My students can be the biggest procrastinators. I suppose we all can procrastinate from time to time but I find that my students every year have trouble with completing their assignments early enough to have proper time for editing and self-reflection. I teach in a graduate school; all of my students are adults and choose to be students at the school. We have discussions in class about the issue of procrastination but for some it seems to be difficult to change. I am hoping to find advice from the community on any tips or strategies you find effective to help students avoid putting off their work until the last minute. Specifically, I am wondering whether there is anything related to the mobile use of Canvas that can motivate students to work in a more time efficient manner. Thanks!
This semester, I challenged myself to only use Teacher when grading and providing feedback. The release of Canvas Teacher got me like:
tl;dr Overwhelmingly positive.
The course I am (was, by the time some of you may be reading this) teaching is Foundations of Online Learning. It needed a redesign, so my focus was on mobile-friendly Universal Design for Learning concepts and OER content. One discussion per week and assignments that made use of design choice including Adobe Spark, Canva, FlipGrid and other non-traditional assignment submission types.
As an eight-week course, and with a full-time job during the week and little spare time outside of work (tbh, I'd rather hang out with my family than grade all the time), it was important to me to find balance.
Being up earlier than the rest of my family, that meant that I could grade assignments that came in on Monday on Tuesday morning, and be caught up and ready to go for Tuesday submissions on Wednesday. The variety offered to me for providing on-the-go comments with my iOS camera and microphone, or annotating with DocViewer, were really stellar. I could do all of that while laying down on the couch in my jammies, rather than trying to prop a MacBook Pro on my lap with cats running around.
Grading anytime, anywhere. I graded assignments in the early morning with a cup of tea, in between takes at band practice and before bed. All on different devices, as the situation warranted.
Editing announcements and assignments on the fly: Based on feedback from the students, I was able to flex Teacher's muscles by adapting course content to meet their needs.
Ran into an issue with drag and drop on iOS 11. Support was incredibly responsive and the issue was resolved.
Notifications for Teacher did not seem to work. I relied on notifications from Student.
If I did not have the Student app, notifications would not have pushed to me. It could have been a potential problem, but was resolved using a workaround.
No support for adding images to assignment submissions as a teacher. Had to go to mobile Canvas via Chrome for iOS. Bummer.
Many, many thanks to the team at Instructure for getting Teacher out to the community. Every opportunity I get to evangelize it, I do. I encourage everyone in this community that also teaches to try a similar experiment. Not only is it worth it, I now have a better sense of how to be more responsive to faculty concerns about the mobile Canvas experience.
During the summer of 2017, a number of UCF faculty were able to preview the Canvas Teacher App and use it in their classes. In an effort to better understand the impact of this app and help communicate our experience to Instructure, my colleague email@example.com and I conducted a number of face-to-face interviews. In the first of a series of blog posts, here is the story of Rick Brunson. Rick is a beloved Journalism instructor in the Nicholson School of Communication at UCF. He is always willing to learn and bend new technologies if it will have a lasting impact on his students. In fact, he is one of just a few instructors that teachers a mobile journalism class to prepare his students for the workplace.
His belief in the smartphone can be summed up in the following quote "The smartphone is very important to me because 90 percent of the content I capture for my classes is done on a mobile device. This includes photos, videos, and lecture notes - and quizzes too!"
“Grading is hypertension, the silent killer of faculty and this app is the prescription because grading is always waiting."
During the interview, Rick repeatedly praised having access to SpeedGrader on his iPhone as the most important feature. This will enable and empower him more with a mobile device to grade wherever. If he’s at a barber shop, a doctor’s office, or just waiting in line, he can grade assignments. All technology is a double-edged sword and it can help you make more of your time, but also be available when you shouldn’t be working, but that’s up to him, and not the tool. He doesn’t see the Teacher app providing more extensive feedback because the nature of mobile is “short” and quick, but thinks it will be great for short assignments on his iPhone.
“The faculty members greatest enemy is time and this app empowers us more with our time.”
He tells his students on the first day of class to email him through Canvas because he gets a notification in the Canvas app and it’s likely to give them a speedy response. Rick believes that he might let communication bleed a little too much his personal life, but he sees it as a positive. He has relied on the Canvas Student app for years as a communication tool to stay in contact with his students. Even if it’s “I’m at dinner, I’ll get back to you in an hour.” Students aren’t necessarily impatient, but technology has trained us to expect fairly rapid responses when we have questions. The app empowers him to do that and meet those expectations. Even though some faculty manage their communication in blocks of time and set expectations that they only answer in certain hours, which keep their lives organized, he doesn't do this. He tells a story about a student who contacted him about her first internship and she was really excited! Because of the Canvas app, he was able to immediately respond and give that virtual high-five. He doesn’t want to stick to a 24-hour policy because it’s important that he is not only responsive to concerns but celebrates their joys. It means something to his students.
“The app helps me take care of the next task, lessen the load, and use time more effectively.”
The student context cards are going to be helpful in enhancing communication with students because he can verify messages from students when they have questions about grades and assignments. In particular, this will give him more information when a student asks "why did I get this grade?" or "how am I doing in class?" Before the Canvas Teacher app, he would have to run back to a computer, look at their progress and then reply. This can take time and hold up the process by hours or days. With the app, he can do that on the fly and communicate much faster to students.
Rick mentioned that the "Message Students Who" feature inside each assignment will be useful for smaller classes, but still might be hard to use for larger class sizes (125+). This will take more time to explore how this feature can enhance communication and possibly increase student engagement.
Every semester UCF conducts the Student Perception of Instruction (SPI) for each course. These are incredibly important to faculty and can be tied to many important performance factors. Rick consistently gets positive notes on how responsive he is when students have a question or concern. He mentioned a quote by the famous educational researcher Chuck Dzuiban; "Does my instructor care about my learning?" This is always the most important question asked by students. Communication style and responsiveness are important to show you “care” about their learning and the app enables you to do that. Rick believes the Canvas Teacher app will be a valuable tool as he continues to increase communication, engage with students, and be more efficient.
We made these Inside Look posts a regular feature in the Canvas Teacher Focus Group, and it seemed to work pretty well, so I’m writing this one to see how it flies in CMUG. The basic premise is to illuminate little nuggets of our product development process for people who might be interested.
Today, we’re talking success metrics. Every major Canvas project starts in a ‘Discover’ phase, in which a product manager (PM) researches a problem until they feel comfortable with it from a bunch of different perspectives. Then the PM prepares a project summary, which is a high-level review of the problem, and what Canvas could do about it, and how it fits with our product strategy. The PM also defines success metrics for the potential project, which take the form of, “If we do this thing, then we would expect this result by this timeframe.” Then the PM presents the project summary to leadership, who gives a thumbs-up or a thumbs-down or a “keep digging.”
Supposing the project makes it through those gates, and is developed and then released -- at the end of the project, we measure success by the metrics that we agreed upon at the outset. Usually with the mobile apps, we’re measuring success by usage and client satisfaction. In the case of the teacher app launch, we’re measuring usage by monthly active user count and we’re measuring client satisfaction by app store rating.
The new teacher app’s success metrics were:
By the end of Q3, this app will have at least 15,000 monthly active users.
By the end of Q3, this app will have at least a 4-star rating in stores.
Great news: We had over 30,000 monthly active users in the teacher app in the month of September! Woah! By comparison, we had roughly 7,000 monthly active users in the old SpeedGrader app at this point a year ago.
Okay news: The iOS teacher app is currently at a 4.1! The Android teacher app is currently at a 3.3 – but we think we’ll see a bump in Android ratings with version 1.1 out the door.
These metrics aren’t used to get people in trouble, but they are used to try to compare what we expected to happen with what actually happened, and then to make better metrics the next time.
If you want to help us out, make your feelings known in app store ratings!
iOS beta users will be happy to hear that we released Canvas Teacher 1.2 to TestFlight this morning! If you're on our list of TestFlight users, you'll have received an email from TestFlight. Here's what we need you to break:
Student context cards. From anywhere in the app (including from the new People list!), you can tap a student's avatar to view their context card. It's cool! Let us know what load times you're experiencing when launching a card. It shouldn't take more than a couple of seconds. You can also tap on an assignment from the context card to launch of submission preview in SpeedGrader. The context cards look like this:
Audio/video comments in SpeedGrader. You can now add audio or video comments to a submission in SpeedGrader by tapping the "+" button from the Comments tab. There's a known issue where the sent video doesn't display properly in the comment stream until you navigate away from and then back to the comments tab, but recording, previewing and posting should all be working properly. The option to add audio or video looks like this:
Attendance. If you've enabled the Roll Call LTI attendance tool in Canvas, you'll see an "Attendance" component added to your course components list in the teacher app. Once launched, you can tap on a student name to mark that student as present, absent, or late. We want to hear your feedback on load times and user experience with this component. Attendance in the teacher app looks like this:
You can also add attachments to announcements, discussions and inbox messages now.
So that's version 1.2!
What about 1.1, you say? iOS will be pushing a 1.1 version to stores which is everything mentioned above minus attendance. We need some more feedback on attendance before we make that available everywhere.
We have dreams for the attendance tool that haven't come to fruition yet. We want teachers to be able to set aphone or tablet at thefront of the classroom that records attendance as students enter the room. We feel like it's technically possible today, and would be better than paper attendance, and shouldn't require schools to purchase any special hardware or adopt lengthy setup procedures. But the technology is still new, and not all smartphones have the right hardware, and not all kids have smartphones, so it'll be a minute before our dreams come true.
As usual with teacher app betas for iOS, you can send us feedback by taking a screenshot from anywhere within the app.
Android teachers - stay tuned, 1.1/1.2 will be out soon!
I hope everyone is enjoying the Teacher App so far. As you begin using it in the fall semester, please continue to share your experience, good or bad! If the app is missing a vital feature, create an idea! If you are lost, ask a question! firstname.lastname@example.org and myself are looking over these everyday!
Teacher App - Part Deux
In case you missed it, the Teacher isn't done and the mobile team needs your help to get over the finish line! If you are interested in the next round of Canvas Teacher beta testing, well here's your chance!
Now that Canvas Teacher is released (with over 100,000 downloads in its first two weeks of life!) and the focus group that helped us build it has wrapped up, we're looking for volunteers from CMUG to help us test pre-production versions of the app, usually a few days or a week before we release them to everybody else in stores.
There are two things we might need from you:
Most importantly, we need you to tell us if you experience catastrophic failures. Here are some examples of catastrophic failures:
"Wooooah, I can't log in anymore on the beta version."
"Wooooah, the app is crashing every time I do [x] on the beta version."
"Wooooah, this new beta feature is garbage."
"Wooooah, I left my coffee on the counter and now I've gone too far to turn back."
Sometimes we'll want to test a feature to see if it's working or not. In these cases, I'll post something in CMUG about what we're testing.
iOS users will get beta access through Apple's TestFlight app. Android users will get beta access directly from Google Play. TestFlight restricts the number of external testers we can have, so -- no hard feelings -- we may boot you from testing if you never look at beta versions.
We'll import new beta registrants on Fridays, and we'll leave this sign-up sheet available for the next few weeks, depending on how many responses we get. You'll receive an email from TestFlight or Google Play -- depending on your response -- when we get you added to our testers list.
I found the CanvasLIVE session on the Mobile Series: Discussions in the Palm of Your Hand to be very helpful as an Instructor. There seems to be better interaction with Discussion Board in the new Canvas Teacher App as well. Although we are limited with the design aspect of our courses (online instructors teach from a template) I will definitely spread the word on this tool to other Instructors in my office. I can see Instructors finding the mobile app for replying and interacting with students beneficial as it is more convenient than pulling up their laptop or waiting to get to a computer.
If you joined us at InstructureCon 2017 for Canvas Mobile, An App for Everyone, thanks for joining me. If not, I wanted to make this available for everyone. The presentation is attached.
This session covers the parent, student, and teacher roles when using the Canvas Mobile apps. This includes a short overview of 23 interviews by myself, Kristin Lundstrum, and Ashley Salter. We plan to share more of these interviews over the next few months in this space.
As part of the presentation, we showed using an iPad Pro with the Apple Pencil to do annotations in SpeedGrader, which is available below:
I have been working in Higher Education for twelve or thirteen years now. I can remember using a VCR to record videoconferencing sessions, and now we have SaaS technologies for remote learners around the globe. I remember the click wheel on the iPod. I also remember when the idea of mobile learning on some campuses was providing a podcast of lectures in iTunes. Recently I have been struggling with K12 mobile initiatives; mainly because it directly affects my family. Let me preface my writing with some warnings:
I have two children. One of my children is in first grade and I have engulfed him in mobile technologies in our house since he was about 18 months old (with limitations). My second child is a bit older than 3 and has had relatively little exposure to mobile devices.
My wife is an elementary educator. She teaches Special Education and was first in the classroom in the Fall of 2007. She stayed home for a few years, but she is now wrapping up her 5th year teaching. Because of her, I have "seen" mobile devices in the classroom, out of the classroom, and district wide "initiatives".
Because my wife is an educator, she was very concerned about exposing my oldest son to "screen time" when he was so young. By the age of 2, he was navigating an iPad like a pro. I was amazed at his brain and how he was able to handle these "tasks". He would start in one app, play a little, go to another and sing a song, cycle through some more, and then complete the circle by coming to the app with the song and continue singing where the song left off. I was amazed. Granted, there's always the chance I scarred him (if there are any early childhood experts here, please let me know!), but I wanted that exposure for him. We were fortunate that I had A LOT of mobile devices for testing purposes at a previous job, so we might as well use them, right?
Now with my second son - he has had considerably less interaction with mobile devices. He turned three in December, and he probably played on an iPad or iPhone for the first time in the past 3-4 months. His frustration with the device is noticeable. He gets confused about where to tap, doesn't understand the purpose of the games/educational learning activities, and eventually just switches to the next app.
Why does the difference between my two boys matter?
I truly believe it is imperative for any educational institution, both Higher Ed and K12, to have a strong, top down, mobile learning initiative in place. However, sometimes when just technical people or district level trainers are involved, pedagogy or learning outcomes are solely missed (I'm guilty as well).
Take my two children - they come from the same house, have access to mobile devices (as long as we allow them!) and both Windows and macOS machines - yet I would only label one of them as "technically proficient" (and yes, I know one of my children is 3). The district my wife works for and my oldest attends recently had a large iPad roll out, and my son has said "I watch YouTube and play games on them..." I know my son can navigate the iPad just fine, but what about his peers? I know the demographics of his school, and there is a possibility that some children do not have regular access to devices. Are we giving our students an iPad just to say the device is in the classroom? Or are we giving a true exposure with measurable learning outcomes?
What about training for classroom teachers? How do you train teachers to work with students who may not understand the functionality? What about helping your teachers on how the device can impact learning and not just help them in their job? Parent and spouse aside - as a tax payer in the district, I want to ensure I didn't just help pay for a pretty little paperweight. My wife went through 8 hours of iPad training when the massive roll out happened; it was worthless. Teachers were taught how to take a selfie. Then they were taught to take a video and upload it to YouTube. Those two things took one day (two hours).
What is the answer? I have no idea! Every district and college has a different make up. But - ensure your classroom teachers are properly trained on how mobile devices will benefit teaching and learning. Ultimately, ask yourself, "What is the value add for the student?" We have all seen the highly publicized district iPad roll outs in the last few years. How many of them had a measurable success for the students?
Quality product and service by its nature shouldn't call attention to itself for being so good, or the amount of preparation and work it took to achieve quality. (This is always my goal designing digital content in our K-12 learning space.)
These 2½ minute videos are clear and concise, and always helpful. email@example.com did a great job producing and delivering these pieces. Why is the series so great? It virtually disintegrates the learning curve by embedding just the knowledge tidbits designers need on the fly. For me, this approach prevents the frustration of being stopped a brick wall of ignorance, especially when I foresee a problem area at the start of a project milestone.
So, thank you #Leslie_Stark, for your exemplary work on the series. I think you've set the bar that much higher for the delivery of bite-sized chunks of information, delivered right on time for us very busy designers. Is there, by the way, an index page of all the videos in the series?