interactions you are having (Daniel Suthers and many others) • Tech: The kind of stack you choose matters for the kind of interface you end up building
But cannot be used on edx.org • Specific to EdX, needs to use specific programming languages and interfaces • Can integrate much more deeply with host platform/ data
unique ID (like 3420-49324j) • Full page loads can also carry EdX ID and email (user has to give permission) • Has no access to any other data on EdX platform (can return a grade) • Not specific to EdX • Can do anything, including integrating with non-LTI enabled sites • Immediate access to analytics data
unique ID (like 3420-49324j) • Full page loads can also carry EdX ID and email (user has to give permission) • Has no access to any other data on EdX platform (can return a grade) • Not specific to EdX • Can do anything, including integrating with non-LTI enabled sites • Immediate access to analytics data
• Very fast (many requests per second, low latency) • Strong support for web sockets • Rich support for background workers, mail servers, etc. • Ecosystem still growing
• Very fast (many requests per second, low latency) • Strong support for web sockets • Rich support for background workers, mail servers, etc. • Ecosystem still growing
be enacted. • 2. Describe the major theme of the lesson. • 3. What are the learning goals of the technology-enhanced lesson? • 4. Some aspects of the design (complete any that are relevant) • 4a. Student-Centered Design • 4b. Peer Collaboration • 4c. Use of Handheld or Mobile Computers • 4d. Supporting Equity and Diversity • 5. What is the activity structure of the lesson? • 6. Assessment notes. • 7. Enactment notes. • 7a. Ethics or enactment concerns Capstone team based project (no-credit)